[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)

[Timo Aaltonen]

lunar will first get 6.1 and release with 6.2

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

Title:
  pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
  Fatal), type=Transaction Layer, (Requester ID)

Status in HWE Next:
  Fix Committed
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  My kernel log periodically bursts with:

  [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.593393] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.598564] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.603829] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.614959] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.620296] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.625554] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.636495] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.641867] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.647169] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.658369] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.663803] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.669263] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.680699] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.686267] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.691759] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 

  This has happened even since I got the machine. It also happened with
  5.15.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2477 F wireplumber
   /dev/snd/seq:dan2474 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep  6 13:52:35 2022
  InstallationDate: Installed on 2022-07-20 (47 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be 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.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-15-generic N/A
   linux-backports-modules-5.19.0-15-generic  N/A
   linux-firmware 20220831.gitd3c92280-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/20/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EDADL579.0046.2021.1220.2351
  dmi.board.name: NUC12EDBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M27908-302
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.7
  dmi.modalias: 

[Kernel-packages] [Bug 1971712] Re: Add support for Intel DG2

[Timo Aaltonen]

mesa backport will get in proposed soon

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Add support for Intel DG2

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in mesa source package in Jammy:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip
  firmare: updates to i915 DMC, GuC

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

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


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

[Kernel-packages] [Bug 1969966] Re: No support for Intel Killer AX1675i

[Juerg Haefliger]

This card is still not supported by upstream. There's not much we can do
until that happens.

** Changed in: backport-iwlwifi-dkms (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: linux (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  No support for Intel Killer AX1675i

Status in backport-iwlwifi-dkms package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 
5511 laptop but can't get WiFi or Bluetooth.
  About WiFi I get these logs:
  ➜ sudo dmesg|grep wifi -i
  [4.917786] Loading modules backported from iwlwifi
  [4.917787] iwlwifi-stack-public:master:9858:4c7cba27
  [4.984194] Intel(R) Wireless WiFi driver for Linux
  [4.985038] iwlwifi :00:14.3: enabling device ( -> 0002)
  [4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, 
rfid=0x2010d000
  [4.996123] iwlwifi: probe of :00:14.3 failed with error -22
  About Bluetooth I get these logs:
  ➜ sudo dmesg|grep bluetooth -i
  [4.977780] Bluetooth: Core ver 2.22
  [4.977793] NET: Registered PF_BLUETOOTH protocol family
  [4.977794] Bluetooth: HCI device and connection manager initialized
  [4.977799] Bluetooth: HCI socket layer initialized
  [4.977800] Bluetooth: L2CAP socket layer initialized
  [4.977803] Bluetooth: SCO socket layer initialized
  [5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018
  [5.003784] Bluetooth: hci0: Device revision is 0
  [5.003787] Bluetooth: hci0: Secure boot is enabled
  [5.003788] Bluetooth: hci0: OTP lock is enabled
  [5.003788] Bluetooth: hci0: API lock is enabled
  [5.003789] Bluetooth: hci0: Debug lock is disabled
  [5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [5.006774] Bluetooth: hci0: Failed to load Intel firmware file 
intel/ibt-19-0-3.sfi (-2)
  [5.007774] Bluetooth: hci0: MSFT supported features length mismatch
  [7.023197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [7.023201] Bluetooth: BNEP filters: protocol multicast
  [7.023204] Bluetooth: BNEP socket layer initialized
  I'm in doubt about WiFi, since the message doesn't mention a missing 
firmware, but Bluetooth is very clear about it.

  
  I'm using Ubuntu 22.04 LTS with bleeding edge kernel 5.17.4. I also tried 
with 5.18rc1 but no change
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Dependencies: firmware-sof-signed 2.0-1ubuntu3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-26 (152 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-firmware 20220329.git681281e4-0ubuntu1
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  jammy
  Uname: Linux 5.17.4-051704-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to jammy on 2022-02-03 (83 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)

[Daniel van Vugt]

I'm finally noticing the bug again on lunar (5.19.0-21-generic) so will
commence testing 5.19.0-28-generic ... But what is the planned series to
fix lunar? Is it 6.0?

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

Title:
  pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
  Fatal), type=Transaction Layer, (Requester ID)

Status in HWE Next:
  Fix Committed
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  My kernel log periodically bursts with:

  [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.593393] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.598564] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.603829] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.614959] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.620296] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.625554] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.636495] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.641867] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.647169] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.658369] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.663803] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.669263] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 
  [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [10405.680699] pcieport :00:1b.0:   device [8086:7ac4] error 
status/mask=0010/4000
  [10405.686267] pcieport :00:1b.0:[20] UnsupReq   (First)
  [10405.691759] pcieport :00:1b.0: AER:   TLP Header: 3400 0152 
 

  This has happened even since I got the machine. It also happened with
  5.15.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan2477 F wireplumber
   /dev/snd/seq:dan2474 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep  6 13:52:35 2022
  InstallationDate: Installed on 2022-07-20 (47 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic 
root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be 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.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-15-generic N/A
   linux-backports-modules-5.19.0-15-generic  N/A
   linux-firmware 20220831.gitd3c92280-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/20/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EDADL579.0046.2021.1220.2351
  dmi.board.name: NUC12EDBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M27908-302
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  

[Kernel-packages] [Bug 1995453] Re: Add some ACPI device IDs for Intel HID device

[Ivan Hu]

Verify pass.

Kernel:5.19.0-30.31 kernel (kinetic-proposed)
SKU: Alxd-Low-DVT-C1 (202209-30619)
BIOS: 0.12.70

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

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

Title:
  Add some ACPI device IDs for Intel HID device

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  Add the ACPI devices IDs for Intel JasonLake, MeteorLake and RaptorLake

  [Fix]
  ACPI devices IDs are add the the related Intel HID devices on these platforms 
can work.

  [Test]
  Verified the Intel HID events can work such as power button for suspend and 
wake.
   
  [Where problems could occur]
  Add the ACPI device IDs for support Intel HID devices, so chance of problems 
should be low.

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


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

[Kernel-packages] [Bug 1987618] Re: [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways

[Frode Nordahl]

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

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

Title:
  [jammy mlx5] Slow outbound N/S TCP connections for instances on
  gateways

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Charmed OpenStack on Jammy.

  Hardware offloaded instances that reside on the hypervisor which is
  also the active OVN gateway for their network have degraded
  connectivity.

  $ time wget --debug -O /dev/null http://nova.clouds.archive.ubuntu.com/ubuntu/
  Setting --output-document (outputdocument) to /dev/null
  DEBUG output created by Wget 1.21.2 on linux-gnu.

  Reading HSTS entries from /home/ubuntu/.wget-hsts
  URI encoding = ‘UTF-8’
  --2022-08-25 07:16:54--  http://nova.clouds.archive.ubuntu.com/ubuntu/
  Resolving nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)... 
91.189.91.121, 185.125.190.38, 185.125.190.41, ...
  Caching nova.clouds.archive.ubuntu.com => 91.189.91.121 185.125.190.38 
185.125.190.41 91.189.91.122 2001:67c:1562::29 2620:2d:4000:1::1b 
2620:2d:4000:1::18 2001:67c:1562::26
  Connecting to nova.clouds.archive.ubuntu.com 
(nova.clouds.archive.ubuntu.com)|91.189.91.121|:80... connected.
  Created socket 4.
  Releasing 0x55ef05654490 (new refcount 1).

  ---request begin---
  GET /ubuntu/ HTTP/1.1
  Host: nova.clouds.archive.ubuntu.com
  User-Agent: Wget/1.21.2
  Accept: */*
  Accept-Encoding: identity
  Connection: Keep-Alive

  ---request end---
  HTTP request sent, awaiting response... 
  ---response begin---
  HTTP/1.1 200 OK
  Date: Thu, 25 Aug 2022 07:16:54 GMT
  Server: Apache/2.4.29 (Ubuntu)
  Vary: Accept-Encoding
  Content-Length: 1779
  Keep-Alive: timeout=5, max=100
  Connection: Keep-Alive
  Content-Type: text/html;charset=UTF-8

  ---response end---
  200 OK
  Registered socket 4 for persistent reuse.
  URI content encoding = ‘UTF-8’
  Length: 1779 (1.7K) [text/html]
  Saving to: ‘/dev/null’

  /dev/null
  
100%[>]
  1.74K  --.-KB/sin 0.07s

  2022-08-25 07:16:59 (24.3 KB/s) - ‘/dev/null’ saved [1779/1779]

  
  real  0m5.591s
  user  0m0.000s
  sys   0m0.005s

  $ sudo tcpdump -nevi ens3 not port 22
  07:16:54.017265 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 
(0x0800), length 74: (tos 0x0, ttl 64, id 50207, offset 0, flags [DF], proto 
TCP (6), length 60)
  10.42.1.8.43060 > 91.189.91.121.80: Flags [S], cksum 0xc296 (incorrect -> 
0x4190), seq 2905559525, win 62314, options [mss 8902,sackOK,TS val 4081686695 
ecr 0,nop,wscale 7], length 0
  07:16:54.091378 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 
(0x0800), length 74: (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto TCP 
(6), length 60)
  91.189.91.121.80 > 10.42.1.8.43060: Flags [S.], cksum 0x809d (correct), 
seq 3404088064, ack 2905559526, win 65160, options [mss 1460,sackOK,TS val 
932285789 ecr 4081686695,nop,wscale 7], length 0
  07:16:54.091402 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 
(0x0800), length 66: (tos 0x0, ttl 64, id 50208, offset 0, flags [DF], proto 
TCP (6), length 52)
  10.42.1.8.43060 > 91.189.91.121.80: Flags [.], cksum 0xc28e (incorrect -> 
0xabc0), ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 932285789], 
length 0
  07:16:54.091512 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 
(0x0800), length 218: (tos 0x0, ttl 64, id 50209, offset 0, flags [DF], proto 
TCP (6), length 204)
  10.42.1.8.43060 > 91.189.91.121.80: Flags [P.], cksum 0xc326 (incorrect 
-> 0x7d0c), seq 1:153, ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 
932285789], length 152: HTTP, length: 152
GET /ubuntu/ HTTP/1.1
Host: nova.clouds.archive.ubuntu.com
User-Agent: Wget/1.21.2
Accept: */*
Accept-Encoding: identity
Connection: Keep-Alive

  07:16:54.166170 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 
(0x0800), length 66: (tos 0x0, ttl 58, id 15660, offset 0, flags [DF], proto 
TCP (6), length 52)
  91.189.91.121.80 > 10.42.1.8.43060: Flags [.], cksum 0xaac7 (correct), 
ack 153, win 508, options [nop,nop,TS val 932285865 ecr 4081686770], length 0
  07:16:59.171924 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 
(0x0800), length 66: (tos 0x0, ttl 58, id 15669, offset 0, flags [DF], proto 
TCP (6), length 52)
  91.189.91.121.80 > 10.42.1.8.43060: Flags [F.], cksum 0x8f61 (correct), 
seq 2008, ack 153, win 508, options [nop,nop,TS val 932290871 ecr 4081686770], 
length 0
  07:16:59.171956 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 
(0x0800), length 78: (tos 0x0, ttl 64, id 50210, offset 0, flags [DF], proto 
TCP (6), length 64)
  10.42.1.8.43060 > 91.189.91.121.80: Flags [.], cksum 0xc29a (incorrect -> 
0x356e), ack 1, win 487, 

[Kernel-packages] [Bug 1995941] Re: [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait

[Frank Heimes]

This bug was not opened against linux-iot, hence the new request for 
verification is not valid.
I'm updating the verification tags just to unblock the further process...

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

Title:
  [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW
  wait

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * In a secure execution guest, the external interrupt for the SIGP
 external call order is delivered twice to a VCPU even though it was 
 only sent once.

   * Under PV (protected virtualization), external call interrupts are
     delivered by the SIGP interpretation facility, without KVM's
     involvement.
     But, if the receiving CPU is in enabled wait, KVM needs to wake the
     receiving CPU such that the interrupt can be delivered.
     Hence, in this case, the SIGP external call order causes
     an interception.

   * In response, KVM only needs to wake the receiving VCPU.
     Interrupt delivery is then handled by the SIGP interpretation facility.

   * KVM wrongly assumed it also needs to request injection for the
     external call interrupt after the respective intercept, causing the
     interrupt to be delivered twice:
     * once through the SIGP interpretation facility
     * and once through the interrupt injection control by KVM.

   * Solution is to add appropriate special handling for 108 external
     call intercepts.

  [Fix]

   * c3f0e5fd2d33 c3f0e5fd2d33d80c5a5a8b5e5d2bab2841709cc8
     "KVM: s390: pv: don't present the ecall interrupt twice"

  [Test Case]

   * Have an Secure Execution (PV) environment setup on an
     IBM z15 or LinuxONE III LPAR using Ubuntu Server 20.04 (latest).

   * Apply kvm-unit-test submitted upstream:
     "[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP call \
  orders in enabled wait"

   * Run the smp_PV kvm-unit-test: ./run_tests.sh smp_PV

   * Check logs/smp_PV.log.
     If system is affected, the following line can be found:
     "ABORT: smp: psw wait: ecall: Unexpected external call interrupt \
  (code 0x1202): on cpu 1 at 0x11958"

   * If the system is not affected, the line should look like this:
     "PASS: smp: psw wait: ecall: received"

  [Regression Potential / What can go wrong]

   * The handle_pv_notification can be wrong and misleading
     in case 'ret' is not handled correctly.

   * trace_kvm_s390_handle_sigp_pei might not be called correctly,
     now after the if condition.

   * In worst case the external interrupt could not be delivered
     at all or still too often.

  [Other]

   * The fix/patch c3f0e5fd2d33 got upstream accepted with kernel v6.0,
     so it not only needs to be applied to 20.04/5.4, but also to 22.04/5.15
     and 22.10/5.19.

   * But the patch got properly tagged for upstream stable:
     Cc:  # 5.7
     Fixes: da24a0cc58ed ("KVM: s390: protvirt: Instruction emulation")

   * And with that it got already picked up and is included in:
     22.04 with Ubuntu-5.15.0-53.59 (currently in jammy-proposed)
     22.10 with Ubuntu-5.19.0-16.16 means incl. in the release kernel.

   * So the only Ubuntu release that is affected is 20.04/focal.
  __

  Description:   KVM: PV: ext call delivered twice when receiver in PSW wait
  Symptom:   In a secure execution guest, the external interrupt for the
     SIGP external call order is delivered twice to a VCPU even
     though it was only sent once.
  Problem:   Under PV, external call interrupts are delivered by the SIGP
     interpretation facility, without KVM's involvement. But, if the
     receiving CPU is in enabled wait, KVM needs to wake the
     receiving CPU such that the interrupt can be delivered. Hence,
     in this case, the SIGP external call order causes an
     interception. In response, KVM only needs to wake the receiving
     VCPU. Interrupt delivery is then handled by the SIGP
     interpretation facility.

     KVM wrongfuly assumed it also needs to request injection for 
the
     external call interrupt after the respective intercept, causing
     the interrupt to be delivered twice: once through the SIGP
     interpretation facility and once through the interrupt 
injection
     control by KVM.
  Solution:  Add appropriate special handling for 108 external call
     intercepts.
  Reproduction:  0. Apply kvm-unit-test submitted upstream
    ("[kvm-unit-tests PATCH v1 0/4] s390x: add tests 

[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer

[Frank Heimes]

This bug was not opened against linux-ibm or linux-iot, hence the new request 
for verification is not valid.
I'm updating the verification tags just to unblock the further process...

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

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

Title:
  [UBUNTU 20.04] boot: Add s390x secure boot trailer

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * Secure boot of Linux on s390x will no longer be possible
     with an upcoming IBM zSystems firmware update.

  [Fix]

   * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
     for kinetic and jammy

   * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
     backport for focal

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.

   * Ensure that 'Enable Secure Boot for Linux' is marked in case
     'SCSI Load' is selected at the HMCs Load task and Activation Profile.

   * Perform an Ubuntu Server installation, either 20.04 or 22.04
     (latest ISO).
     It will be a secure boot installation by default in case
     'Enable Secure Boot for Linux' was marked.

   * Check sysfs:
     /sys/firmware/ipl/has_secure
    '1' indicates hw support for secure boot, otherwise '0'
     /sys/firmware/ipl/secure
    '1' indicates that secure IPL was successful, otherwise '0'

   * Navigate to the HMC task 'System information'
     and check the active firmware release.

   * Ensure that Ubuntu is still bootable in secure-boot mode
     with the updated firmware active,
     by for example doing a reboot after the firmware upgrade.

   * There is also a way to test the trailer on systems that do not
 have the updated firmware yet - in this case use the following script:
 https://launchpadlibrarian.net/633126861/check_sb_trailer.sh

  [Where problems could occur]

   * The 'trailer' might be broken, invalid or in a wrong format
     and can't be identified or read properly,
     or may cause issues while compressing/decompressing the kernel.

   * In worst case secure boot might become broken,
     even on systems that are still on the unpatched firmware level.

   * Or secure boot will become broken in general.

  [Other Info]

   * The above commit was upstream accepted with v6.1-rc3.

   * And it got tagged for upstream stable with:
     "Cc:  # 5.2+"

   * But since this bug is marked as critical, and the patch is relatively
     short, traceable and s390x-specific, I'll go ahead and submit this
     patch for Jammy and Focal ahead of upstream stable.

   * Since on focal file 'vmlinux.lds.S' is at a different location
     'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
     and the context is slightly different, the backport is needed.

   * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
     the patch incl. when at the planned target level.

  __

  Description:   boot: Add secure boot trailer
  Symptom:   Secure boot of Linux will no longer be possible with an 
upcoming
     IBM Z firmware update.

  Problem:   New IBM Z firmware requires signed bootable images to contain a
     trailing data block with a specific format.

  Solution:  Add the trailing data block to the Linux kernel image.

  Reproduction:  Apply latest firmware, perform IPL with Secure Boot
  enabled.

  Fix:   available upstream with
  Upstream-ID:   aa127a069ef312aca02b730d5137e1778d0c3ba7

  Preventive:yes

  Date:  2022-10-27
  Author:Peter Oberparleiter 
  Component: kernel

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


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

[Kernel-packages] [Bug 1995941] Re: [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-iot/5.4.0-1011.13
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 removed: verification-done-focal
** Tags added: kernel-spammed-focal-linux-iot verification-needed-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/1995941

Title:
  [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW
  wait

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * In a secure execution guest, the external interrupt for the SIGP
 external call order is delivered twice to a VCPU even though it was 
 only sent once.

   * Under PV (protected virtualization), external call interrupts are
     delivered by the SIGP interpretation facility, without KVM's
     involvement.
     But, if the receiving CPU is in enabled wait, KVM needs to wake the
     receiving CPU such that the interrupt can be delivered.
     Hence, in this case, the SIGP external call order causes
     an interception.

   * In response, KVM only needs to wake the receiving VCPU.
     Interrupt delivery is then handled by the SIGP interpretation facility.

   * KVM wrongly assumed it also needs to request injection for the
     external call interrupt after the respective intercept, causing the
     interrupt to be delivered twice:
     * once through the SIGP interpretation facility
     * and once through the interrupt injection control by KVM.

   * Solution is to add appropriate special handling for 108 external
     call intercepts.

  [Fix]

   * c3f0e5fd2d33 c3f0e5fd2d33d80c5a5a8b5e5d2bab2841709cc8
     "KVM: s390: pv: don't present the ecall interrupt twice"

  [Test Case]

   * Have an Secure Execution (PV) environment setup on an
     IBM z15 or LinuxONE III LPAR using Ubuntu Server 20.04 (latest).

   * Apply kvm-unit-test submitted upstream:
     "[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP call \
  orders in enabled wait"

   * Run the smp_PV kvm-unit-test: ./run_tests.sh smp_PV

   * Check logs/smp_PV.log.
     If system is affected, the following line can be found:
     "ABORT: smp: psw wait: ecall: Unexpected external call interrupt \
  (code 0x1202): on cpu 1 at 0x11958"

   * If the system is not affected, the line should look like this:
     "PASS: smp: psw wait: ecall: received"

  [Regression Potential / What can go wrong]

   * The handle_pv_notification can be wrong and misleading
     in case 'ret' is not handled correctly.

   * trace_kvm_s390_handle_sigp_pei might not be called correctly,
     now after the if condition.

   * In worst case the external interrupt could not be delivered
     at all or still too often.

  [Other]

   * The fix/patch c3f0e5fd2d33 got upstream accepted with kernel v6.0,
     so it not only needs to be applied to 20.04/5.4, but also to 22.04/5.15
     and 22.10/5.19.

   * But the patch got properly tagged for upstream stable:
     Cc:  # 5.7
     Fixes: da24a0cc58ed ("KVM: s390: protvirt: Instruction emulation")

   * And with that it got already picked up and is included in:
     22.04 with Ubuntu-5.15.0-53.59 (currently in jammy-proposed)
     22.10 with Ubuntu-5.19.0-16.16 means incl. in the release kernel.

   * So the only Ubuntu release that is affected is 20.04/focal.
  __

  Description:   KVM: PV: ext call delivered twice when receiver in PSW wait
  Symptom:   In a secure execution guest, the external interrupt for the
     SIGP external call order is delivered twice to a VCPU even
     though it was only sent once.
  Problem:   Under PV, external call interrupts are delivered by the SIGP
     interpretation facility, without KVM's involvement. But, if the
     receiving CPU is in enabled wait, KVM needs to wake the
     receiving CPU such that the interrupt can be delivered. Hence,
     in this case, the SIGP external call order causes an
     interception. In response, KVM only needs to wake the receiving
     VCPU. Interrupt delivery is then handled by the SIGP
     interpretation facility.

     KVM wrongfuly assumed it also needs to request injection for 
the
     

[Kernel-packages] [Bug 1993315] Re: md: Replace snprintf with scnprintf

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-iot/5.4.0-1011.13
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 removed: verification-done-focal
** Tags added: kernel-spammed-focal-linux-iot verification-needed-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/1993315

Title:
  md: Replace snprintf with scnprintf

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]
  Current code produces a warning as shown below when total characters
  in the constituent block device names plus the slashes exceeds 200.
  snprintf() returns the number of characters generated from the given
  input, which could cause the expression “200 – len” to wrap around
  to a large positive number. Fix this by using scnprintf() instead,
  which returns the actual number of characters written into the buffer.

  [ 1513.267938] [ cut here ]
  [ 1513.267943] WARNING: CPU: 15 PID: 37247 at /lib/vsprintf.c:2509 
vsnprintf+0x2c8/0x510
  [ 1513.267944] Modules linked in:  
  [ 1513.267969] CPU: 15 PID: 37247 Comm: mdadm Not tainted 5.4.0-1085-azure 
#90~18.04.1-Ubuntu
  [ 1513.267969] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 05/09/2022
  [ 1513.267971] RIP: 0010:vsnprintf+0x2c8/0x510
  <-snip->
  [ 1513.267982] Call Trace:
  [ 1513.267986]  snprintf+0x45/0x70
  [ 1513.267990]  ? disk_name+0x71/0xa0
  [ 1513.267993]  dump_zones+0x114/0x240 [raid0]
  [ 1513.267996]  ? _cond_resched+0x19/0x40
  [ 1513.267998]  raid0_run+0x19e/0x270 [raid0]
  [ 1513.268000]  md_run+0x5e0/0xc50
  [ 1513.268003]  ? security_capable+0x3f/0x60
  [ 1513.268005]  do_md_run+0x19/0x110
  [ 1513.268006]  md_ioctl+0x195e/0x1f90
  [ 1513.268007]  blkdev_ioctl+0x91f/0x9f0
  [ 1513.268010]  block_ioctl+0x3d/0x50
  [ 1513.268012]  do_vfs_ioctl+0xa9/0x640
  [ 1513.268014]  ? __fput+0x162/0x260
  [ 1513.268016]  ksys_ioctl+0x75/0x80
  [ 1513.268017]  __x64_sys_ioctl+0x1a/0x20
  [ 1513.268019]  do_syscall_64+0x5e/0x200
  [ 1513.268021]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=1727fd5015d8f93474148f94e34cda5aa6ad4a43

  [Where things could go wrong]

  This seems unlikely to cause a regression

  [Other Info]

  SF: #00346036

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


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

[Kernel-packages] [Bug 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-iot/5.4.0-1011.13
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: kernel-spammed-focal-linux-iot

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

Title:
  input/keyboard: the keyboard on some Asus laptops can't work

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  This is upstream tracking bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=216158

  The bug originates from an upstream bug, and the ubuntu users request
  me to do a SRU to make the ubuntu linux work on their Asus laptops, so
  once the pathces are merge to mainline kernel, I start to prepare this
  SRU.

  [Impact]
  Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel
  will override to a new configuration for that IRQ, this will make the
  keyboard not work anymore under linux.

  [Fix]
  Backport 2 patches from mainlie kernel to fix this problem.

  [Test]
  boot the patched kernel on the machine, test the keyboard, all
  regular keys could work.

  
  [Where problems could occur]
  The patches use the dmi table to match the machines, so only the
  matched Asus laptops will be impacted by the patches, if there is
  any regression, the regression only affects those matched Asus
  laptops, and the regression possibility is very low since ubuntu
  users already tested the patches on their own Asus laptops.

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


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

[Kernel-packages] [Bug 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-iot/5.4.0-1011.13
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 removed: verification-done-focal
** Tags added: kernel-spammed-focal-linux-iot verification-needed-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/1996071

Title:
  [UBUNTU 20.04] boot: Add s390x secure boot trailer

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * Secure boot of Linux on s390x will no longer be possible
     with an upcoming IBM zSystems firmware update.

  [Fix]

   * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add 
secure boot trailer"
     for kinetic and jammy

   * 
https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch
     backport for focal

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is
  required.

   * Ensure that 'Enable Secure Boot for Linux' is marked in case
     'SCSI Load' is selected at the HMCs Load task and Activation Profile.

   * Perform an Ubuntu Server installation, either 20.04 or 22.04
     (latest ISO).
     It will be a secure boot installation by default in case
     'Enable Secure Boot for Linux' was marked.

   * Check sysfs:
     /sys/firmware/ipl/has_secure
    '1' indicates hw support for secure boot, otherwise '0'
     /sys/firmware/ipl/secure
    '1' indicates that secure IPL was successful, otherwise '0'

   * Navigate to the HMC task 'System information'
     and check the active firmware release.

   * Ensure that Ubuntu is still bootable in secure-boot mode
     with the updated firmware active,
     by for example doing a reboot after the firmware upgrade.

   * There is also a way to test the trailer on systems that do not
 have the updated firmware yet - in this case use the following script:
 https://launchpadlibrarian.net/633126861/check_sb_trailer.sh

  [Where problems could occur]

   * The 'trailer' might be broken, invalid or in a wrong format
     and can't be identified or read properly,
     or may cause issues while compressing/decompressing the kernel.

   * In worst case secure boot might become broken,
     even on systems that are still on the unpatched firmware level.

   * Or secure boot will become broken in general.

  [Other Info]

   * The above commit was upstream accepted with v6.1-rc3.

   * And it got tagged for upstream stable with:
     "Cc:  # 5.2+"

   * But since this bug is marked as critical, and the patch is relatively
     short, traceable and s390x-specific, I'll go ahead and submit this
     patch for Jammy and Focal ahead of upstream stable.

   * Since on focal file 'vmlinux.lds.S' is at a different location
     'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
     and the context is slightly different, the backport is needed.

   * It's planned to have kernel 6.2 in lunar (23.04), hence it will have
     the patch incl. when at the planned target level.

  __

  Description:   boot: Add secure boot trailer
  Symptom:   Secure boot of Linux will no longer be possible with an 
upcoming
     IBM Z firmware update.

  Problem:   New IBM Z firmware requires signed bootable images to contain a
     trailing data block with a specific format.

  Solution:  Add the trailing data block to the Linux kernel image.

  Reproduction:  Apply latest firmware, perform IPL with Secure Boot
  enabled.

  Fix:   available upstream with
  Upstream-ID:   aa127a069ef312aca02b730d5137e1778d0c3ba7

  Preventive:yes

  Date:  2022-10-27
  Author:Peter Oberparleiter 
  Component: kernel

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


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

[Kernel-packages] [Bug 1996198] Re: Fix rfkill causing soft blocked wifi

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-iot/5.4.0-1011.13
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: kernel-spammed-focal-linux-iot

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

Title:
  Fix rfkill causing soft blocked wifi

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-6.0 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Need this patch in so a BIOS upgrade won't cause issues on HP laptops.

  commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a
  Author: Jorge Lopez 
  Date:   Fri Oct 28 10:55:27 2022 -0500

   platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi

  After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded
  strange char "^@" which printed out every second and makes login
  nearly impossible. Also the below messages were shown both in console
  and journal/dmesg every second:

  usb 1-3: Device not responding to setup address.
  usb 1-3: device not accepting address 4, error -71
  usb 1-3: device descriptor read/all, error -71
  usb usb1-port3: unable to enumerate USB device

  Wifi is soft blocked by checking rfkill. When unblocked manually,
  after few seconds it would be soft blocked again. So I was suspecting
  something triggered rfkill to soft block wifi.  At the end it was
  fixed by removing hp_wmi module.

  The root cause is the way hp-wmi driver handles command 1B on
  post-2009 BIOS.  In pre-2009 BIOS, command 1Bh return 0x4 to indicate
  that BIOS no longer controls the power for the wireless devices.

  Signed-off-by: Jorge Lopez 
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468
  Reviewed-by: Mario Limonciello 
  Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com
  Cc: sta...@vger.kernel.org
  Reviewed-by: Hans de Goede 
  Signed-off-by: Hans de Goede 

  [Test case]

  test on a HP laptop with the new BIOS

  [Where problems could occur]

  from the commit:
    * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that
    * BIOS no longer controls the power for the wireless
    * devices. All features supported by this command will no
    * longer be supported.

  anyone running a laptop with obsolete pre-2009 BIOS probably won't
  notice the missing feature at this point.

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


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

[Kernel-packages] [Bug 1996892] Re: Expose built-in trusted and revoked certificates

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-iot/5.4.0-1011.13
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 removed: verification-done-focal
** Tags added: kernel-spammed-focal-linux-iot verification-needed-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/1996892

Title:
  Expose built-in trusted and revoked certificates

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Confirmed

Bug description:
  [ Impact ]

   * Kernels have a set of builtin trusted and revoked certificates as a bundle
   * It is not very easy to access them, one needs to either download linux 
kernel package source code; or boot the kernel look up builtin hashes; and then 
find certificates externally
   * It would be more convenient for inspection to expose these in the 
buildinfo package, which already exposes auxiliary kernel information

  [ Test Plan ]

   * sudo apt install linux-buildinfo-$(uname -r)
   * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and 
contains livepatch cert
   * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists 
and contains 2012 cert

  Example output:
  $ grep Subject: -r usr/lib/linux
  usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: CN = 
Canonical Ltd. Live Patch Signing
  usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: C = GB, 
ST = Isle of Man, L = Douglas, O = Canonical Ltd., CN = Canonical Ltd. Kernel 
Module Signing
  usr/lib/linux/5.19.0-24-generic/canonical-revoked-certs.pem:Subject: 
C = GB, ST = Isle of Man, O = Canonical Ltd., OU = Secure Boot, CN = Canonical 
Ltd. Secure Boot Signing

  
  [ Where problems could occur ]

   * buildinfo is an auxiliary package not installed by default, but
  used by developer tooling and packaging.

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


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

[Kernel-packages] [Bug 2002432] Re: X11 not started during boot (intel: waited 2020 ms for i915.ko driver to load)

[Daniel van Vugt]

Please also remember to delete /root/xorg.conf.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/2002432

Title:
  X11 not started during boot (intel: waited 2020 ms for i915.ko driver
  to load)

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Won't Fix

Bug description:
  After update from Ubuntu 20.04->22.10 X11 was not correctly updated. I
  can only boot into recovery mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  Uname: Linux 5.15.0-57-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Jan 10 18:45:16 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call/1.2.2, 5.15.0-56-generic, x86_64: installed
   acpi-call/1.2.2, 5.15.0-57-generic, x86_64: installed
   tp_smapi/0.43, 5.15.0-56-generic, x86_64: installed
   tp_smapi/0.43, 5.15.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:501e]
  InstallationDate: Installed on 2015-11-17 (2611 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20AV002WXS
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=23ec64aa-726f-4a3c-b489-2dbbc0a36528 ro recovery nomodeset 
dis_ucode_ldr i915.enable_hangcheck=0
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2018
  dmi.bios.release: 1.93
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J4ET93WW(1.93)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AV002WXS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ4ET93WW(1.93):bd05/30/2018:br1.93:svnLENOVO:pn20AV002WXS:pvrThinkPadL540:rvnLENOVO:rn20AV002WXS:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AV_BU_Think_FM_ThinkPadL540:
  dmi.product.family: ThinkPad L540
  dmi.product.name: 20AV002WXS
  dmi.product.sku: LENOVO_MT_20AV_BU_Think_FM_ThinkPad L540
  dmi.product.version: ThinkPad L540
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1
  xserver.bootTime: Tue Jan 10 18:24:35 2023
  xserver.configfile: /root/xorg.conf.new
  xserver.devices:
   
  xserver.errors: Server terminated with error (2). Closing log file.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:21.1.3-2ubuntu2.5

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


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

[Kernel-packages] [Bug 2002432] Re: X11 not started during boot (intel: waited 2020 ms for i915.ko driver to load)

[Daniel van Vugt]

Also your logs are all from recovery mode so that explains why there's
no working graphics driver there.

Can you provide a log from a non-recovery boot? Try:

  journalctl -b-1 > prevboot1.txt
  journalctl -b-2 > prevboot2.txt
  journalctl -b-3 > prevboot3.txt

and attach the resulting text files here.

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

** Tags removed: regression-update

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

Title:
  X11 not started during boot (intel: waited 2020 ms for i915.ko driver
  to load)

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Won't Fix

Bug description:
  After update from Ubuntu 20.04->22.10 X11 was not correctly updated. I
  can only boot into recovery mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  Uname: Linux 5.15.0-57-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Jan 10 18:45:16 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call/1.2.2, 5.15.0-56-generic, x86_64: installed
   acpi-call/1.2.2, 5.15.0-57-generic, x86_64: installed
   tp_smapi/0.43, 5.15.0-56-generic, x86_64: installed
   tp_smapi/0.43, 5.15.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:501e]
  InstallationDate: Installed on 2015-11-17 (2611 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20AV002WXS
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=23ec64aa-726f-4a3c-b489-2dbbc0a36528 ro recovery nomodeset 
dis_ucode_ldr i915.enable_hangcheck=0
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2018
  dmi.bios.release: 1.93
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J4ET93WW(1.93)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AV002WXS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ4ET93WW(1.93):bd05/30/2018:br1.93:svnLENOVO:pn20AV002WXS:pvrThinkPadL540:rvnLENOVO:rn20AV002WXS:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AV_BU_Think_FM_ThinkPadL540:
  dmi.product.family: ThinkPad L540
  dmi.product.name: 20AV002WXS
  dmi.product.sku: LENOVO_MT_20AV_BU_Think_FM_ThinkPad L540
  dmi.product.version: ThinkPad L540
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1
  xserver.bootTime: Tue Jan 10 18:24:35 2023
  xserver.configfile: /root/xorg.conf.new
  xserver.devices:
   
  xserver.errors: Server terminated with error (2). Closing log file.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:21.1.3-2ubuntu2.5

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


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

[Kernel-packages] [Bug 2002432] Re: X11 not started during boot, crashed

[Daniel van Vugt]

Thanks for the bug report.

The problem preventing Xorg from loading appears to be:

  intel: waited 2020 ms for i915.ko driver to load

But 'intel' is an old buggy driver that nobody should be using. Please
remove any custom configs in /root/xorg.conf.new and
/usr/share/X11/xorg.conf.d that are loading the 'intel' driver and
reboot. The correct Xorg driver that should be loaded by default is
called 'modesetting'.


** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu)

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: New => Won't Fix

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

** Summary changed:

- X11 not started during boot, crashed
+ X11 not started during boot (intel: waited 2020 ms for i915.ko driver to load)

** Tags added: regression-update

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

Title:
  X11 not started during boot (intel: waited 2020 ms for i915.ko driver
  to load)

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Won't Fix

Bug description:
  After update from Ubuntu 20.04->22.10 X11 was not correctly updated. I
  can only boot into recovery mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  Uname: Linux 5.15.0-57-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Jan 10 18:45:16 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call/1.2.2, 5.15.0-56-generic, x86_64: installed
   acpi-call/1.2.2, 5.15.0-57-generic, x86_64: installed
   tp_smapi/0.43, 5.15.0-56-generic, x86_64: installed
   tp_smapi/0.43, 5.15.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:501e]
  InstallationDate: Installed on 2015-11-17 (2611 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20AV002WXS
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=23ec64aa-726f-4a3c-b489-2dbbc0a36528 ro recovery nomodeset 
dis_ucode_ldr i915.enable_hangcheck=0
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2018
  dmi.bios.release: 1.93
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J4ET93WW(1.93)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AV002WXS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ4ET93WW(1.93):bd05/30/2018:br1.93:svnLENOVO:pn20AV002WXS:pvrThinkPadL540:rvnLENOVO:rn20AV002WXS:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AV_BU_Think_FM_ThinkPadL540:
  dmi.product.family: ThinkPad L540
  dmi.product.name: 20AV002WXS
  dmi.product.sku: LENOVO_MT_20AV_BU_Think_FM_ThinkPad L540
  dmi.product.version: ThinkPad L540
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1
  xserver.bootTime: Tue Jan 10 18:24:35 2023
  xserver.configfile: /root/xorg.conf.new
  xserver.devices:
   
  xserver.errors: Server terminated with error (2). Closing log file.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:21.1.3-2ubuntu2.5

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


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

[Kernel-packages] [Bug 1987618] Re: [jammy mlx5] Slow outbound N/S TCP connections for instances on gateways

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

Title:
  [jammy mlx5] Slow outbound N/S TCP connections for instances on
  gateways

Status in linux package in Ubuntu:
  Expired

Bug description:
  Charmed OpenStack on Jammy.

  Hardware offloaded instances that reside on the hypervisor which is
  also the active OVN gateway for their network have degraded
  connectivity.

  $ time wget --debug -O /dev/null http://nova.clouds.archive.ubuntu.com/ubuntu/
  Setting --output-document (outputdocument) to /dev/null
  DEBUG output created by Wget 1.21.2 on linux-gnu.

  Reading HSTS entries from /home/ubuntu/.wget-hsts
  URI encoding = ‘UTF-8’
  --2022-08-25 07:16:54--  http://nova.clouds.archive.ubuntu.com/ubuntu/
  Resolving nova.clouds.archive.ubuntu.com (nova.clouds.archive.ubuntu.com)... 
91.189.91.121, 185.125.190.38, 185.125.190.41, ...
  Caching nova.clouds.archive.ubuntu.com => 91.189.91.121 185.125.190.38 
185.125.190.41 91.189.91.122 2001:67c:1562::29 2620:2d:4000:1::1b 
2620:2d:4000:1::18 2001:67c:1562::26
  Connecting to nova.clouds.archive.ubuntu.com 
(nova.clouds.archive.ubuntu.com)|91.189.91.121|:80... connected.
  Created socket 4.
  Releasing 0x55ef05654490 (new refcount 1).

  ---request begin---
  GET /ubuntu/ HTTP/1.1
  Host: nova.clouds.archive.ubuntu.com
  User-Agent: Wget/1.21.2
  Accept: */*
  Accept-Encoding: identity
  Connection: Keep-Alive

  ---request end---
  HTTP request sent, awaiting response... 
  ---response begin---
  HTTP/1.1 200 OK
  Date: Thu, 25 Aug 2022 07:16:54 GMT
  Server: Apache/2.4.29 (Ubuntu)
  Vary: Accept-Encoding
  Content-Length: 1779
  Keep-Alive: timeout=5, max=100
  Connection: Keep-Alive
  Content-Type: text/html;charset=UTF-8

  ---response end---
  200 OK
  Registered socket 4 for persistent reuse.
  URI content encoding = ‘UTF-8’
  Length: 1779 (1.7K) [text/html]
  Saving to: ‘/dev/null’

  /dev/null
  
100%[>]
  1.74K  --.-KB/sin 0.07s

  2022-08-25 07:16:59 (24.3 KB/s) - ‘/dev/null’ saved [1779/1779]

  
  real  0m5.591s
  user  0m0.000s
  sys   0m0.005s

  $ sudo tcpdump -nevi ens3 not port 22
  07:16:54.017265 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 
(0x0800), length 74: (tos 0x0, ttl 64, id 50207, offset 0, flags [DF], proto 
TCP (6), length 60)
  10.42.1.8.43060 > 91.189.91.121.80: Flags [S], cksum 0xc296 (incorrect -> 
0x4190), seq 2905559525, win 62314, options [mss 8902,sackOK,TS val 4081686695 
ecr 0,nop,wscale 7], length 0
  07:16:54.091378 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 
(0x0800), length 74: (tos 0x0, ttl 58, id 0, offset 0, flags [DF], proto TCP 
(6), length 60)
  91.189.91.121.80 > 10.42.1.8.43060: Flags [S.], cksum 0x809d (correct), 
seq 3404088064, ack 2905559526, win 65160, options [mss 1460,sackOK,TS val 
932285789 ecr 4081686695,nop,wscale 7], length 0
  07:16:54.091402 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 
(0x0800), length 66: (tos 0x0, ttl 64, id 50208, offset 0, flags [DF], proto 
TCP (6), length 52)
  10.42.1.8.43060 > 91.189.91.121.80: Flags [.], cksum 0xc28e (incorrect -> 
0xabc0), ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 932285789], 
length 0
  07:16:54.091512 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 
(0x0800), length 218: (tos 0x0, ttl 64, id 50209, offset 0, flags [DF], proto 
TCP (6), length 204)
  10.42.1.8.43060 > 91.189.91.121.80: Flags [P.], cksum 0xc326 (incorrect 
-> 0x7d0c), seq 1:153, ack 1, win 487, options [nop,nop,TS val 4081686770 ecr 
932285789], length 152: HTTP, length: 152
GET /ubuntu/ HTTP/1.1
Host: nova.clouds.archive.ubuntu.com
User-Agent: Wget/1.21.2
Accept: */*
Accept-Encoding: identity
Connection: Keep-Alive

  07:16:54.166170 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 
(0x0800), length 66: (tos 0x0, ttl 58, id 15660, offset 0, flags [DF], proto 
TCP (6), length 52)
  91.189.91.121.80 > 10.42.1.8.43060: Flags [.], cksum 0xaac7 (correct), 
ack 153, win 508, options [nop,nop,TS val 932285865 ecr 4081686770], length 0
  07:16:59.171924 fa:16:3e:47:3a:ad > fa:16:3e:6d:94:75, ethertype IPv4 
(0x0800), length 66: (tos 0x0, ttl 58, id 15669, offset 0, flags [DF], proto 
TCP (6), length 52)
  91.189.91.121.80 > 10.42.1.8.43060: Flags [F.], cksum 0x8f61 (correct), 
seq 2008, ack 153, win 508, options [nop,nop,TS val 932290871 ecr 4081686770], 
length 0
  07:16:59.171956 fa:16:3e:6d:94:75 > fa:16:3e:47:3a:ad, ethertype IPv4 
(0x0800), length 78: (tos 0x0, ttl 64, id 50210, offset 0, flags [DF], proto 
TCP (6), length 64)
  10.42.1.8.43060 > 

[Kernel-packages] [Bug 1992393] Re: Crashed 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/1992393

Title:
  Crashed boot

Status in linux package in Ubuntu:
  Expired

Bug description:
  After updating Linux Mint 21, along with kernal updates from 5.15.0-48.
  Update hung near end of kernal update and never moved. Rebooted and system 
would hang at flashing courser after booting to just after the login and pw and 
would just hang there.
  Had to start in emergency mode and revert to kernal 5.15.0-48.

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


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

[Kernel-packages] [Bug 2002467] [NEW] ThinkPad L14 Gen 3 blank laptop screen on bootup

[Paul Gear]

Public bug reported:

When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a
Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank
shortly after bootup.

As far as I can tell (the screen blanks pretty quickly, so I'm not 100%
sure), the last message before the screen disappears is this one:

Jan  9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu
from EFI VGA

Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine,
so this appears to be a regression in whatever changes there were in the
framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.

I think this should be high priority, because it gives the impression
that the system is completely borked, when in actuality it's probably
just waiting for me to enter my drive encryption password.

If I type the encryption password, it seems to progress to starting the
system (the microphone mute LED comes on as expected), but even X
starting does not turn the screen back on.  Switching to the frame
buffer console with Ctrl-Alt-Fx does nothing.

** Affects: linux-signed-oem-5.10 (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a
  Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank
  shortly after bootup.
  
  As far as I can tell (the screen blanks pretty quickly, so I'm not 100%
  sure), the last message before the screen disappears is this one:
  
  Jan  9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu
  from EFI VGA
  
  Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine,
  so this appears to be a regression in whatever changes there were in the
  framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.
  
- I'm going to mark this as high, because it gives the impression that the
- system is completely borked, when in actuality it's probably just
- waiting for me to enter my drive encryption password.
+ I think this should be high priority, because it gives the impression
+ that the system is completely borked, when in actuality it's probably
+ just waiting for me to enter my drive encryption password.

** Summary changed:

- Blank screen on bootup
+ ThinkPad L14 Gen 3 blank screen on bootup

** Description changed:

  When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a
  Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank
  shortly after bootup.
  
  As far as I can tell (the screen blanks pretty quickly, so I'm not 100%
  sure), the last message before the screen disappears is this one:
  
  Jan  9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu
  from EFI VGA
  
  Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine,
  so this appears to be a regression in whatever changes there were in the
  framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.
  
  I think this should be high priority, because it gives the impression
  that the system is completely borked, when in actuality it's probably
  just waiting for me to enter my drive encryption password.
+ 
+ If I type the encryption password, it seems to progress to starting the
+ system (the microphone mute LED comes on as expected), but even X
+ starting does not turn the screen back on.

** Summary changed:

- ThinkPad L14 Gen 3 blank screen on bootup
+ ThinkPad L14 Gen 3 blank laptop screen on bootup

** Description changed:

  When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a
  Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank
  shortly after bootup.
  
  As far as I can tell (the screen blanks pretty quickly, so I'm not 100%
  sure), the last message before the screen disappears is this one:
  
  Jan  9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu
  from EFI VGA
  
  Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine,
  so this appears to be a regression in whatever changes there were in the
  framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27.
  
  I think this should be high priority, because it gives the impression
  that the system is completely borked, when in actuality it's probably
  just waiting for me to enter my drive encryption password.
  
  If I type the encryption password, it seems to progress to starting the
  system (the microphone mute LED comes on as expected), but even X
- starting does not turn the screen back on.
+ starting does not turn the screen back on.  Switching to the frame
+ buffer console with Ctrl-Alt-Fx does nothing.

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

Title:
  ThinkPad L14 Gen 3 blank laptop screen on bootup

Status in linux-signed-oem-5.10 package in Ubuntu:
  New

Bug description:
  When booting 

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

[Ubuntu SRU Bot]

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

systemd/251.4-1ubuntu7 (amd64, ppc64el)


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/kinetic/update_excuses.html#linux-meta

[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:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
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:
  Won't Fix
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:
  Won't Fix
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 1998419] Re: Gnome doesn't run smooth when performing normal usage with RPL-P CPU

[Andy Chi]

Enable proposed pocket on TRBR-DVT1-C3_202211-30859, and install linux-
oem-6.1/6.1.0-1004.4, the screen movement works well.

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

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

Title:
  Gnome doesn't run smooth when performing normal usage with RPL-P CPU

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  Gnome desktop doesn't run smooth when performing normal usage, the cursor 
usually stops working and stuck, and then becomes back to normal.

  [Fix]
  Can't reproduce this issue with drm-tip kernel, so found below commit after 
bisected
  dc73ac63e63a drm/i915/rpl-p: Add stepping info

  [Test]
  Verified on the RPL-P machine and the cursor/window move smoothly.

  [Where problems could occur]
  Adding info for new RPL-P chipset should be pretty safe.

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


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

[Kernel-packages] [Bug 1997946] Re: [SRU] Support soundwire speaker AMP-ALC1318 codec

[Kai-Chuan Hsieh]

reply #4

The diff is because that quilt suggests to do quilt refresh on 
0005-acp6x-add-initial-support-for-AMD-Yellow-Carp-ACP6x.patch.
I did the comparison to the modified files which changed by old and new 
0005-acp6x-add-initial-support-for-AMD-Yellow-Carp-ACP6x.patch, there is no 
difference. I think it can help to apply patch more cleanly if someone would 
like to propose another SRU next time, so I include it into the debdiff too.

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

Title:
  [SRU] Support soundwire speaker AMP-ALC1318 codec

Status in OEM Priority Project:
  Triaged
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

   * Add ALC1318 speaker codec ucm file
   * Make internal speaker working on the platform with the codec

  [ Test Plan ]

   * On platform with the codec, the internal speaker should work after
     boot into Ubuntu

  [ Where problems could occur ]

   * The config only be executed on the platform with the codec exported

   * It needs to add the codec combination to the machine driver to make the 
function work
 ex. 
https://github.com/thesofproject/linux/blob/topic/sof-dev/sound/soc/intel/common/soc-acpi-intel-rpl-match.c#L225

  [ Other Info ]

   * Upstream commit soundwire speaker AMP-ALC1318 codec.
     
https://github.com/alsa-project/alsa-ucm-conf/commit/c82c400fb653292bbf0570e278d60e1ba14cc341

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


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

[Kernel-packages] [Bug 1997946] Re: [SRU] Support soundwire speaker AMP-ALC1318 codec

[Launchpad Bug Tracker]

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu3.1

---
alsa-ucm-conf (1.2.6.3-1ubuntu3.1) lunar; urgency=medium

  * Backport patch for speaker AMP-ALC1318 support. (LP: #1997946)

 -- Kai-Chuan Hsieh   Mon, 26 Dec 2022
15:12:24 +0800

** Changed in: alsa-ucm-conf (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Support soundwire speaker AMP-ALC1318 codec

Status in OEM Priority Project:
  Triaged
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

   * Add ALC1318 speaker codec ucm file
   * Make internal speaker working on the platform with the codec

  [ Test Plan ]

   * On platform with the codec, the internal speaker should work after
     boot into Ubuntu

  [ Where problems could occur ]

   * The config only be executed on the platform with the codec exported

   * It needs to add the codec combination to the machine driver to make the 
function work
 ex. 
https://github.com/thesofproject/linux/blob/topic/sof-dev/sound/soc/intel/common/soc-acpi-intel-rpl-match.c#L225

  [ Other Info ]

   * Upstream commit soundwire speaker AMP-ALC1318 codec.
     
https://github.com/alsa-project/alsa-ucm-conf/commit/c82c400fb653292bbf0570e278d60e1ba14cc341

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


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

[Kernel-packages] [Bug 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware -
20220923.gitf09bebf3-0ubuntu1.3

---
linux-firmware (20220923.gitf09bebf3-0ubuntu1.3) kinetic; urgency=medium

  * Fix The Bluetooth connection cannot be established between two Ubuntu 22.04 
systems with Realtek 8821 (LP: #1999491)
- linux-firmware: rtl_bt: Update RTL8821C BT(USB I/F) FW to 0x75b8_f098

linux-firmware (20220923.gitf09bebf3-0ubuntu1.2) kinetic; urgency=medium

  * Mediatek WLAN RZ616(MT7922) SAR table control (LP: #1997200)
- linux-firmware: update firmware for MT7922 WiFi device
- linux-firmware: update firmware for mediatek bluetooth chip (MT7922)
  * New DMCUB FW for AMD amdgpu DCN 3.1.6 (LP: #1998468)
- amdgpu: update DMCUB firmware for DCN 3.1.6

 -- Juerg Haefliger   Tue, 13 Dec 2022
10:41:42 +0100

** Changed in: linux-firmware (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  Mediatek WLAN RZ616(MT7922) SAR table control

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  In order to make sure the amount of RF energy being absorbed by our bodies is 
safe according to the FCC’s guidelines, products must undergo and pass SAR 
testing.

  [Fix]
  Add ACPI SAR table control to pass the testing.

  [Test]
  the unit is 0.5dBm in following:

  Without the SAR table control:
  $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user
  CCK (user)  :N.AN.AN.AN.A
  OFDM (user) : 40 40 40 40 40 40 40 40
  HT20 (user) : 40 40 40 40 40 40 40 40
  HT40 (user) : 40 40 40 40 40 40 40 40 
40
  VHT20 (user): 40 40 40 40 40 40 40 40 
40 40  0  0
  VHT40 (user): 40 40 40 40 40 40 40 40 
40 40  0  0
  VHT80 (user): 40 40 40 40 40 40 40 40 
40 40  0  0
  VHT160 (user)   : 40 40 40 40 40 40 40 40 
40 40  0  0
  HE26 (user) : 40 40 40 40 40 40 40 40 
40 40 40 40
  HE52 (user) : 40 40 40 40 40 40 40 40 
40 40 40 40
  HE106 (user): 40 40 40 40 40 40 40 40 
40 40 40 40
  HE242 (user): 40 40 40 40 40 40 40 40 
40 40 40 40
  HE484 (user): 40 40 40 40 40 40 40 40 
40 40 40 40
  HE996 (user): 40 40 40 40 40 40 40 40 
40 40 40 40
  HE996x2 (user)  : 40 40 40 40 40 40 40 40 
40 40 40 40

  After enabled SAR table control:
  $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user
  CCK (user)  :N.AN.AN.AN.A
  OFDM (user) : 26 26 26 26 26 26 26 26
  HT20 (user) : 26 26 26 26 26 26 26 26
  HT40 (user) : 26 26 26 26 26 26 26 26 
26
  VHT20 (user): 26 26 26 26 26 26 26 26 
26 26  0  0
  VHT40 (user): 26 26 26 26 26 26 26 26 
26 26  0  0
  VHT80 (user): 26 26 26 26 26 26 26 26 
26 26  0  0
  VHT160 (user)   : 26 26 26 26 26 26 26 26 
26 26  0  0
  HE26 (user) : 26 26 26 26 26 26 26 26 
26 26 26 26
  HE52 (user) : 26 26 26 26 26 26 26 26 
26 26 26 26
  HE106 (user): 26 26 26 26 26 26 26 26 
26 26 26 26
  HE242 (user): 26 26 26 26 26 26 26 26 
26 26 26 26
  HE484 (user): 26 26 26 26 26 26 26 26 
26 26 26 26
  HE996 (user): 26 26 26 26 26 26 26 26 
26 26 26 26
 

[Kernel-packages] [Bug 1998468] Re: New DMCUB FW for AMD amdgpu DCN 3.1.6

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware -
20220923.gitf09bebf3-0ubuntu1.3

---
linux-firmware (20220923.gitf09bebf3-0ubuntu1.3) kinetic; urgency=medium

  * Fix The Bluetooth connection cannot be established between two Ubuntu 22.04 
systems with Realtek 8821 (LP: #1999491)
- linux-firmware: rtl_bt: Update RTL8821C BT(USB I/F) FW to 0x75b8_f098

linux-firmware (20220923.gitf09bebf3-0ubuntu1.2) kinetic; urgency=medium

  * Mediatek WLAN RZ616(MT7922) SAR table control (LP: #1997200)
- linux-firmware: update firmware for MT7922 WiFi device
- linux-firmware: update firmware for mediatek bluetooth chip (MT7922)
  * New DMCUB FW for AMD amdgpu DCN 3.1.6 (LP: #1998468)
- amdgpu: update DMCUB firmware for DCN 3.1.6

 -- Juerg Haefliger   Tue, 13 Dec 2022
10:41:42 +0100

** Changed in: linux-firmware (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  New DMCUB FW for AMD amdgpu DCN 3.1.6

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Released
Status in linux-firmware source package in Lunar:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  Multiple issues in DP alt mode, PSR-SU(Panel Self Refresh–Selective
  Update), and HDMI signal integrity.

  [Fix]

  Upstream commit b0f995cd61cd ("amdgpu: update DMCUB firmware for DCN
  3.1.6") that updates binary firmware.

  [Test Case]

  Can only be verified with dedicated equipment from vendor.

  [Where problems could occur]

  Binary firmware, everything can go wrong.

  [Other Info]

  Already in korg upstream, included in Lunar, too. Only Jammy and
  Kinetic will be nominated for fix.

  == original bug report ==

  Some fixes for DP alt mode and PSR-SU(Panel Self Refresh–Selective
  Update), and also improve HDMI signal integrity. This FW would be
  tuning PHY of HDMI to enhance signal integrity in eye diagram to reach
  HDMI spec(2.0/1.4b), and also avoid any risk on monitor with multiple
  resolutions over HDMI output.

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=b0f995cd61cd29e7eee1dc22aeeacb2eadc21227

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


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

[Kernel-packages] [Bug 1999491] Re: Fix The Bluetooth connection cannot be established between two Ubuntu 22.04 systems with Realtek 8821

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware -
20220923.gitf09bebf3-0ubuntu1.3

---
linux-firmware (20220923.gitf09bebf3-0ubuntu1.3) kinetic; urgency=medium

  * Fix The Bluetooth connection cannot be established between two Ubuntu 22.04 
systems with Realtek 8821 (LP: #1999491)
- linux-firmware: rtl_bt: Update RTL8821C BT(USB I/F) FW to 0x75b8_f098

linux-firmware (20220923.gitf09bebf3-0ubuntu1.2) kinetic; urgency=medium

  * Mediatek WLAN RZ616(MT7922) SAR table control (LP: #1997200)
- linux-firmware: update firmware for MT7922 WiFi device
- linux-firmware: update firmware for mediatek bluetooth chip (MT7922)
  * New DMCUB FW for AMD amdgpu DCN 3.1.6 (LP: #1998468)
- amdgpu: update DMCUB firmware for DCN 3.1.6

 -- Juerg Haefliger   Tue, 13 Dec 2022
10:41:42 +0100

** Changed in: linux-firmware (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  Fix The Bluetooth connection cannot be established between two Ubuntu
  22.04 systems with Realtek 8821

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  The Bluetooth connection cannot be established between two Ubuntu 22.04 
systems with Realtek 8821.

  [Fix]
  Use the updated firmware for rtl8821c to fix issue.

  [Test]
  1. Prepare two Ubuntu 22.04 systems with Realtek 8821.
  2. Open Bluetooth Settings and launch research available device automatically.
  3. Found this two systems are visible in research list for connection, 
Bluetooth connection can be established normally without problem.

  [Where problems could occur]
  It's binary so anything would happen.

  [Other Info]
  This firmware has existed in Lunar.

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


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

[Kernel-packages] [Bug 1987829] Re: LG Gram 12gen high CPU use when USB-C/TB is in use

[Cristian Cocos]

Confirmed on Ubuntu 22.10, same LG Gram computer (17Z90Q).

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

Title:
  LG Gram 12gen high CPU use when USB-C/TB is in use

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

Bug description:
  LG Gram laptop 17Z90Q with a Core i7-1260P CPU.

  Whenever an external monitor is connected to USB-C/Thunderbolt 4,
  average load goes above 3.0 and the machine is getting very hot.

  Output from top -H shows a lot of kworker CPU usage:

  top - 11:45:06 up 33 min,  2 users,  load average: 3,30, 3,08, 2,79
  Threads: 1442 total,   2 running, 1440 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0,1 us,  3,7 sy,  0,0 ni, 96,1 id,  0,0 wa,  0,0 hi,  0,1 si,  0,0 
st
  MiB Mem :  15684,6 total,   8510,2 free,   2580,8 used,   4593,6 buff/cache
  MiB Swap:   3815,0 total,   3815,0 free,  0,0 used.  11326,9 avail Mem 

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ WCHAN  
COMMAND
 7766 root  20   0   0  0  0 R  19,8   0,0   0:56.05 
worker_th+ kworker/0:2-events
  196 root  20   0   0  0  0 D  15,8   0,0   1:18.12 
ec_guard   kworker/u32:2+USBC000:00-con0
10237 root  20   0   0  0  0 I  12,9   0,0   0:26.44 
worker_th+ kworker/0:0-events
 1027 root  20   0   0  0  0 I   6,6   0,0   0:43.30 
worker_th+ kworker/1:3-events
10971 root  20   0   0  0  0 I   4,0   0,0   0:00.20 
worker_th+ kworker/15:0-events
  175 root  20   0   0  0  0 I   2,3   0,0   0:03.24 
worker_th+ kworker/11:1-events
 2410 root  20   0   0  0  0 I   1,7   0,0   0:05.49 
worker_th+ kworker/9:3-events

  Perf shows a lot of time spent inside
  handle_irq_event/acpi_ev_gpe_detect/acpi_hw_gpe_read.

  Additionally, kernel log is getting spammed with these lines every 4
  seconds (but also without any USB-C device attached):

  [  223.514304] ACPI Error: No handler for Region [XIN1] (f2ad4f1f) 
[UserDefinedRegion] (20210730/evregion-130)
  [  223.514323] ACPI Error: Region UserDefinedRegion (ID=143) has no handler 
(20210730/exfldio-261)

  [  223.514337] 
 Initialized Local Variables for Method [_TMP]:
  [  223.514339]   Local0: 21495082Integer 
0034

  [  223.514349] No Arguments are initialized for method [_TMP]

  [  223.514354] ACPI Error: Aborting method
  \_SB.PC00.LPCB.LGEC.SEN2._TMP due to previous error (AE_NOT_EXIST)
  (20210730/psparse-529)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-46-generic 5.15.0-46.49
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  me 1678 F pulseaudio
   /dev/snd/controlC1:  me 1678 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Aug 26 11:57:05 2022
  InstallationDate: Installed on 2022-08-25 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LG Electronics 17Z90Q-G.AA78N
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=e2f96916-a67c-432e-b687-730071271216 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.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2022
  dmi.bios.release: 0.1
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: A1ZG0380 X64
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 17Z90Q
  dmi.board.vendor: LG Electronics
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 33.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrA1ZG0380X64:bd07/06/2022:br0.1:efr33.0:svnLGElectronics:pn17Z90Q-G.AA78N:pvr0.1:rvnLGElectronics:rn17Z90Q:rvrFAB1:cvnLGElectronics:ct10:cvr0.1:skuEVO:
  dmi.product.family: LG gram PC
  dmi.product.name: 17Z90Q-G.AA78N
  dmi.product.sku: EVO
  dmi.product.version: 0.1
  dmi.sys.vendor: LG Electronics

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


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

[Kernel-packages] [Bug 1990294] Re: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..."

[Taihsiang Ho]

Similar to comment #6. Here is the log of another Mt. Jade with AltraMax
reproducing this issue with Ubuntu kernel.

[8.308100] [ cut here ]^M
[8.308185] GICv3: CPU248: using allocated LPI pending table 
@0x0800026a^M
[8.314742] Dying CPU not properly vacated!^M
[   16.480898] WARNING: CPU: 0 PID: 1 at kernel/sched/core.c:9215 
sched_cpu_dying+0x1d0/0x2a0^M
[   16.493557] Modules linked in:^M
[   16.496658] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.15.0-43-generic 
#46~20.04.1-Ubuntu^M
[   16.505065] pstate: 604000c9 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)^M
[   16.512146] pc : sched_cpu_dying+0x1d0/0x2a0^M
[   16.516483] lr : sched_cpu_dying+0x1d0/0x2a0^M
[   16.520822] sp : 8881bbe0^M
[   16.524187] x29: 8881bbe0 x28: c747c462da80 x27: 
^M
[   16.531443] x26: 78f67d08a000 x25: 00f8 x24: 
403e40f12728^M
[   16.538703] x23: c747c4632618 x22:  x21: 
00f8^M
[   16.545961] x20: c747c3e99100 x19: 403e40f23100 x18: 
0014^M
[   16.553222] x17: 6136323030303830 x16: 3030303078304020 x15: 
656c62617420676e^M
[   16.560480] x14: 69646e6570204950 x13: 3030303061363230 x12: 
3030383030303030^M
[   16.567738] x11: 78304020656c6261 x10: 7420676e69646e65 x9 : 
c747c1f639a0^M
[   16.574995] x8 : 6c6c6120676e6973 x7 : 205d353831383033 x6 : 
c000fffe^M
[   16.582255] x5 : 0017ffe8 x4 :  x3 : 
8881b8c8^M
[   16.589512] x2 :  x1 :  x0 : 
^M
[   16.596772] Call trace:^M
[   16.599252]  sched_cpu_dying+0x1d0/0x2a0^M
[   16.603238]  cpuhp_invoke_callback+0x14c/0x5a8^M
[   16.607757]  cpuhp_invoke_callback_range+0x5c/0xb8^M
[   16.612627]  _cpu_up+0x234/0x360^M
[   16.615904]  cpu_up+0xb8/0x110^M
[   16.619003]  bringup_nonboot_cpus+0x7c/0xb0^M
[   16.623254]  smp_init+0x3c/0x98^M
[   16.626444]  kernel_init_freeable+0x1a4/0x39c^M
[   16.630871]  kernel_init+0x2c/0x158^M
[   16.634415]  ret_from_fork+0x10/0x20^M
[   16.638046] ---[ end trace b4903e61a7ade0b4 ]---^M
[   16.642739] CPU248 enqueued tasks (0 total):^M

** Attachment added: "kopter.log"
   
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1990294/+attachment/5640544/+files/kopter.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/1990294

Title:
  Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot
  services..."

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  When kernel test rebooted onto the 5.15.0-43-generic HWE kernel, no
  output appeared on the console after the EFI stub:

  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint A0
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint 92
  Checkpoint AD
  EFI stub: Booting Linux Kernel...
  EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
  EFI stub: Using DTB from configuration table
  EFI stub: Exiting boot services...

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


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

[Kernel-packages] [Bug 1998885] Re: Add additional Mediatek MT7922 BT device ID

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.1 - 6.1.0-1004.4

---
linux-oem-6.1 (6.1.0-1004.4) jammy; urgency=medium

  * jammy/linux-oem-6.1: 6.1.0-1004.4 -proposed tracker (LP: #2001678)

  * Microphone mute LED not working as expected after pressing the mic mute
hotkey (LP: #2000909)
- ALSA: hda/realtek: Apply dual codec fixup for Dell Latitude laptops

  * Virtual GPU driver packaging regression (LP: #1996112)
- [Packaging] Reintroduce VM DRM drivers into modules

  * Soundwire support for the Intel RPL Gen 0C40/0C11 platforms (LP: #230)
- SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C40 
product
- SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C11 
product

  [ Ubuntu: 6.1.0-11.11 ]

  * lunar/linux: 6.1.0-11.11 -proposed tracker (LP: #2000704)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * Lunar update: v6.1.1 upstream stable release (LP: #2000706)
- x86/vdso: Conditionally export __vdso_sgx_enter_enclave()
- libbpf: Fix uninitialized warning in btf_dump_dump_type_data
- PCI: mt7621: Add sentinel to quirks table
- mips: ralink: mt7621: define MT7621_SYSC_BASE with __iomem
- mips: ralink: mt7621: soc queries and tests as functions
- mips: ralink: mt7621: do not use kzalloc too early
- irqchip/ls-extirq: Fix endianness detection
- udf: Discard preallocation before extending file with a hole
- udf: Fix preallocation discarding at indirect extent boundary
- udf: Do not bother looking for prealloc extents if i_lenExtents matches
  i_size
- udf: Fix extending file within last block
- usb: gadget: uvc: Prevent buffer overflow in setup handler
- USB: serial: option: add Quectel EM05-G modem
- USB: serial: cp210x: add Kamstrup RF sniffer PIDs
- USB: serial: f81232: fix division by zero on line-speed change
- USB: serial: f81534: fix division by zero on line-speed change
- xhci: Apply XHCI_RESET_TO_DEFAULT quirk to ADL-N
- staging: r8188eu: fix led register settings
- igb: Initialize mailbox message for VF reset
- usb: typec: ucsi: Resume in separate work
- usb: dwc3: pci: Update PCIe device ID for USB3 controller on CPU 
sub-system
  for Raptor Lake
- cifs: fix oops during encryption
- KEYS: encrypted: fix key instantiation with user-provided data
- Linux 6.1.1
  * Expose built-in trusted and revoked certificates (LP: #1996892)
- [Packaging] Expose built-in trusted and revoked certificates
  * Fix System cannot detect bluetooth after running suspend stress test
(LP: #1998727)
- wifi: rtw88: 8821c: enable BT device recovery mechanism
  * Gnome doesn't run smooth when performing normal usage with RPL-P CPU
(LP: #1998419)
- drm/i915/rpl-p: Add stepping info
  * Mute/mic LEDs no function on a HP platfrom (LP: #1998882)
- ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook
  * Add additional Mediatek MT7922 BT device ID (LP: #1998885)
- Bluetooth: btusb: Add a new VID/PID 0489/e0f2 for MT7922
  * Support Icicle Kit reference design v2022.10 (LP: #1993148)
- SAUCE: riscv: dts: microchip: Disable PCIe on the Icicle Kit
  * Add iommu passthrough quirk for Intel IPU6 on RaptorLake (LP: #1989041)
- SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs on 
Raptor
  Lake
  * Enable Intel FM350 wwan CCCI driver port logging (LP: #1997686)
- net: wwan: t7xx: use union to group port type specific data
- net: wwan: t7xx: Add port for modem logging
  * TEE Support for CCP driver (LP: #1991608)
- crypto: ccp - Add support for TEE for PCI ID 0x14CA
  * Kinetic update: v5.19.17 upstream stable release (LP: #1994179)
- Revert "fs: check FMODE_LSEEK to control internal pipe splicing"
- kbuild: Add skip_encoding_btf_enum64 option to pahole
  * Kinetic update: v5.19.15 upstream stable release (LP: #1994078)
- Revert "clk: ti: Stop using legacy clkctrl names for omap4 and 5"
  * support independent clock and LED GPIOs for Intel IPU6 platforms
(LP: #1989046)
- SAUCE: platform/x86: int3472: support independent clock and LED GPIOs
  * Kernel livepatch support for for s390x (LP: #1639924)
- [Config] Enable EXPOLINE_EXTERN on s390x
  * Kinetic update: v5.19.7 upstream stable release (LP: #1988733)
- Revert "PCI/portdrv: Don't disable AER reporting in
  get_port_device_capability()"
  * Kinetic update: v5.19.3 upstream stable release (LP: #1987345)
- Revert "mm: kfence: apply kmemleak_ignore_phys on early allocated pool"
  * Fix non-working e1000e device after resume (LP: #1951861)
- SAUCE: Revert "e1000e: Add polling mechanism to indicate CSME DPG exit"
  * Add additional Mediatek MT7921 WiFi/BT device IDs (LP: #1937004)
- SAUCE: Bluetooth: btusb: Add support for Foxconn Mediatek Chip
  * Fix system sleep on TGL systems with Intel ME (LP: #1919321)
- SAUCE: PCI: Serialize TGL e1000e PM ops
  * Fix broken e1000e 

[Kernel-packages] [Bug 2000030] Re: Soundwire support for the Intel RPL Gen 0C40/0C11 platforms

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.1 - 6.1.0-1004.4

---
linux-oem-6.1 (6.1.0-1004.4) jammy; urgency=medium

  * jammy/linux-oem-6.1: 6.1.0-1004.4 -proposed tracker (LP: #2001678)

  * Microphone mute LED not working as expected after pressing the mic mute
hotkey (LP: #2000909)
- ALSA: hda/realtek: Apply dual codec fixup for Dell Latitude laptops

  * Virtual GPU driver packaging regression (LP: #1996112)
- [Packaging] Reintroduce VM DRM drivers into modules

  * Soundwire support for the Intel RPL Gen 0C40/0C11 platforms (LP: #230)
- SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C40 
product
- SAUCE: ASoC: Intel: soc-acpi: add configuration for variant of 0C11 
product

  [ Ubuntu: 6.1.0-11.11 ]

  * lunar/linux: 6.1.0-11.11 -proposed tracker (LP: #2000704)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * Lunar update: v6.1.1 upstream stable release (LP: #2000706)
- x86/vdso: Conditionally export __vdso_sgx_enter_enclave()
- libbpf: Fix uninitialized warning in btf_dump_dump_type_data
- PCI: mt7621: Add sentinel to quirks table
- mips: ralink: mt7621: define MT7621_SYSC_BASE with __iomem
- mips: ralink: mt7621: soc queries and tests as functions
- mips: ralink: mt7621: do not use kzalloc too early
- irqchip/ls-extirq: Fix endianness detection
- udf: Discard preallocation before extending file with a hole
- udf: Fix preallocation discarding at indirect extent boundary
- udf: Do not bother looking for prealloc extents if i_lenExtents matches
  i_size
- udf: Fix extending file within last block
- usb: gadget: uvc: Prevent buffer overflow in setup handler
- USB: serial: option: add Quectel EM05-G modem
- USB: serial: cp210x: add Kamstrup RF sniffer PIDs
- USB: serial: f81232: fix division by zero on line-speed change
- USB: serial: f81534: fix division by zero on line-speed change
- xhci: Apply XHCI_RESET_TO_DEFAULT quirk to ADL-N
- staging: r8188eu: fix led register settings
- igb: Initialize mailbox message for VF reset
- usb: typec: ucsi: Resume in separate work
- usb: dwc3: pci: Update PCIe device ID for USB3 controller on CPU 
sub-system
  for Raptor Lake
- cifs: fix oops during encryption
- KEYS: encrypted: fix key instantiation with user-provided data
- Linux 6.1.1
  * Expose built-in trusted and revoked certificates (LP: #1996892)
- [Packaging] Expose built-in trusted and revoked certificates
  * Fix System cannot detect bluetooth after running suspend stress test
(LP: #1998727)
- wifi: rtw88: 8821c: enable BT device recovery mechanism
  * Gnome doesn't run smooth when performing normal usage with RPL-P CPU
(LP: #1998419)
- drm/i915/rpl-p: Add stepping info
  * Mute/mic LEDs no function on a HP platfrom (LP: #1998882)
- ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook
  * Add additional Mediatek MT7922 BT device ID (LP: #1998885)
- Bluetooth: btusb: Add a new VID/PID 0489/e0f2 for MT7922
  * Support Icicle Kit reference design v2022.10 (LP: #1993148)
- SAUCE: riscv: dts: microchip: Disable PCIe on the Icicle Kit
  * Add iommu passthrough quirk for Intel IPU6 on RaptorLake (LP: #1989041)
- SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs on 
Raptor
  Lake
  * Enable Intel FM350 wwan CCCI driver port logging (LP: #1997686)
- net: wwan: t7xx: use union to group port type specific data
- net: wwan: t7xx: Add port for modem logging
  * TEE Support for CCP driver (LP: #1991608)
- crypto: ccp - Add support for TEE for PCI ID 0x14CA
  * Kinetic update: v5.19.17 upstream stable release (LP: #1994179)
- Revert "fs: check FMODE_LSEEK to control internal pipe splicing"
- kbuild: Add skip_encoding_btf_enum64 option to pahole
  * Kinetic update: v5.19.15 upstream stable release (LP: #1994078)
- Revert "clk: ti: Stop using legacy clkctrl names for omap4 and 5"
  * support independent clock and LED GPIOs for Intel IPU6 platforms
(LP: #1989046)
- SAUCE: platform/x86: int3472: support independent clock and LED GPIOs
  * Kernel livepatch support for for s390x (LP: #1639924)
- [Config] Enable EXPOLINE_EXTERN on s390x
  * Kinetic update: v5.19.7 upstream stable release (LP: #1988733)
- Revert "PCI/portdrv: Don't disable AER reporting in
  get_port_device_capability()"
  * Kinetic update: v5.19.3 upstream stable release (LP: #1987345)
- Revert "mm: kfence: apply kmemleak_ignore_phys on early allocated pool"
  * Fix non-working e1000e device after resume (LP: #1951861)
- SAUCE: Revert "e1000e: Add polling mechanism to indicate CSME DPG exit"
  * Add additional Mediatek MT7921 WiFi/BT device IDs (LP: #1937004)
- SAUCE: Bluetooth: btusb: Add support for Foxconn Mediatek Chip
  * Fix system sleep on TGL systems with Intel ME (LP: #1919321)
- SAUCE: PCI: Serialize TGL e1000e PM ops
  * Fix broken e1000e 

[Kernel-packages] [Bug 2002427] Re: Subiquity segfault in ARM64 with -64k Kernel

[Michael Hudson-Doyle]

** No longer affects: linux (Ubuntu)

** Also affects: snapcraft
   Importance: Undecided
   Status: New

** Summary changed:

- Subiquity segfault in ARM64 with -64k Kernel
+ classic snaps do not work on ARM64 kernel configured to use 64k pages

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

Title:
  classic snaps do not work on ARM64 kernel configured to use 64k pages

Status in Snapcraft:
  New
Status in subiquity:
  New

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  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:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   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/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   

[Kernel-packages] [Bug 2002206] Re: Periodic freezing after unplugging USB-C monitor - "Enabling HDA controller" in dmesg

[rustyx]

** Description changed:

- Lenovo Thinkpad X1 Extreme Gen 5 (Intel 12th gen CPU, Nvidia RTX 3050
- GPU).
- 
- After disconnecting an external monitor from Thunderbolt 4 (USB-C port),
- the system keeps on randomly freezing for 1-2 seconds.
+ After disconnecting an external monitor from a Thunderbolt 4 (USB-C) port
+ *while the system is asleep*, after wake-up the system keeps on randomly 
freezing for 1-2 seconds.
  
  Every freeze is accompanied by an "Enabling HDA controller" kernel
  message:
  
  [54984.259832] nvidia :01:00.0: Enabling HDA controller
  [55008.355784] nvidia :01:00.0: Enabling HDA controller
  [55044.771722] nvidia :01:00.0: Enabling HDA controller
  [55069.859682] nvidia :01:00.0: Enabling HDA controller
  [55096.547622] nvidia :01:00.0: Enabling HDA controller
  [55122.243581] nvidia :01:00.0: Enabling HDA controller
  [55146.339543] nvidia :01:00.0: Enabling HDA controller
  [55168.579505] nvidia :01:00.0: Enabling HDA controller
  [55199.491437] nvidia :01:00.0: Enabling HDA controller
  
- Rebooting or even logging out "fixes" the problem.
- 
+ Rebooting or restarting Xorg "fixes" the problem.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-56-generic 5.15.0-56.62
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: socwatch2_15 vtsspp sep5 socperf3 pax nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  me 2469 F pulseaudio
   /dev/snd/controlC0:  me 2469 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Sat Jan  7 12:19:39 2023
  InstallationDate: Installed on 2022-08-31 (128 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 04f2:b74f Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 003: ID 06cb:00f9 Synaptics, Inc.
   Bus 001 Device 007: ID 8087:0033 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 21DE001QMH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=d4a7fdda-30e3-439b-b327-e87d7b2bc81e ro pci=nommconf
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-56-generic N/A
   linux-backports-modules-5.15.0-56-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2022
  dmi.bios.release: 1.12
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3JET28W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21DE001QMH
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3JET28W(1.12):bd10/18/2022:br1.12:efr1.8:svnLENOVO:pn21DE001QMH:pvrThinkPadX1ExtremeGen5:rvnLENOVO:rn21DE001QMH:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21DE_BU_Think_FM_ThinkPadX1ExtremeGen5:
  dmi.product.family: ThinkPad X1 Extreme Gen 5
  dmi.product.name: 21DE001QMH
  dmi.product.sku: LENOVO_MT_21DE_BU_Think_FM_ThinkPad X1 Extreme Gen 5
  dmi.product.version: ThinkPad X1 Extreme Gen 5
  dmi.sys.vendor: LENOVO

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

Title:
  Periodic freezing after unplugging USB-C monitor - "Enabling HDA
  controller" in dmesg

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After disconnecting an external monitor from a Thunderbolt 4 (USB-C) port
  *while the system is asleep*, after wake-up the system keeps on randomly 
freezing for 1-2 seconds.

  Every freeze is accompanied by an "Enabling HDA controller" kernel
  message:

  [54984.259832] nvidia :01:00.0: Enabling HDA controller
  [55008.355784] nvidia :01:00.0: Enabling HDA controller
  [55044.771722] nvidia :01:00.0: Enabling HDA controller
  [55069.859682] nvidia :01:00.0: Enabling HDA controller
  [55096.547622] nvidia :01:00.0: Enabling HDA controller
  [55122.243581] nvidia :01:00.0: Enabling HDA controller
  [55146.339543] nvidia :01:00.0: Enabling HDA controller
  [55168.579505] nvidia :01:00.0: Enabling HDA controller
  [55199.491437] nvidia :01:00.0: Enabling HDA controller

  Rebooting or restarting Xorg "fixes" the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: 

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

[Joao Andre Simioni]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/2002427/+attachment/5640540/+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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

Status in subiquity:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  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:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   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/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

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

[Joao Andre Simioni]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2002427/+attachment/5640541/+files/acpidump.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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

Status in subiquity:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  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:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   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/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

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

[Joao Andre Simioni]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/2002427/+attachment/5640539/+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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

Status in subiquity:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  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:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   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/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

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

[Joao Andre Simioni]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/2002427/+attachment/5640538/+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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

Status in subiquity:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  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:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   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/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

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

[Joao Andre Simioni]

apport information

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

Title:
  Subiquity segfault in ARM64 with -64k Kernel

Status in subiquity:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  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:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   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/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

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

[Joao Andre Simioni]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2002427/+attachment/5640536/+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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

Status in subiquity:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  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:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   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/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

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

[Joao Andre Simioni]

apport information

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

Title:
  Subiquity segfault in ARM64 with -64k Kernel

Status in subiquity:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  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:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   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/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

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

[Joao Andre Simioni]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/2002427/+attachment/5640537/+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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

Status in subiquity:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  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:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   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/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

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

[Joao Andre Simioni]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/2002427/+attachment/5640533/+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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

Status in subiquity:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  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:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   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/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

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

[Joao Andre Simioni]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/2002427/+attachment/5640532/+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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

Status in subiquity:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  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:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   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/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 2002427] Re: Subiquity segfault in ARM64 with -64k Kernel

[Joao Andre Simioni]

apport information

** Tags added: apport-collected jammy uec-images

** Description changed:

  [Problem Description]
  
  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message
  
  [Additional Info]
  
  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-info
  works fine. Both python3.8 and wget are statically compiled, while
  ubuntu-distro-info is not.
  
  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable
  
  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable
  
  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)
  
  The same VM, using the non -64k kernel works:
  
  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works
  
  Tried other kernels (5.17, 5.19) with the same error.
  
  [Reproducer]
  
  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole
  
  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569
  
  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux
  
  4. Install subiquity
  sudo snap install subiquity
  
  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
+  crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
+ ApportVersion: 2.20.11-0ubuntu82.3
+ Architecture: arm64
+ 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:
+ CRDA: N/A
+ CasperMD5CheckResult: unknown
+ DistroRelease: Ubuntu 22.04
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  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/15p, 5000M
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
+ MachineType: QEMU QEMU Virtual Machine
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic-64k 
root=UUID=a6c92eea-e1ae-4ec4-9fbc-69e3ab11d0f7 ro console=tty1 console=ttyS0
+ ProcVersionSignature: Ubuntu 5.15.0-27.28-generic-64k 5.15.30
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-27-generic-64k N/A
+  linux-backports-modules-5.15.0-27-generic-64k  N/A
+  linux-firmware

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

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

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

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

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

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

Title:
  Subiquity segfault in ARM64 with -64k Kernel

Status in subiquity:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault

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


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

[Kernel-packages] [Bug 2002427] Re: Subiquity segfault in ARM64 with -64k Kernel

[Dan Bungert]

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

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

Title:
  Subiquity segfault in ARM64 with -64k Kernel

Status in subiquity:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault

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


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

[Kernel-packages] [Bug 1997472] Re: Touchpad problem detecting working area on Dell XPS

[florin]

I sent them to that email address you posted above. (I am not sure what
are the possible implications and risks if I post it here)

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

Title:
  Touchpad problem detecting working area on Dell XPS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using a new Dell XPS 17 with the latest Ubuntu (22.10). One bug I
  could see is the touchpad sensitivity. Sometimes, randomly, the upper
  part of the touchpad is the only one working, most of its surface does
  not work. If the movement starts in the working area, then you can use
  the whole touchpad until you lift the finger. After a while it seems
  to recover by itself. My feeling is that this is somehow related to
  the sensitivity of the touchpad (some instability) or related to the
  system that disables the touchpad while writing (again, some buggy
  detection). While writing this text I experienced the bug twice, for
  instance, intermittently.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-23-generic 5.19.0-23.24
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  florin 1581 F pipewire
florin 1584 F wireplumber
   /dev/snd/controlC0:  florin 1584 F wireplumber
   /dev/snd/seq:florin 1581 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 22 17:25:52 2022
  InstallationDate: Installed on 2022-10-24 (29 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: Dell Inc. XPS 17 9720
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=99833626-9acf-4145-9fee-2cbbe47e4d33 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.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2022
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0KNF8J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd09/08/2022:br1.11:svnDellInc.:pnXPS179720:pvr:rvnDellInc.:rn0KNF8J:rvrA00:cvnDellInc.:ct10:cvr:sku0AFF:
  dmi.product.family: XPS
  dmi.product.name: XPS 17 9720
  dmi.product.sku: 0AFF
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1997946] Re: [SRU] Support soundwire speaker AMP-ALC1318 codec

[Sebastien Bacher]

I've uploaded to lunar the same changes that kinetic now

** Changed in: alsa-ucm-conf (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: alsa-ucm-conf (Ubuntu)
   Importance: Undecided => High

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

Title:
  [SRU] Support soundwire speaker AMP-ALC1318 codec

Status in OEM Priority Project:
  Triaged
Status in alsa-ucm-conf package in Ubuntu:
  Fix Committed

Bug description:
  [ Impact ]

   * Add ALC1318 speaker codec ucm file
   * Make internal speaker working on the platform with the codec

  [ Test Plan ]

   * On platform with the codec, the internal speaker should work after
     boot into Ubuntu

  [ Where problems could occur ]

   * The config only be executed on the platform with the codec exported

   * It needs to add the codec combination to the machine driver to make the 
function work
 ex. 
https://github.com/thesofproject/linux/blob/topic/sof-dev/sound/soc/intel/common/soc-acpi-intel-rpl-match.c#L225

  [ Other Info ]

   * Upstream commit soundwire speaker AMP-ALC1318 codec.
     
https://github.com/alsa-project/alsa-ucm-conf/commit/c82c400fb653292bbf0570e278d60e1ba14cc341

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


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

[Kernel-packages] [Bug 1945289] Re: Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16 (installed while updating to impish), amdgpu driver.

[KOLANICH]

** Description changed:

  On 5.11.0 everything is OK.
  The GPU is AMD Carrizo APU.
  
  UPD: I have checked several kernels for presence of this bug
  
  Ubuntu:
  linux-image-5.13.0-35-generic/now 5.13.0-35.40~20.04.1 amd64 
[installed,local] - BROKEN
  linux-image-5.14.0-1055-oem/now 5.14.0-1055.62 amd64 [installed,local] - OK
  linux-image-5.15.0-57-generic/now 5.15.0-57.63 amd64 [installed,local] - OK
  linux-image-5.17.0-1003-oem/now 5.17.0-1003.3 amd64 [installed,local] - OK
  linux-image-5.19.0-21-generic/now 5.19.0-21.21 amd64 [installed,local] - OK
  
- 
  Debian:
  linux-image-5.10.0-20-amd64/stable,now 5.10.158-2 amd64 [installed] - 
probably OK, haven't checked
  linux-image-5.18.0-0.deb11.4-amd64/bullseye-backports,now 5.18.16-1~bpo11+1 
amd64 [installed] - OK
  linux-image-5.19.0-0.deb11.2-amd64/bullseye-backports,now 5.19.11-1~bpo11+1 
amd64 [installed] - OK
  linux-image-6.0.0-6-amd64/testing,now 6.0.12-1 amd64 [installed] - OK
+ 
+ Other people reports in this thread:
+ 
+ 
+ korta (Carrizo)
+ 5.13.0-21-generic - BROKEN
+ 
+ Paweł Szmergała (Lucienne)
+ 5.13.0-27-generic - OK
+ 5.13.0-28-generic - BROKEN
+ 5.13.0-30-generic - BROKEN
+ 5.13.0-35-generic - BROKEN

** Tags added: lucienne

** Tags added: s3

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

Title:
  Failed to properly resume from S3 (suspend-to-ram) on kernel version
  5.13.0-16 (installed while updating to impish), amdgpu driver.

Status in linux-meta package in Ubuntu:
  Fix Released

Bug description:
  On 5.11.0 everything is OK.
  The GPU is AMD Carrizo APU.

  UPD: I have checked several kernels for presence of this bug

  Ubuntu:
  linux-image-5.13.0-35-generic/now 5.13.0-35.40~20.04.1 amd64 
[installed,local] - BROKEN
  linux-image-5.14.0-1055-oem/now 5.14.0-1055.62 amd64 [installed,local] - OK
  linux-image-5.15.0-57-generic/now 5.15.0-57.63 amd64 [installed,local] - OK
  linux-image-5.17.0-1003-oem/now 5.17.0-1003.3 amd64 [installed,local] - OK
  linux-image-5.19.0-21-generic/now 5.19.0-21.21 amd64 [installed,local] - OK

  Debian:
  linux-image-5.10.0-20-amd64/stable,now 5.10.158-2 amd64 [installed] - 
probably OK, haven't checked
  linux-image-5.18.0-0.deb11.4-amd64/bullseye-backports,now 5.18.16-1~bpo11+1 
amd64 [installed] - OK
  linux-image-5.19.0-0.deb11.2-amd64/bullseye-backports,now 5.19.11-1~bpo11+1 
amd64 [installed] - OK
  linux-image-6.0.0-6-amd64/testing,now 6.0.12-1 amd64 [installed] - OK

  Other people reports in this thread:

  
  korta (Carrizo)
  5.13.0-21-generic - BROKEN

  Paweł Szmergała (Lucienne)
  5.13.0-27-generic - OK
  5.13.0-28-generic - BROKEN
  5.13.0-30-generic - BROKEN
  5.13.0-35-generic - BROKEN

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


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

[Kernel-packages] [Bug 1945289] Re: Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16 (installed while updating to impish), amdgpu driver.

[KOLANICH]

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

** Description changed:

  On 5.11.0 everything is OK.
  The GPU is AMD Carrizo APU.
+ 
+ UPD: I have checked several kernels for presence of this bug
+ 
+ Ubuntu:
+ linux-image-5.13.0-35-generic/now 5.13.0-35.40~20.04.1 amd64 
[installed,local] - BROKEN
+ linux-image-5.14.0-1055-oem/now 5.14.0-1055.62 amd64 [installed,local] - OK
+ linux-image-5.15.0-57-generic/now 5.15.0-57.63 amd64 [installed,local] - OK
+ linux-image-5.17.0-1003-oem/now 5.17.0-1003.3 amd64 [installed,local] - OK
+ linux-image-5.19.0-21-generic/now 5.19.0-21.21 amd64 [installed,local] - OK
+ 
+ 
+ Debian:
+ linux-image-5.10.0-20-amd64/stable,now 5.10.158-2 amd64 [installed] - 
probably OK, haven't checked
+ linux-image-5.18.0-0.deb11.4-amd64/bullseye-backports,now 5.18.16-1~bpo11+1 
amd64 [installed] - OK
+ linux-image-5.19.0-0.deb11.2-amd64/bullseye-backports,now 5.19.11-1~bpo11+1 
amd64 [installed] - OK
+ linux-image-6.0.0-6-amd64/testing,now 6.0.12-1 amd64 [installed] - OK

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

Title:
  Failed to properly resume from S3 (suspend-to-ram) on kernel version
  5.13.0-16 (installed while updating to impish), amdgpu driver.

Status in linux-meta package in Ubuntu:
  Fix Released

Bug description:
  On 5.11.0 everything is OK.
  The GPU is AMD Carrizo APU.

  UPD: I have checked several kernels for presence of this bug

  Ubuntu:
  linux-image-5.13.0-35-generic/now 5.13.0-35.40~20.04.1 amd64 
[installed,local] - BROKEN
  linux-image-5.14.0-1055-oem/now 5.14.0-1055.62 amd64 [installed,local] - OK
  linux-image-5.15.0-57-generic/now 5.15.0-57.63 amd64 [installed,local] - OK
  linux-image-5.17.0-1003-oem/now 5.17.0-1003.3 amd64 [installed,local] - OK
  linux-image-5.19.0-21-generic/now 5.19.0-21.21 amd64 [installed,local] - OK

  
  Debian:
  linux-image-5.10.0-20-amd64/stable,now 5.10.158-2 amd64 [installed] - 
probably OK, haven't checked
  linux-image-5.18.0-0.deb11.4-amd64/bullseye-backports,now 5.18.16-1~bpo11+1 
amd64 [installed] - OK
  linux-image-5.19.0-0.deb11.2-amd64/bullseye-backports,now 5.19.11-1~bpo11+1 
amd64 [installed] - OK
  linux-image-6.0.0-6-amd64/testing,now 6.0.12-1 amd64 [installed] - OK

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


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

[Kernel-packages] [Bug 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

[Anthony Wong]

** Changed in: linux-oem-6.0 (Ubuntu Kinetic)
   Status: New => Invalid

** Changed in: linux-oem-5.17 (Ubuntu Kinetic)
   Status: New => Invalid

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  New
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

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


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

[Kernel-packages] [Bug 1997946] Re: [SRU] Support soundwire speaker AMP-ALC1318 codec

[Sebastien Bacher]

Is the issue fixed in lunar?

Also for 22.04 the patch modifies 0005-acp6x-add-initial-support-for-
AMD-Yellow-Carp-ACP6x.patch is that wanted?

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

Title:
  [SRU] Support soundwire speaker AMP-ALC1318 codec

Status in OEM Priority Project:
  Triaged
Status in alsa-ucm-conf package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

   * Add ALC1318 speaker codec ucm file
   * Make internal speaker working on the platform with the codec

  [ Test Plan ]

   * On platform with the codec, the internal speaker should work after
     boot into Ubuntu

  [ Where problems could occur ]

   * The config only be executed on the platform with the codec exported

   * It needs to add the codec combination to the machine driver to make the 
function work
 ex. 
https://github.com/thesofproject/linux/blob/topic/sof-dev/sound/soc/intel/common/soc-acpi-intel-rpl-match.c#L225

  [ Other Info ]

   * Upstream commit soundwire speaker AMP-ALC1318 codec.
     
https://github.com/alsa-project/alsa-ucm-conf/commit/c82c400fb653292bbf0570e278d60e1ba14cc341

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


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

[Kernel-packages] [Bug 1958410] Re: bytcr_rt5640 sound not working with kernel >= 5.13

[Yosha872]

Also concerns a Acer Aspire Switch 10E SW3-013, with Lubuntu 22.04
(kernel 5.15).

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

Title:
  bytcr_rt5640 sound not working with kernel >= 5.13

Status in linux-meta-hwe-5.13 package in Ubuntu:
  Confirmed
Status in linux-meta-hwe-5.15 package in Ubuntu:
  Confirmed

Bug description:
  Using the built in speakers on a Linx 1010b. The 5.11 kernel works
  fine, but 5.13 and 5.14 fail.

  The card, when working is seen in alsa-info as bytcrrt5640,bytcr-
  rt5640, whereas in the later (hwe-20.04-edge, oem-20.04d) kernels
  where it fails, it is seen as "rt5640,sof-bytcht rt5640"

  When failing, speaker-test, spd-say, and most other sound sources seem
  to get 'sunk', and the level meter on the pulse mixer shows activity.
  FWIW "espeak-ng hello" blocks on the broken setup.

  I confess I'm not actually using the linux-meta-hwe-5.13 as it is
  unavailable in LinuxMint. I am using linux-generic-hwe-20.04-edge,
  which AFAICT pulls in the same kernels. apt policy pointed me to
  report here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.13/+bug/1958410/+subscriptions


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

[Kernel-packages] [Bug 1958410] Re: bytcr_rt5640 sound not working with kernel >= 5.13

[Launchpad Bug Tracker]

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

** Changed in: linux-meta-hwe-5.15 (Ubuntu)
   Status: New => Confirmed

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

Title:
  bytcr_rt5640 sound not working with kernel >= 5.13

Status in linux-meta-hwe-5.13 package in Ubuntu:
  Confirmed
Status in linux-meta-hwe-5.15 package in Ubuntu:
  Confirmed

Bug description:
  Using the built in speakers on a Linx 1010b. The 5.11 kernel works
  fine, but 5.13 and 5.14 fail.

  The card, when working is seen in alsa-info as bytcrrt5640,bytcr-
  rt5640, whereas in the later (hwe-20.04-edge, oem-20.04d) kernels
  where it fails, it is seen as "rt5640,sof-bytcht rt5640"

  When failing, speaker-test, spd-say, and most other sound sources seem
  to get 'sunk', and the level meter on the pulse mixer shows activity.
  FWIW "espeak-ng hello" blocks on the broken setup.

  I confess I'm not actually using the linux-meta-hwe-5.13 as it is
  unavailable in LinuxMint. I am using linux-generic-hwe-20.04-edge,
  which AFAICT pulls in the same kernels. apt policy pointed me to
  report here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.13/+bug/1958410/+subscriptions


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

[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

[Giuliano Lotta]

UPDATE:
after resuming the nobebook, the system crashed with the following message:

usb 3-6: Failed to query (SET_CUR) UVC control 4 on unit 1: -32 (exp. 4)
uvcvideo 3-6:1.0: reset_resume error -5

WHERE / HOW may I find other useful information to debug the problem ?

Giuliano

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/20/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 

[Kernel-packages] [Bug 1995511] Re: net-build failed in ubuntu_kernel_selftests with 6.0 kernel

[Po-Hsu Lin]

This is affecting J-oem-6.1 as well.

** Tags added: 6.1 sru-20221114

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

Title:
  net-build failed in ubuntu_kernel_selftests with 6.0 kernel

Status in ubuntu-kernel-tests:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  New

Bug description:
  Issue found with J-oem-6.0.0-1007.7

  This is not a regression, issue exists before this kernel.

  make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
  gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include  
  reuseport_bpf.c  -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf
  gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include  
  reuseport_bpf_cpu.c  -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_cpu
  gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include  
  reuseport_bpf_numa.c -lnuma -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_numa
  gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include  
  reuseport_dualstack.c  -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_dualstack
  gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include  
  reuseaddr_conflict.c  -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseaddr_conflict
  gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include  
  tls.c  -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/tls
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
  make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  stderr:
  tls.c:32:50: error: field ‘sm4gcm’ has incomplete type
 32 | struct tls12_crypto_info_sm4_gcm sm4gcm;
|  ^~
  tls.c:33:50: error: field ‘sm4ccm’ has incomplete type
 33 | struct tls12_crypto_info_sm4_ccm sm4ccm;
|  ^~
  tls.c: In function ‘tls_crypto_info_init’:
  tls.c:56:14: error: ‘TLS_CIPHER_SM4_GCM’ undeclared (first use in this 
function); did you mean ‘TLS_CIPHER_AES_GCM_256’?
 56 | case TLS_CIPHER_SM4_GCM:
|  ^~
|  TLS_CIPHER_AES_GCM_256
  tls.c:56:14: note: each undeclared identifier is reported only once for each 
function it appears in
  tls.c:57:37: error: invalid application of ‘sizeof’ to incomplete type 
‘struct tls12_crypto_info_sm4_gcm’
 57 | tls12->len = sizeof(struct tls12_crypto_info_sm4_gcm);
| ^~
  tls.c:61:14: error: ‘TLS_CIPHER_SM4_CCM’ undeclared (first use in this 
function); did you mean ‘TLS_CIPHER_AES_CCM_128’?
 61 | case TLS_CIPHER_SM4_CCM:
|  ^~
|  TLS_CIPHER_AES_CCM_128
  tls.c:62:37: error: invalid application of ‘sizeof’ to incomplete type 
‘struct tls12_crypto_info_sm4_ccm’
 62 | tls12->len = sizeof(struct tls12_crypto_info_sm4_ccm);
| ^~
  tls.c: At top level:
  tls.c:268:24: error: ‘TLS_CIPHER_SM4_GCM’ undeclared here (not in a 
function); did you mean ‘TLS_CIPHER_AES_GCM_256’?
268 | .cipher_type = TLS_CIPHER_SM4_GCM,
|^~
|TLS_CIPHER_AES_GCM_256
  tls.c:274:24: error: ‘TLS_CIPHER_SM4_CCM’ undeclared here (not in a 
function); did you mean ‘TLS_CIPHER_AES_CCM_128’?
274 | .cipher_type = TLS_CIPHER_SM4_CCM,
|^~
|TLS_CIPHER_AES_CCM_128
  tls.c: In function ‘tls_setup’:
  tls.c:329:54: 

[Kernel-packages] [Bug 1999528] Re: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later

[Stefan Bader]

** Changed in: linux (Ubuntu Kinetic)
   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/1999528

Title:
  [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and
  later

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  [SRU Justification]

  == Impact ==

  Since we split the lowlatency kernel into its own source package the
  check in the regression test suite is missing a case and will not run,
  even though the kernel can be booted in a VM instance.

  == Fix ==

  Add the missing case to the test script which is used by ADT testing.
  The test scripts are inherited from the primary/distro kernel. The fix
  should be made there instead of changing the lowlatency tree.

  == Test ==

  Inspecting the ADT logs we should start to see tests executed instead of:
    autopkgtest [19:22:21]: test ubuntu-regression-suite: [-
    ubuntu-regression-suite is pointless, if one cannot boot the kernel

  == Regression Potential ==

  There are a couple of flaky tests which will start to show up, rather
  than only successful runs (which should have been a suspicious thing).

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


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

[Kernel-packages] [Bug 2002256] Re: [UBUNTU 22.04] zfcp: fix double free of FSF request when qdio send fails

[Frank Heimes]

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

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

Title:
  [UBUNTU 22.04] zfcp: fix double free of FSF request when qdio send
  fails

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux source package in Kinetic:
  New

Bug description:
  Description:   zfcp: fix double free of FSF request when qdio send fails
  Symptom:   When doing maintenance actions on FCP devices that turn off a
 FCP device while I/O is still running on it in Linux - for
 example turning off the channel path of the FCP device - the
 Linux kernel crashes.
  Problem:   We used to use the wrong type of integer in
 'zfcp_fsf_req_send()' to cache the FSF request ID when sending 
a
 new FSF request. This is used in case the sending fails and we
 need to remove the request from our internal hash table again
 (so we don't keep an invalid reference and use it when we free
 the request again).

 In 'zfcp_fsf_req_send()' we used to cache the ID as 'int'
 (signed and 32 bit wide), but the rest of the zfcp code (and 
the
 firmware specification) handles the ID as 'unsigned long'/'u64'
 (unsigned and 64 bit wide [s390x ELF ABI]).
 For one this has the obvious problem that when the ID grows
 past 32 bit (this can happen reasonably fast) it is truncated 
to
 32 bit when storing it in the cache variable and so doesn't
 match the original ID anymore.
 The second less obvious problem is that even when the
 original ID has not yet grown past 32 bit, as soon as the 32nd
 bit is set in the original ID (0x8000 = 2'147'483'648) we
 will have a mismatch when we cast it back to 'unsigned long'
 because casting the signed type 'int' into the wider type
 'unsigned long' will use a sign-extending instruction, and so
 flip all leading zeros to one instead.

 If we can't successfully remove the request from the hash table
 again after 'zfcp_qdio_send()' fails (this happens regularly
 when zfcp cannot notify the adapter about new work because the
 adapter is already gone during e.g. a ChpID toggle) we will end
 up with a double free.
 We unconditionally free the request in the calling function
 when 'zfcp_fsf_req_send()' fails, but because the request is
 still in the hash table we end up with a stale memory 
reference,
 and once the zfcp adapter is either reset during recovery or
 shutdown we end up freeing the same memory twice.

  Solution:  To fix this, simply change the type of the cache variable to
 'unsigned long', like the rest of zfcp and also the argument 
for
 'zfcp_reqlist_find_rm()'. This prevents truncation and wrong
 sign extension and so can successfully remove the request from
 the hash table.

  Reproduction:  Run I/O on a FCP device for so long that you have sent
 2'147'483'648 requests. The current request number can not be
 read directly from user space, but can be read indirectly by
 using 'zfcp_ping' and 'zfcpdbf' (use the correct 
device-bus-ID):

 sudo sh -c 'zfcp_ping -a "${0}" 0x \
 2>/dev/null 1>&2; zfcpdbf "${0}" -x all -i SAN 2>/dev/null 
\
 | grep -E -e "^(Timestamp|Request ID)[[:blank:]]+:" | tail 
\
 -n2' 0.0.1700

 After having reached 0x8000 requests, stop all I/O on the
 FCP device and start only a single process doing 
single-threaded
 synchronous, direct I/O on the FCP device (always only one
 outstanding I/O operation).

 While this I/O process is running, turn of the channel path
 (ChpID) that is used for the FCP device/subchannel. This will
 not always trigger the bug, but occasionally it will.
 Proof that it hit the correct code-path in zfcp can be 
found
 by using 'zfcpdbf' again (use the correct device-bus-ID):

 zfcpdbf 0.0.1700 -x all -i REC 2>/dev/null | grep
  'fsrs__1'

 In case you hit the correct code-path this will print some 
lines
 starting with 'Tag'.

  Upstream-ID:   

[Kernel-packages] [Bug 2001599] Re: Lost display on built-in monitor after suspend

[AceLan Kao]

** Tags added: originate-from-2000236

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

Title:
  Lost display on built-in monitor after suspend

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  In Progress
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  On some laptops, the eDP blinking slowly after resuming from S3

  [Fix]
  The series of patches which are in drp-tip fix the isue
  https://patchwork.freedesktop.org/series/110693/

  [Test]
  ODM and I confirmed the issue is fixed after the patches have been applied.

  [Where problems may occur]
  This series of patches fixes a dedicate issue and change the power sequence 
for the eDP panel. eDP panel may stay blank if the rules are wrong. Our QA will 
help us to verify this kind of issue.

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


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

[Kernel-packages] [Bug 1997472] Re: Touchpad problem detecting working area on Dell XPS

[Zorro Zhang]

Unfortunately, the touchpad firmware was not web post.
Could share the system's service tag? I know it's sensitive but could send to: 
client.linux.issue.escalat...@dell.com

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

Title:
  Touchpad problem detecting working area on Dell XPS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using a new Dell XPS 17 with the latest Ubuntu (22.10). One bug I
  could see is the touchpad sensitivity. Sometimes, randomly, the upper
  part of the touchpad is the only one working, most of its surface does
  not work. If the movement starts in the working area, then you can use
  the whole touchpad until you lift the finger. After a while it seems
  to recover by itself. My feeling is that this is somehow related to
  the sensitivity of the touchpad (some instability) or related to the
  system that disables the touchpad while writing (again, some buggy
  detection). While writing this text I experienced the bug twice, for
  instance, intermittently.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-23-generic 5.19.0-23.24
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  florin 1581 F pipewire
florin 1584 F wireplumber
   /dev/snd/controlC0:  florin 1584 F wireplumber
   /dev/snd/seq:florin 1581 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 22 17:25:52 2022
  InstallationDate: Installed on 2022-10-24 (29 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: Dell Inc. XPS 17 9720
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=99833626-9acf-4145-9fee-2cbbe47e4d33 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.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2022
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0KNF8J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd09/08/2022:br1.11:svnDellInc.:pnXPS179720:pvr:rvnDellInc.:rn0KNF8J:rvrA00:cvnDellInc.:ct10:cvr:sku0AFF:
  dmi.product.family: XPS
  dmi.product.name: XPS 17 9720
  dmi.product.sku: 0AFF
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2001599] Re: Lost display on built-in monitor after suspend

[AceLan Kao]

** Description changed:

  [Impact]
  On some laptops, the eDP blinking slowly after resuming from S3
  
  [Fix]
  The series of patches which are in drp-tip fix the isue
  https://patchwork.freedesktop.org/series/110693/
  
  [Test]
- Verified on the machine which can reproduce the issue.
+ ODM and I confirmed the issue is fixed after the patches have been applied.
  
  [Where problems may occur]
+ This series of patches fixes a dedicate issue and change the power sequence 
for the eDP panel. eDP panel may stay blank if the rules are wrong. Our QA will 
help us to verify this kind of issue.

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

Title:
  Lost display on built-in monitor after suspend

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  In Progress
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  On some laptops, the eDP blinking slowly after resuming from S3

  [Fix]
  The series of patches which are in drp-tip fix the isue
  https://patchwork.freedesktop.org/series/110693/

  [Test]
  ODM and I confirmed the issue is fixed after the patches have been applied.

  [Where problems may occur]
  This series of patches fixes a dedicate issue and change the power sequence 
for the eDP panel. eDP panel may stay blank if the rules are wrong. Our QA will 
help us to verify this kind of issue.

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


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

[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync

[Florian Klemenz]

** Also affects: linux-signed-hwe-5.4 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  kernel io hangs during mdcheck/resync

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.11 package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.4 package in Ubuntu:
  New

Bug description:
  It seems to always occur during an mdcheck/resync, if I am logged in
  via SSH it is still somewhat responsive and basic utilities like dmesg
  will work.  But it apppears any write I/O will hang the terminal and
  nothing is written to syslog (presumably because it is blocked).

  Below is output of dmesg and cat /proc/mdstat, it appears the data
  check was interrupted and /proc/mdstat still shows progress, and a
  whole slew of hung tasks including md1_resync itself.

  [756484.534293] md: data-check of RAID array md0
  [756484.628039] md: delaying data-check of md1 until md0 has finished (they 
share one or more physical units)
  [756493.808773] md: md0: data-check done.
  [756493.829760] md: data-check of RAID array md1
  [778112.446410] md: md1: data-check interrupted.
  [810654.608102] md: data-check of RAID array md1
  [832291.201064] md: md1: data-check interrupted.
  [899745.389485] md: data-check of RAID array md1
  [921395.835305] md: md1: data-check interrupted.
  [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 
seconds.
  [921588.558846]   Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu
  [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [921588.558854] task:systemd-journal state:D stack:0 pid:  376 ppid: 
1 flags:0x0220
  [921588.558859] Call Trace:
  [921588.558864]  __schedule+0x44c/0x8a0
  [921588.558872]  schedule+0x4f/0xc0
  [921588.558876]  md_write_start+0x150/0x240
  [921588.558880]  ? wait_woken+0x80/0x80
  [921588.558886]  raid5_make_request+0x88/0x890 [raid456]
  [921588.558898]  ? wait_woken+0x80/0x80
  [921588.558901]  ? mempool_kmalloc+0x17/0x20
  [921588.558904]  md_handle_request+0x12d/0x1a0
  [921588.558907]  ? __part_start_io_acct+0x51/0xf0
  [921588.558912]  md_submit_bio+0xca/0x100
  [921588.558915]  submit_bio_noacct+0x112/0x4f0
  [921588.558918]  ? ext4_fc_reserve_space+0x110/0x230
  [921588.558922]  submit_bio+0x51/0x1a0
  [921588.558925]  ? _cond_resched+0x19/0x30
  [921588.558928]  ? kmem_cache_alloc+0x38e/0x440
  [921588.558932]  ? ext4_init_io_end+0x1f/0x50
  [921588.558936]  ext4_io_submit+0x4d/0x60
  [921588.558940]  ext4_writepages+0x2c6/0xcd0
  [921588.558944]  do_writepages+0x43/0xd0
  [921588.558948]  ? do_writepages+0x43/0xd0
  [921588.558951]  ? fault_dirty_shared_page+0xa5/0x110
  [921588.558955]  __filemap_fdatawrite_range+0xcc/0x110
  [921588.558960]  file_write_and_wait_range+0x74/0xc0
  [921588.558962]  ext4_sync_file+0xf5/0x350
  [921588.558967]  vfs_fsync_range+0x49/0x80
  [921588.558970]  do_fsync+0x3d/0x70
  [921588.558973]  __x64_sys_fsync+0x14/0x20
  [921588.558976]  do_syscall_64+0x38/0x90
  [921588.558980]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [921588.558984] RIP: 0033:0x7f4c97ee832b
  [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 
004a
  [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 
7f4c97ee832b
  [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 
0021
  [921588.558995] RBP: 0001 R08:  R09: 
7ffdceb29fa8
  [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 
7ffdceb29fa8
  [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 
55ced34bcf90
  [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds.
  [921588.559018]   Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu
  [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [921588.559025] task:mysqld  state:D stack:0 pid: 1505 ppid: 
1 flags:0x
  [921588.559030] Call Trace:
  [921588.559032]  __schedule+0x44c/0x8a0
  [921588.559036]  schedule+0x4f/0xc0
  [921588.559040]  md_write_start+0x150/0x240
  [921588.559044]  ? wait_woken+0x80/0x80
  [921588.559047]  raid5_make_request+0x88/0x890 [raid456]
  [921588.559056]  ? wait_woken+0x80/0x80
  [921588.559059]  ? mempool_kmalloc+0x17/0x20
  [921588.559062]  md_handle_request+0x12d/0x1a0
  [921588.559065]  ? __part_start_io_acct+0x51/0xf0
  [921588.559068]  md_submit_bio+0xca/0x100
  [921588.559071]  submit_bio_noacct+0x112/0x4f0
  [921588.559075]  submit_bio+0x51/0x1a0
  [921588.559077]  ? _cond_resched+0x19/0x30
  [921588.559081]  ? kmem_cache_alloc+0x38e/0x440
  [921588.559084]  ? ext4_init_io_end+0x1f/0x50
  [921588.559088]  ext4_io_submit+0x4d/0x60
  [921588.559091]  ext4_writepages+0x2c6/0xcd0
  [921588.559094]  ? 

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

[Bert Rievers]

apport information

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

Title:
  Memory error while booting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just installed  ¨LinuxMint Vera Xfce" again after getting probably
  the same problem with an Ubuntu intstallation (ubuntu-22.04.1-desktop-
  amd64.iso) I tried out to get an external HDMI/VDI monitor working on
  my laptop.

  All worked fine with the default "Nouveau" video driver installed. I
  tried some xandr settings to check my external HDMI monitor, which
  basically worked. Then I noticed only the Nouveau driver was
  installed. I upgraded to the official (recommended by LinuxMint)
  NVidia-driver-525, did the compulsary reboot and got stuck with an
  "out of memory error" during that reboot (I don´t recall the literal
  message but something like that it was). The only option I had
  (because the install-USB oviously came with it) was choosing to boot
  with the previous 5.15.0-56 kernel which to my relief worked. After
  this boot I reverted to the Nouveau video driver and installed Kernel
  5.15.0-57 again. So far this works, but I dare not install the
  official NVidia-driver-525 again.

  I don´t know if this is important, but so far I have no
  /etc/X11/xorg.conf file in place. I'm still trying to find out what a
  working configuration for my laptop with a secondary external IIyama
  screen is.

  I have an Acer Nitro VN7 with 12GB of internal memory, new 240 GB SSD
  boot drive and 1TB extra SATA HDD. Booting is setup for EFI (which is
  also far from fully developed it seems) with secure boot disabled.

  b.t.w. It seems I cannot add more than one attachment to this report.

  Version log is: Ubuntu 5.15.0-57.63-generic 5.15.74

  1) lsb_release -rd:  Description: Linux Mint 21.1
    Release:21.1
  2) n.a.
  3) I expected to happen: flawless reboot
  4) What happened instead: boot got stuck on a out of memory error.

  Extra info: default-display-manager (file in /etc/X11/): /usr/sbin/lightdm
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scutec 3996 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  DistroRelease: Linux Mint 21.1
  InstallationDate: Installed on 2023-01-09 (0 days ago)
  InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217
  MachineType: Acer Aspire VN7-792G
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic 
root=UUID=fc2964e7-baed-4419-a709-e3fb79bc9e17 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  vera
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2016
  dmi.bios.release: 1.9
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd05/17/2016:br1.9:efr1.5:svnAcer:pnAspireVN7-792G:pvrV1.09:rvnAcer:rnAspireVN7-792G:rvrV1.09:cvnAcer:ct10:cvrV1.09:skuAspireVN7-792G_103B_1.09:
  dmi.product.family: SKL
  dmi.product.name: Aspire VN7-792G
  dmi.product.sku: Aspire VN7-792G_103B_1.09
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer

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


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

[Kernel-packages] [Bug 2002385] Re: Memory error while booting

[Bert Rievers]

apport information

** Tags added: apport-collected vera

** Description changed:

  I just installed  ¨LinuxMint Vera Xfce" again after getting probably the
  same problem with an Ubuntu intstallation (ubuntu-22.04.1-desktop-
  amd64.iso) I tried out to get an external HDMI/VDI monitor working on my
  laptop.
  
  All worked fine with the default "Nouveau" video driver installed. I
  tried some xandr settings to check my external HDMI monitor, which
  basically worked. Then I noticed only the Nouveau driver was installed.
  I upgraded to the official (recommended by LinuxMint) NVidia-driver-525,
  did the compulsary reboot and got stuck with an "out of memory error"
  during that reboot (I don´t recall the literal message but something
  like that it was). The only option I had (because the install-USB
  oviously came with it) was choosing to boot with the previous 5.15.0-56
  kernel which to my relief worked. After this boot I reverted to the
  Nouveau video driver and installed Kernel 5.15.0-57 again. So far this
  works, but I dare not install the official NVidia-driver-525 again.
  
  I don´t know if this is important, but so far I have no
  /etc/X11/xorg.conf file in place. I'm still trying to find out what a
  working configuration for my laptop with a secondary external IIyama
  screen is.
  
  I have an Acer Nitro VN7 with 12GB of internal memory, new 240 GB SSD
  boot drive and 1TB extra SATA HDD. Booting is setup for EFI (which is
  also far from fully developed it seems) with secure boot disabled.
  
  b.t.w. It seems I cannot add more than one attachment to this report.
  
  Version log is: Ubuntu 5.15.0-57.63-generic 5.15.74
  
  1) lsb_release -rd:  Description: Linux Mint 21.1
    Release:21.1
  2) n.a.
  3) I expected to happen: flawless reboot
  4) What happened instead: boot got stuck on a out of memory error.
  
- Extra info: default-display-manager (file in /etc/X11/):
- /usr/sbin/lightdm
+ Extra info: default-display-manager (file in /etc/X11/): /usr/sbin/lightdm
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.3
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  scutec 3996 F pulseaudio
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: XFCE
+ DistroRelease: Linux Mint 21.1
+ InstallationDate: Installed on 2023-01-09 (0 days ago)
+ InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217
+ MachineType: Acer Aspire VN7-792G
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic 
root=UUID=fc2964e7-baed-4419-a709-e3fb79bc9e17 ro quiet splash
+ ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-57-generic N/A
+  linux-backports-modules-5.15.0-57-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.9
+ Tags:  vera
+ Uname: Linux 5.15.0-57-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/17/2016
+ dmi.bios.release: 1.9
+ dmi.bios.vendor: Insyde Corp.
+ dmi.bios.version: V1.09
+ dmi.board.asset.tag: No Asset Tag
+ dmi.board.name: Aspire VN7-792G
+ dmi.board.vendor: Acer
+ dmi.board.version: V1.09
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Acer
+ dmi.chassis.version: V1.09
+ dmi.ec.firmware.release: 1.5
+ dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd05/17/2016:br1.9:efr1.5:svnAcer:pnAspireVN7-792G:pvrV1.09:rvnAcer:rnAspireVN7-792G:rvrV1.09:cvnAcer:ct10:cvrV1.09:skuAspireVN7-792G_103B_1.09:
+ dmi.product.family: SKL
+ dmi.product.name: Aspire VN7-792G
+ dmi.product.sku: Aspire VN7-792G_103B_1.09
+ dmi.product.version: V1.09
+ dmi.sys.vendor: Acer

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

Title:
  Memory error while booting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just installed  ¨LinuxMint Vera Xfce" again after getting probably
  the same problem with an Ubuntu intstallation (ubuntu-22.04.1-desktop-
  amd64.iso) I tried out to get an external HDMI/VDI monitor working on
  my laptop.

  All worked fine with the default "Nouveau" video driver installed. I
  tried some xandr settings to check my external HDMI monitor, which
  basically worked. Then I noticed only the Nouveau driver was
  installed. I upgraded to the official (recommended by LinuxMint)
  NVidia-driver-525, did the compulsary reboot and got stuck with an
  "out of memory error" during that reboot (I don´t recall the literal
  message but something like that it 

[Kernel-packages] [Bug 2000772] Re: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19

[Stefan Bader]

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

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

Title:
  powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Kinetic:
  In Progress

Bug description:
  [Impact]
  When trying to build powerpc tests from ubuntu_kernel_selftests, it 
  will fail with:
  inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3:
  /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may 
be used uninitialized [-Werror=maybe-uninitialized]
     86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack 
());
    | ^~~
  cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’:
  cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here
     25 | uint64_t val, expected[2], actual;
    | ^~
  cc1: all warnings being treated as errors

  [Fix]
  * ff446cd768 "selftests/powerpc: Avoid GCC 12 uninitialised variable warning"
  This patch can be cherry-picked into Kinetic kernel.

  [Test]
  Apply this patch to the kernel tree and build it with:
  sudo make -C linux/tools/testing/selftests TARGETS=powerpc

  With this error fixed, test compliation can finish without any issue.

  [Where problems could occur]
  Change for test case, no impact to acutal function.

  [Original Bug Report]
  Issue found with K-5.19.0-28-generic on P9 node baltar

  This should not be considered as a regression since
  ubuntu_kernel_selftests will be blocked by the net test crash before
  this powerpc tests can be started. This was found by manually running
  the test.

  Test build failed with:
  gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"unknown"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
  -m64   -no-pie  cycles_with_mmcr2_test.c ../../harness.c ../../utils.c 
../event.c ../lib.c ebb.c ebb_handler.S trace.c busy_loop.S  -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test
  In file included from /usr/include/stdio.h:906,
   from cycles_with_mmcr2_test.c:6:
  In function ‘printf’,
  inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3:
  /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may 
be used uninitialized [-Werror=maybe-uninitialized]
     86 |   return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack 
());
    |  
^~~
  cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’:
  cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here
     25 | uint64_t val, expected[2], actual;
    |^~
  cc1: all warnings being treated as errors
  make[3]: *** [../../../lib.mk:173: 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test]
 Error 1

  Please find attachment for the complete build log.

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


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

[Kernel-packages] [Bug 2001599] Re: Lost display on built-in monitor after suspend

[AceLan Kao]

** Description changed:

  [Impact]
  On some laptops, the eDP blinking slowly after resuming from S3
  
  [Fix]
- The series of patches fixed the isue
+ The series of patches which are in drp-tip fix the isue
  https://patchwork.freedesktop.org/series/110693/
  
  [Test]
  Verified on the machine which can reproduce the issue.
  
  [Where problems may occur]

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

Title:
  Lost display on built-in monitor after suspend

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  In Progress
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  On some laptops, the eDP blinking slowly after resuming from S3

  [Fix]
  The series of patches which are in drp-tip fix the isue
  https://patchwork.freedesktop.org/series/110693/

  [Test]
  Verified on the machine which can reproduce the issue.

  [Where problems may occur]

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


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

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

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

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

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

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

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

Title:
  Memory error while booting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just installed  ¨LinuxMint Vera Xfce" again after getting probably
  the same problem with an Ubuntu intstallation (ubuntu-22.04.1-desktop-
  amd64.iso) I tried out to get an external HDMI/VDI monitor working on
  my laptop.

  All worked fine with the default "Nouveau" video driver installed. I
  tried some xandr settings to check my external HDMI monitor, which
  basically worked. Then I noticed only the Nouveau driver was
  installed. I upgraded to the official (recommended by LinuxMint)
  NVidia-driver-525, did the compulsary reboot and got stuck with an
  "out of memory error" during that reboot (I don´t recall the literal
  message but something like that it was). The only option I had
  (because the install-USB oviously came with it) was choosing to boot
  with the previous 5.15.0-56 kernel which to my relief worked. After
  this boot I reverted to the Nouveau video driver and installed Kernel
  5.15.0-57 again. So far this works, but I dare not install the
  official NVidia-driver-525 again.

  I don´t know if this is important, but so far I have no
  /etc/X11/xorg.conf file in place. I'm still trying to find out what a
  working configuration for my laptop with a secondary external IIyama
  screen is.

  I have an Acer Nitro VN7 with 12GB of internal memory, new 240 GB SSD
  boot drive and 1TB extra SATA HDD. Booting is setup for EFI (which is
  also far from fully developed it seems) with secure boot disabled.

  b.t.w. It seems I cannot add more than one attachment to this report.

  Version log is: Ubuntu 5.15.0-57.63-generic 5.15.74

  1) lsb_release -rd:  Description: Linux Mint 21.1
    Release:21.1
  2) n.a.
  3) I expected to happen: flawless reboot
  4) What happened instead: boot got stuck on a out of memory error.

  Extra info: default-display-manager (file in /etc/X11/):
  /usr/sbin/lightdm

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


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

[Kernel-packages] [Bug 2002385] [NEW] Memory error while booting

[Bert Rievers]

Public bug reported:

I just installed  ¨LinuxMint Vera Xfce" again after getting probably the
same problem with an Ubuntu intstallation (ubuntu-22.04.1-desktop-
amd64.iso) I tried out to get an external HDMI/VDI monitor working on my
laptop.

All worked fine with the default "Nouveau" video driver installed. I
tried some xandr settings to check my external HDMI monitor, which
basically worked. Then I noticed only the Nouveau driver was installed.
I upgraded to the official (recommended by LinuxMint) NVidia-driver-525,
did the compulsary reboot and got stuck with an "out of memory error"
during that reboot (I don´t recall the literal message but something
like that it was). The only option I had (because the install-USB
oviously came with it) was choosing to boot with the previous 5.15.0-56
kernel which to my relief worked. After this boot I reverted to the
Nouveau video driver and installed Kernel 5.15.0-57 again. So far this
works, but I dare not install the official NVidia-driver-525 again.

I don´t know if this is important, but so far I have no
/etc/X11/xorg.conf file in place. I'm still trying to find out what a
working configuration for my laptop with a secondary external IIyama
screen is.

I have an Acer Nitro VN7 with 12GB of internal memory, new 240 GB SSD
boot drive and 1TB extra SATA HDD. Booting is setup for EFI (which is
also far from fully developed it seems) with secure boot disabled.

b.t.w. It seems I cannot add more than one attachment to this report.

Version log is: Ubuntu 5.15.0-57.63-generic 5.15.74

1) lsb_release -rd:  Description:   Linux Mint 21.1
  Release:  21.1
2) n.a.
3) I expected to happen: flawless reboot
4) What happened instead: boot got stuck on a out of memory error.

Extra info: default-display-manager (file in /etc/X11/):
/usr/sbin/lightdm

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


** Tags: 525 driver error memory nvidia on reboot with

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/2002385/+attachment/5640423/+files/lspci-vnvn.log

** Description changed:

  I just installed  ¨LinuxMint Vera Xfce" again after getting probably the
  same problem with an Ubuntu intstallation (ubuntu-22.04.1-desktop-
  amd64.iso) I tried out to get an external HDMI/VDI monitor working on my
  laptop.
  
  All worked fine with the default "Nouveau" video driver installed. I
  tried some xandr settings to check my external HDMI monitor, which
  basically worked. Then I noticed only the Nouveau driver was installed.
  I upgraded to the official (recommended by LinuxMint) NVidia-driver-525,
- did the compulary reboot and got stuck with an "out of memory error"
+ did the compulsary reboot and got stuck with an "out of memory error"
  during that reboot (I don´t recall the literal message but something
  like that it was). The only option I had (because the install-USB
  oviously came with it) was choosing to boot with the previous 5.15.0-56
  kernel which to my relief worked. After this boot I reverted to the
  Nouveau video driver and installed Kernel 5.15.0-57 again. So far this
  works, but I dare not install the official NVidia-driver-525 again.
  
  I don´t know if this is important, but so far I have no
  /etc/X11/xorg.conf file in place. I'm still trying to find out what a
  working configuration for my laptop with a secondary external IIyama
  screen is.
  
  I have an Acer Nitro VN7 with 12GB of internal memory, new 240 GB SSD
  boot drive and 1TB extra SATA HDD. Booting is setup for EFI (which is
  also far from fully developed it seems) with secure boot disabled.
  
  b.t.w. It seems I cannot add more than one attachment to this report.
  
  Version log is: Ubuntu 5.15.0-57.63-generic 5.15.74
  
  1) lsb_release -rd:  Description: Linux Mint 21.1
-   Release:21.1
+   Release:21.1
  2) n.a.
  3) I expected to happen: flawless reboot
  4) What happened instead: boot got stuck on a out of memory error.
  
  Extra info: default-display-manager (file in /etc/X11/):
  /usr/sbin/lightdm

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

Title:
  Memory error while booting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just installed  ¨LinuxMint Vera Xfce" again after getting probably
  the same problem with an Ubuntu intstallation (ubuntu-22.04.1-desktop-
  amd64.iso) I tried out to get an external HDMI/VDI monitor working on
  my laptop.

  All worked fine with the default "Nouveau" video driver installed. I
  tried some xandr settings to check my external HDMI monitor, which
  basically worked. Then I noticed only the Nouveau driver was
  installed. I upgraded to the official (recommended by LinuxMint)
  NVidia-driver-525, did the compulsary reboot and got stuck with an
  "out of memory error" during that reboot 

[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend

[Johannes Mayrhofer]

Hi,
also sorry, now for my delayed response.

My `/sys/power/mem_sleep` says:
s2idle [deep]

So, if I read this correctly, this means s3 is selected, right?
(Currently checking from a session in Kernel 5.15, as I was testing
other things not being smooth with 6.1 for me. But I presume this would
be the same for all installed Kernels, right?)

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

Title:
  cm32181 module error blocking suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to 22.04.1 (from 20.04) suspend gets interrupted and
  the system returns after a few seconds.

  journalctl output
  ```
  Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep)
  Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds
  Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... 
(elapsed 0.002 seconds) done.
  Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled.
  Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... 
(elapsed 3.894 seconds) done.
  Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use 
no_console_suspend to debug)
  Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI 
cache
  Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): 
acpi_subsys_suspend+0x0/0x60 returns -121
  Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to 
suspend: error -121
  Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk
  Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or 
early wake event detected
  Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk
  Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated 
(0x6)
  Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled.
  Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done.
  Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake 
event 0x0
  Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit
  Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle)
  Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds
  Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... 
(elapsed 0.005 seconds) done.
  Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled.
  Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... 
  Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM 
TrackPoint firmware: 0x0e, buttons: 3/3
  Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as 
/devices/rmi4-00/rmi4-00.fn03/serio2/input/input196
  Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done.
  Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use 
no_console_suspend to debug)
  Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI 
cache
  Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): 
acpi_subsys_suspend+0x0/0x60 returns -121
  Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to 
suspend: error -121
  Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk
  Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or 
early wake event detected
  Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk
  Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated 
(0x6)
  Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled.
  Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done.
  Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit
  Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: 
Deactivated successfully.
  Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake 
event 0x0
  Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to 
sleep. System resumed again: Remote I/O error
  Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda:
  Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]:  setting Advanced Power 
Management level to 0xfe (254)
  Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]:  APM_level= 254
  Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]:   
[1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 
uid=0 result="success"
  Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main 
process exited, code=exited, status=1/FAILURE
  Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed 
with result 'exit-code'.
  Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend.
  Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend.
  Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: