[Kernel-packages] [Bug 2060924] Re: [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel show " detected conn error (1020)"

[Dan Bungert]

** Package changed: subiquity (Ubuntu) => subiquity

** Changed in: subiquity
   Status: New => Triaged

** Changed in: subiquity
   Importance: Undecided => Wishlist

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

Title:
  [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel
  show " detected conn error (1020)"

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

Bug description:
  Description:
  When installing Ubuntu 24.04 in remote iscsi storage disk, the installer can 
not detect the remote iscsi storage. After install Ubuntu 24.04 to a local disk 
and boot up to OS, the OS can not detect the remote iscsi disk either. 

  Reproduce Steps:
1. Install Ubunut 24.04 
2. Boot into OS
3. perform command lsblk check remote disk, there isn't one appeared.
   
  Configuration:
  System: Lenovo SR655V3
  OS:noble-live-server-amd64-0401.iso
  BMC Version ：2.30 (Build ID: KAX321V)
  UEFI Version:3.10 (Build ID: KAE115K)
  CPU:Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz*2 M321R2GA3BB6-CQKMG*8
  NIC adapter: Mellanox ConnectX-6 Lx 10/25GbE SFP28 2-port PCIe Ethernet 
Adapte 
  storage：Lenovo D7000 or Lenovo V7000

   Expected results:
   OS can recognize the remote iscsi disk

   Actual results:
   OS cannot recognize the remote iscsi disk.

  Additional info:
1. Ubuntu 22.04 also have this issue, But RHEL9.4 hasn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2060924/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

[Dan Bungert]

Per https://irclogs.ubuntu.com/2024/04/20/%23ubuntu-release.html#t18:58
the required kernel is -31, which is currently in proposed

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in systemd source package in Noble:
  Fix Committed
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low

[dan stewart]

Many crash because VM_max_count two low.

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

Title:
  Some Games are crashing linked to a vm_max_map_count too low

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

Bug description:
  Hello there,

  I submit this request to improve the gaming experience in ubuntu for all 
users. 
  Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just 
not starting because the vm_max_map_count is locked at 65530. If we change this 
value to a value > 20, all games are working well and there is no bug 
linked to maps. 

  Some others distribution like Fedora or Pop OS, have already made the
  change few month before.

  It's time to Ubuntu to makes the change also.

  Thanks in advance for applying this request.

  How to make this change :

  One file to modify : 
  /etc/sysctl.conf
  Add this line :
  vm.max_map_count=2147483642
  Save
  Reboot and enjoy

  Best Regards
  Vinceff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2057792/+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 2056682] [NEW] NFS writeback corruption - backport needed

[Dan Aloni]

Public bug reported:

Linux kernels 5.18 to 6.7 are affected by an issue that causes lost NFS
writes.

Reported here: https://marc.info/?l=linux-nfs=170861357200809=2

**A fix for it already exists in upstream**:

https://lore.kernel.org/linux-
nfs/170907634991.24797.14120500624611379...@noble.neil.brown.name/

Please make sure Ubuntu-maintained kernel packages receive the fix.
There are many setups using NFS to write files.

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

Title:
  NFS writeback corruption - backport needed

Status in linux package in Ubuntu:
  New

Bug description:
  Linux kernels 5.18 to 6.7 are affected by an issue that causes lost
  NFS writes.

  Reported here: https://marc.info/?l=linux-nfs=170861357200809=2

  **A fix for it already exists in upstream**:

  https://lore.kernel.org/linux-
  nfs/170907634991.24797.14120500624611379...@noble.neil.brown.name/

  Please make sure Ubuntu-maintained kernel packages receive the fix.
  There are many setups using NFS to write files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056682/+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 1990272] Re: PCIe Bus Error: Uncorrected, Transaction Layer, device [8086:51b0], AER UnsupReq

[Dan Kortschak]

I am experiencing the same issue on a Thinkpad P1 Gen6.

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

Title:
  PCIe Bus Error: Uncorrected, Transaction Layer, device [8086:51b0],AER
  UnsupReq

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My dmesg is getting spammed by these AER errors. The laptop (Lenovo X1
  Extreme Gen 5, Intel Core i7-12700H) is otherwise working fine.

  The errors come in random waves of 60..160 back-to-back errors with an
  interval of 130..140 microseconds.

  Device [8086:51b0] is the PCI/thunderbolt bridge.

  [   20.086628] pcieport :00:1d.0: AER: Uncorrected (Non-Fatal) error 
received: :00:1d.0
  [   20.086671] pcieport :00:1d.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [   20.086680] pcieport :00:1d.0:   device [8086:51b0] error 
status/mask=0010/4000
  [   20.086688] pcieport :00:1d.0:[20] UnsupReq   (First)
  [   20.086694] pcieport :00:1d.0: AER:   TLP Header: 3400 2052 
 
  [   20.086810] thunderbolt :22:00.0: AER: can't recover (no 
error_detected callback)
  [   20.086846] xhci_hcd :56:00.0: AER: can't recover (no error_detected 
callback)
  [   20.086878] pcieport :00:1d.0: AER: device recovery failed
  [   20.106033] pcieport :00:1d.0: AER: Multiple Uncorrected (Non-Fatal) 
error received: :00:1d.0
  [   20.106082] pcieport :00:1d.0: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [   20.106093] pcieport :00:1d.0:   device [8086:51b0] error 
status/mask=0010/4000
  [   20.106101] pcieport :00:1d.0:[20] UnsupReq   (First)
  [   20.106108] pcieport :00:1d.0: AER:   TLP Header: 3400 2052 
 
  [   20.106219] thunderbolt :22:00.0: AER: can't recover (no 
error_detected callback)
  [   20.106257] xhci_hcd :56:00.0: AER: can't recover (no error_detected 
callback)
  [   20.106301] pcieport :00:1d.0: AER: device recovery failed

  Another wave was at 418s, 440s, 1168s, etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-48-generic 5.15.0-48.54
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  me 1827 F pulseaudio
   /dev/snd/controlC0:  me 1827 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue Sep 20 13:34:43 2022
  InstallationDate: Installed on 2022-08-31 (19 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 21DE001QMH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=d4a7fdda-30e3-439b-b327-e87d7b2bc81e ro
  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-48-generic N/A
   linux-backports-modules-5.15.0-48-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2022
  dmi.bios.release: 1.8
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3JET24W (1.08 )
  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.5
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3JET24W(1.08):bd07/21/2022:br1.8:efr1.5: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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990272/+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 2043841] Re: kernel BUG: io_uring openat triggers audit reference count underflow

[Dan Clash]

Please let me know if testing from the Canonical Kernel PPA is
sufficient or if I should test again using -proposed.

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

Title:
  kernel BUG: io_uring openat triggers audit reference count underflow

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Released

Bug description:
  I first encountered a bug in 6.2.0-1012-azure #12~22.04.1-Ubuntu that
  occurs during io_uring openat audit processing.  I have a kernel patch
  that was accepted into the upstream kernel as well as the v6.6,
  v6.5.9, and v6.1.60 releases.  The bug was first introduced in the
  upstream v5.16 kernel.

  I do not see the change yet in:

  * The Ubuntu-azure-6.2-6.2.0-1017.17_22.04.1 tag in the jammy kernel 
repository.
  * The Ubuntu-azure-6.5.0-1009.9 tag in the mantic kernel repository.

  Can this upstream commit be cherry picked?

  The upstream commit is:

  03adc61edad49e1bbecfb53f7ea5d78f398fe368

  The upstream patch thread is:

  
https://lore.kernel.org/audit/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net/T/#u

  The maintainer pull request thread is:

  https://lore.kernel.org/lkml/20231019-kampfsport-
  metapher-e5211d7be247@brauner

  The pre-patch discussion thread is:

  https://lore.kernel.org/io-
  
uring/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/T/#u

  The commit log message is:

  commit 03adc61edad49e1bbecfb53f7ea5d78f398fe368
  Author: Dan Clash 
  Date:   Thu Oct 12 14:55:18 2023 -0700

  audit,io_uring: io_uring openat triggers audit reference count
  underflow

  An io_uring openat operation can update an audit reference count
  from multiple threads resulting in the call trace below.

  A call to io_uring_submit() with a single openat op with a flag of
  IOSQE_ASYNC results in the following reference count updates.

  These first part of the system call performs two increments that
  do not race.

  do_syscall_64()
__do_sys_io_uring_enter()
  io_submit_sqes()
io_openat_prep()
  __io_openat_prep()
getname()
  getname_flags()   /* update 1 (increment) */
__audit_getname()   /* update 2 (increment) */

  The openat op is queued to an io_uring worker thread which starts the
  opportunity for a race.  The system call exit performs one decrement.

  do_syscall_64()
syscall_exit_to_user_mode()
  syscall_exit_to_user_mode_prepare()
__audit_syscall_exit()
  audit_reset_context()
 putname()  /* update 3 (decrement) */

  The io_uring worker thread performs one increment and two decrements.
  These updates can race with the system call decrement.

  io_wqe_worker()
io_worker_handle_work()
  io_wq_submit_work()
io_issue_sqe()
  io_openat()
io_openat2()
  do_filp_open()
path_openat()
  __audit_inode()   /* update 4 (increment) */
  putname() /* update 5 (decrement) */
  __audit_uring_exit()
audit_reset_context()
  putname() /* update 6 (decrement) */

  The fix is to change the refcnt member of struct audit_names
  from int to atomic_t.

  kernel BUG at fs/namei.c:262!
  Call Trace:
  ...
   ? putname+0x68/0x70
   audit_reset_context.part.0.constprop.0+0xe1/0x300
   __audit_uring_exit+0xda/0x1c0
   io_issue_sqe+0x1f3/0x450
   ? lock_timer_base+0x3b/0xd0
   io_wq_submit_work+0x8d/0x2b0
   ? __try_to_del_timer_sync+0x67/0xa0
   io_worker_handle_work+0x17c/0x2b0
   io_wqe_worker+0x10a/0x350

  Cc: sta...@vger.kernel.org
  Link: 
https://lore.kernel.org/lkml/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/
  Fixes: 5bd2182d58e9 ("audit,io_uring,io-wq: add some basic audit support 
to io_uring")
  Signed-off-by: Dan Clash 
  Link: 
https://lore.kernel.org/r/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net
  Reviewed-by: Jens Axboe 
  Signed-off-by: Christian Brauner 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043841/+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 2043841] Re: kernel BUG: io_uring openat triggers audit reference count underflow

[Dan Clash]

I previously verified that the test program hangs when 6.5.0-1011-azure is 
installed.
I have been testing with 6.5.0-1012-azure from the Canonical Kernel PPA for a 
while with no issues.
I upgraded to 6.5.0-1013-azure just now and the test program still passes.

devvm7 ~ $ uname -a
Linux daclashlinux7 6.5.0-1013-azure #13~22.04.1-Ubuntu SMP Tue Feb  6 20:34:09 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

devvm7 ~ $ sudo dmesg --clear

devvm7 ~ $ ./io_uring_open_close_audit_hang --directory /tmp/deleteme --count 
1
i=0
i=100
i=200
...
i=9800
i=9900

devvm7 ~ $ sudo dmesg
devvm7 ~ $

The test program does not hang when running with 6.5.0-1012-azure.

daclash@daclashlinux4:~$ uname -a
Linux daclashlinux4 6.5.0-1012-azure #12~22.04.1-Ubuntu SMP Tue Jan 16 21:24:44 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

daclash@daclashlinux4:~$ sudo dmesg --clear

daclash@daclashlinux4:~$ ./io_uring_open_close_audit_hang --directory 
/tmp/deleteme --count 1
...
i=9900

daclash@daclashlinux4:~$ sudo dmesg
daclash@daclashlinux4:~$


The test program does hang when running with 6.5.0-1011-azure.

daclash@daclashlinux4:~$ uname -a
Linux daclashlinux4 6.5.0-1011-azure #11~22.04.1-Ubuntu SMP Mon Jan 15 16:59:12 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

daclash@daclashlinux4:~$ sudo dmesg --clear
daclash@daclashlinux4:~$ ./io_uring_open_close_audit_hang --directory 
/tmp/deleteme --count 1
i=0
...
i=5900
i=6000
^C

daclash@daclashlinux4:~$ sudo dmesg | grep "kernel BUG at fs/namei.c"
[  125.159601] kernel BUG at fs/namei.c:264!

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

Title:
  kernel BUG: io_uring openat triggers audit reference count underflow

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Released

Bug description:
  I first encountered a bug in 6.2.0-1012-azure #12~22.04.1-Ubuntu that
  occurs during io_uring openat audit processing.  I have a kernel patch
  that was accepted into the upstream kernel as well as the v6.6,
  v6.5.9, and v6.1.60 releases.  The bug was first introduced in the
  upstream v5.16 kernel.

  I do not see the change yet in:

  * The Ubuntu-azure-6.2-6.2.0-1017.17_22.04.1 tag in the jammy kernel 
repository.
  * The Ubuntu-azure-6.5.0-1009.9 tag in the mantic kernel repository.

  Can this upstream commit be cherry picked?

  The upstream commit is:

  03adc61edad49e1bbecfb53f7ea5d78f398fe368

  The upstream patch thread is:

  
https://lore.kernel.org/audit/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net/T/#u

  The maintainer pull request thread is:

  https://lore.kernel.org/lkml/20231019-kampfsport-
  metapher-e5211d7be247@brauner

  The pre-patch discussion thread is:

  https://lore.kernel.org/io-
  
uring/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/T/#u

  The commit log message is:

  commit 03adc61edad49e1bbecfb53f7ea5d78f398fe368
  Author: Dan Clash 
  Date:   Thu Oct 12 14:55:18 2023 -0700

  audit,io_uring: io_uring openat triggers audit reference count
  underflow

  An io_uring openat operation can update an audit reference count
  from multiple threads resulting in the call trace below.

  A call to io_uring_submit() with a single openat op with a flag of
  IOSQE_ASYNC results in the following reference count updates.

  These first part of the system call performs two increments that
  do not race.

  do_syscall_64()
__do_sys_io_uring_enter()
  io_submit_sqes()
io_openat_prep()
  __io_openat_prep()
getname()
  getname_flags()   /* update 1 (increment) */
__audit_getname()   /* update 2 (increment) */

  The openat op is queued to an io_uring worker thread which starts the
  opportunity for a race.  The system call exit performs one decrement.

  do_syscall_64()
syscall_exit_to_user_mode()
  syscall_exit_to_user_mode_prepare()
__audit_syscall_exit()
  audit_reset_context()
 putname()  /* update 3 (decrement) */

  The io_uring worker thread performs one increment and two decrements.
  These updates can race with the system call decrement.

  io_wqe_worker()
io_worker_handle_work()
  io_wq_submit_work()
io_issue_sqe()
  io_openat()
io_openat2()
  do_filp_open()
path_openat()
  __audit_inode()   /* update 4 (increment) */
  putname() /* update 5 (decrement) */
  __audit_uring_exit()
audit_reset_context()
  putname() /* update 6 (decrement) */

  The fix is

[Kernel-packages] [Bug 2052411] Re: thunderbolt: interrupt for TX ring 0 is already enabled

[Dan Kortschak]

linux-image-6.5.0-14-generic does not display this behaviour so this is
clearly a regression.

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

Title:
  thunderbolt: interrupt for TX ring 0 is already enabled

Status in linux-signed package in Ubuntu:
  New

Bug description:
  After upgrading to linux-image-6.5.0-15-generic 6.5.0-15.15~22.04.1 I
  lost use of an HID device via thunderbolt (still working via USB).
  This coincided with the following dmesg trace.

  [26360.900981] [ cut here ]
  [26360.900984] thunderbolt :22:00.0: interrupt for TX ring 0 is already 
enabled
  [26360.901065] WARNING: CPU: 19 PID: 263006 at drivers/thunderbolt/nhi.c:146 
ring_interrupt_active+0x270/0x350 [thunderbolt]
  [26360.901108] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) xfrm_user xfrm_algo xt_addrtype br_netfilter ccm xt_CHECKSUM 
xt_MASQUERADE xt_conntrack snd_ctl_led snd_soc_skl_hda_dsp 
snd_soc_intel_hda_dsp_common snd_sof_probes snd_soc_hdac_hdmi cmac udp_diag 
ipt_REJECT nf_reject_ipv4 algif_hash snd_hda_codec_realtek nf_conntrack_netlink 
xt_tcpudp nft_ct snd_hda_codec_generic algif_skcipher nvidia_uvm(PO) nft_compat 
nft_masq nft_queue af_alg nft_chain_nat nf_nat_h323 nf_conntrack_h323 
nf_nat_pptp nf_conntrack_pptp nf_nat_tftp nf_conntrack_tftp nf_nat_sip 
nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp 
iptable_nat nf_nat nf_tables nf_conntrack nfnetlink_queue nf_defrag_ipv6 
nf_defrag_ipv4 libcrc32c bridge stp llc nfnetlink tcp_diag inet_diag overlay 
bnep snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common 
soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda 
snd_sof_pci snd_sof_xtensa_dsp snd_sof intel_uncore_
 frequency intel_uncore_frequency_common
  [26360.901169]  intel_tcc_cooling snd_sof_utils snd_soc_hdac_hda 
snd_hda_ext_core x86_pkg_temp_thermal intel_powerclamp snd_soc_acpi_intel_match 
coretemp snd_soc_acpi soundwire_generic_allocation soundwire_bus nvidia_drm(PO) 
iwlmvm kvm_intel snd_soc_core snd_compress nvidia_modeset(PO) i915 
snd_hda_codec_hdmi ac97_bus mac80211 snd_pcm_dmaengine kvm btusb 
crct10dif_pclmul polyval_clmulni btrtl polyval_generic uvcvideo 
ghash_clmulni_intel drm_buddy btbcm aesni_intel snd_hda_intel videobuf2_vmalloc 
hid_sensor_als btintel snd_hda_scodec_cs35l41_spi uvc ttm snd_intel_dspcfg 
crypto_simd btmtk videobuf2_memops mei_hdcp mei_pxp intel_rapl_msr libarc4 
snd_intel_sdw_acpi cryptd videobuf2_v4l2 nvidia(PO) binfmt_misc irqbypass 
snd_usb_audio hid_sensor_trigger bluetooth iwlwifi snd_hda_codec thinkpad_acpi 
industrialio_triggered_buffer videodev drm_display_helper spi_nor kfifo_buf 
snd_usbmidi_lib snd_seq_midi snd_hda_core videobuf2_common rapl 
hid_sensor_iio_common snd_ump hid_magicmouse think_l
 mi snd_hda_scodec_cs35l41_i2c
  [26360.901228]  snd_seq_midi_event ecdh_generic intel_cstate nls_iso8859_1 
serio_raw cec snd_hda_scodec_cs35l41 processor_thermal_device_pci industrialio 
firmware_attributes_class wmi_bmof input_leds joydev apple_mfi_fastcharge mc 
snd_rawmidi mtd nvram ecc snd_hwdep rc_core mei_me processor_thermal_device 
snd_hda_cs_dsp_ctls cfg80211 snd_pcm snd_seq cs_dsp hid_multitouch 
processor_thermal_rfim mei snd_soc_cs35l41_lib processor_thermal_mbox 
drm_kms_helper snd_seq_device processor_thermal_rapl i2c_algo_bit snd_timer 
intel_rapl_common mac_hid snd soundcore serial_multi_instantiate ledtrig_audio 
int3403_thermal platform_profile int340x_thermal_zone int3400_thermal 
acpi_thermal_rel acpi_pad acpi_tad sch_fq_codel msr parport_pc ppdev drm lp 
parport efi_pstore ip_tables x_tables autofs4 hid_sensor_hub cdc_ncm cdc_ether 
usbnet r8152 mii usbhid hid_generic rtsx_pci_sdmmc i2c_i801 nvme spi_intel_pci 
crc32_pclmul psmouse thunderbolt i2c_smbus spi_intel nvme_core ucsi_acpi 
intel_lpss_pci rtsx_
 pci typec_ucsi intel_lpss xhci_pci
  [26360.901294]  nvme_common idma64 xhci_pci_renesas i2c_hid_acpi typec 
i2c_hid hid video pinctrl_tigerlake wmi
  [26360.901305] CPU: 19 PID: 263006 Comm: kworker/19:2 Tainted: P   OE 
 6.5.0-15-generic #15~22.04.1-Ubuntu
  [26360.901309] Hardware name: LENOVO 21FV003CAU/21FV003CAU, BIOS N3ZET21W 
(1.08 ) 07/07/2023
  [26360.901311] Workqueue: pm pm_runtime_work
  [26360.901317] RIP: 0010:ring_interrupt_active+0x270/0x350 [thunderbolt]
  [26360.901348] Code: 89 5d c8 44 89 45 d4 e8 8e da 38 cc 44 8b 45 d4 48 8b 4d 
c0 49 89 d9 48 8b 55 b8 48 89 c6 48 c7 c7 78 70 5e c0 e8 50 7e 97 cb <0f> 0b 4d 
8b 7f 08 44 8b 5d c8 49 8b 77 18 45 84 ed 0f 85 d9 fe ff
  [26360.901351] RSP: 0018:b091a6213c48 EFLAGS: 00010046
  [26360.901354] RAX:  RBX: c05eb6db RCX: 

  [26360.901357] RDX:  RSI:  RDI: 

  [26360.901358] RBP: b091a6213c98 R08:  R09: 

  

[Kernel-packages] [Bug 2052411] [NEW] thunderbolt: interrupt for TX ring 0 is already enabled

[Dan Kortschak]

Public bug reported:

After upgrading to linux-image-6.5.0-15-generic 6.5.0-15.15~22.04.1 I
lost use of an HID device via thunderbolt (still working via USB). This
coincided with the following dmesg trace.

[26360.900981] [ cut here ]
[26360.900984] thunderbolt :22:00.0: interrupt for TX ring 0 is already 
enabled
[26360.901065] WARNING: CPU: 19 PID: 263006 at drivers/thunderbolt/nhi.c:146 
ring_interrupt_active+0x270/0x350 [thunderbolt]
[26360.901108] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) xfrm_user xfrm_algo xt_addrtype br_netfilter ccm xt_CHECKSUM 
xt_MASQUERADE xt_conntrack snd_ctl_led snd_soc_skl_hda_dsp 
snd_soc_intel_hda_dsp_common snd_sof_probes snd_soc_hdac_hdmi cmac udp_diag 
ipt_REJECT nf_reject_ipv4 algif_hash snd_hda_codec_realtek nf_conntrack_netlink 
xt_tcpudp nft_ct snd_hda_codec_generic algif_skcipher nvidia_uvm(PO) nft_compat 
nft_masq nft_queue af_alg nft_chain_nat nf_nat_h323 nf_conntrack_h323 
nf_nat_pptp nf_conntrack_pptp nf_nat_tftp nf_conntrack_tftp nf_nat_sip 
nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp 
iptable_nat nf_nat nf_tables nf_conntrack nfnetlink_queue nf_defrag_ipv6 
nf_defrag_ipv4 libcrc32c bridge stp llc nfnetlink tcp_diag inet_diag overlay 
bnep snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common 
soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda 
snd_sof_pci snd_sof_xtensa_dsp snd_sof intel_uncore_fr
 equency intel_uncore_frequency_common
[26360.901169]  intel_tcc_cooling snd_sof_utils snd_soc_hdac_hda 
snd_hda_ext_core x86_pkg_temp_thermal intel_powerclamp snd_soc_acpi_intel_match 
coretemp snd_soc_acpi soundwire_generic_allocation soundwire_bus nvidia_drm(PO) 
iwlmvm kvm_intel snd_soc_core snd_compress nvidia_modeset(PO) i915 
snd_hda_codec_hdmi ac97_bus mac80211 snd_pcm_dmaengine kvm btusb 
crct10dif_pclmul polyval_clmulni btrtl polyval_generic uvcvideo 
ghash_clmulni_intel drm_buddy btbcm aesni_intel snd_hda_intel videobuf2_vmalloc 
hid_sensor_als btintel snd_hda_scodec_cs35l41_spi uvc ttm snd_intel_dspcfg 
crypto_simd btmtk videobuf2_memops mei_hdcp mei_pxp intel_rapl_msr libarc4 
snd_intel_sdw_acpi cryptd videobuf2_v4l2 nvidia(PO) binfmt_misc irqbypass 
snd_usb_audio hid_sensor_trigger bluetooth iwlwifi snd_hda_codec thinkpad_acpi 
industrialio_triggered_buffer videodev drm_display_helper spi_nor kfifo_buf 
snd_usbmidi_lib snd_seq_midi snd_hda_core videobuf2_common rapl 
hid_sensor_iio_common snd_ump hid_magicmouse think_lmi
  snd_hda_scodec_cs35l41_i2c
[26360.901228]  snd_seq_midi_event ecdh_generic intel_cstate nls_iso8859_1 
serio_raw cec snd_hda_scodec_cs35l41 processor_thermal_device_pci industrialio 
firmware_attributes_class wmi_bmof input_leds joydev apple_mfi_fastcharge mc 
snd_rawmidi mtd nvram ecc snd_hwdep rc_core mei_me processor_thermal_device 
snd_hda_cs_dsp_ctls cfg80211 snd_pcm snd_seq cs_dsp hid_multitouch 
processor_thermal_rfim mei snd_soc_cs35l41_lib processor_thermal_mbox 
drm_kms_helper snd_seq_device processor_thermal_rapl i2c_algo_bit snd_timer 
intel_rapl_common mac_hid snd soundcore serial_multi_instantiate ledtrig_audio 
int3403_thermal platform_profile int340x_thermal_zone int3400_thermal 
acpi_thermal_rel acpi_pad acpi_tad sch_fq_codel msr parport_pc ppdev drm lp 
parport efi_pstore ip_tables x_tables autofs4 hid_sensor_hub cdc_ncm cdc_ether 
usbnet r8152 mii usbhid hid_generic rtsx_pci_sdmmc i2c_i801 nvme spi_intel_pci 
crc32_pclmul psmouse thunderbolt i2c_smbus spi_intel nvme_core ucsi_acpi 
intel_lpss_pci rtsx_pc
 i typec_ucsi intel_lpss xhci_pci
[26360.901294]  nvme_common idma64 xhci_pci_renesas i2c_hid_acpi typec i2c_hid 
hid video pinctrl_tigerlake wmi
[26360.901305] CPU: 19 PID: 263006 Comm: kworker/19:2 Tainted: P   OE   
   6.5.0-15-generic #15~22.04.1-Ubuntu
[26360.901309] Hardware name: LENOVO 21FV003CAU/21FV003CAU, BIOS N3ZET21W (1.08 
) 07/07/2023
[26360.901311] Workqueue: pm pm_runtime_work
[26360.901317] RIP: 0010:ring_interrupt_active+0x270/0x350 [thunderbolt]
[26360.901348] Code: 89 5d c8 44 89 45 d4 e8 8e da 38 cc 44 8b 45 d4 48 8b 4d 
c0 49 89 d9 48 8b 55 b8 48 89 c6 48 c7 c7 78 70 5e c0 e8 50 7e 97 cb <0f> 0b 4d 
8b 7f 08 44 8b 5d c8 49 8b 77 18 45 84 ed 0f 85 d9 fe ff
[26360.901351] RSP: 0018:b091a6213c48 EFLAGS: 00010046
[26360.901354] RAX:  RBX: c05eb6db RCX: 
[26360.901357] RDX:  RSI:  RDI: 
[26360.901358] RBP: b091a6213c98 R08:  R09: 
[26360.901360] R10:  R11:  R12: 0001
[26360.901361] R13: 0001 R14: 00038200 R15: 9763017d0240
[26360.901363] FS:  () GS:976a3f6c() 
knlGS:
[26360.901366] CS:  0010 DS:  ES:  CR0: 80050033
[26360.901368] CR2: 7ffc979f4d00 CR3: 00010fd6 CR4: 00752ee0
[26360.901370] PKRU: 

[Kernel-packages] [Bug 2047153] Re: Intel TPM: tpm_crb: probe of MSFT0101:00 failed with error 378

[Dan Podeanu]

Agreed, fixed in linux-generic-hwe-22.04 6.5.0.14.14~22.04.7 -
resolving.

** Changed in: linux-signed-hwe-6.2 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Intel TPM: tpm_crb: probe of MSFT0101:00 failed with error 378

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Fix Released

Bug description:
  Linux kernel 6.2.0-37 introduces a regression which breaks Intel TPM
  detection at boot. This was reported in the upstream kernel, and a fix
  is available.

  https://bugzilla.kernel.org/show_bug.cgi?id=217804
  
https://github.com/torvalds/linux/commit/8f7f35e5aa6f2182eabcfa3abef4d898a48e9aa8

  # dmesg|grep -i tpm
  [0.00] efi: ACPI=0x7564 ACPI 2.0=0x75640014 
TPMFinalLog=0x7560f000 SMBIOS=0x75cc8000 SMBIOS 3.0=0x75cc7000 
MEMATTR=0x6e49a018 ESRT=0x6e8b3198 RNG=0x754fe018 TPMEventLog=0x6e2a2018 
  [0.014972] ACPI: TPM2 0x7550 4C (v04 ALASKA A M I
0001 AMI  )
  [0.015001] ACPI: Reserving TPM2 table memory at [mem 
0x7550-0x7550004b]
  [0.391710] tpm_crb: probe of MSFT0101:00 failed with error 378
  [1.119989] ima: No TPM chip found, activating TPM-bypass!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Fri Dec 22 00:01:29 2023
  InstallationDate: Installed on 2023-04-09 (256 days ago)
  InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release 
amd64 (20230217.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2047153/+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 2043841] Re: kernel BUG: io_uring openat triggers audit reference count underflow

[Dan Clash]

epository.
  * The Ubuntu-azure-6.5.0-1009.9 tag in the mantic kernel repository.

  Can this upstream commit be cherry picked?

  The upstream commit is:

  03adc61edad49e1bbecfb53f7ea5d78f398fe368

  The upstream patch thread is:

  
https://lore.kernel.org/audit/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net/T/#u

  The maintainer pull request thread is:

  https://lore.kernel.org/lkml/20231019-kampfsport-
  metapher-e5211d7be247@brauner

  The pre-patch discussion thread is:

  https://lore.kernel.org/io-
  
uring/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/T/#u

  The commit log message is:

  commit 03adc61edad49e1bbecfb53f7ea5d78f398fe368
  Author: Dan Clash 
  Date:   Thu Oct 12 14:55:18 2023 -0700

  audit,io_uring: io_uring openat triggers audit reference count
  underflow

  An io_uring openat operation can update an audit reference count
  from multiple threads resulting in the call trace below.

  A call to io_uring_submit() with a single openat op with a flag of
  IOSQE_ASYNC results in the following reference count updates.

  These first part of the system call performs two increments that
  do not race.

  do_syscall_64()
__do_sys_io_uring_enter()
  io_submit_sqes()
io_openat_prep()
  __io_openat_prep()
getname()
  getname_flags()   /* update 1 (increment) */
__audit_getname()   /* update 2 (increment) */

  The openat op is queued to an io_uring worker thread which starts the
  opportunity for a race.  The system call exit performs one decrement.

  do_syscall_64()
syscall_exit_to_user_mode()
  syscall_exit_to_user_mode_prepare()
__audit_syscall_exit()
  audit_reset_context()
 putname()  /* update 3 (decrement) */

  The io_uring worker thread performs one increment and two decrements.
  These updates can race with the system call decrement.

  io_wqe_worker()
io_worker_handle_work()
  io_wq_submit_work()
io_issue_sqe()
  io_openat()
io_openat2()
  do_filp_open()
path_openat()
  __audit_inode()   /* update 4 (increment) */
  putname() /* update 5 (decrement) */
  __audit_uring_exit()
audit_reset_context()
  putname() /* update 6 (decrement) */

  The fix is to change the refcnt member of struct audit_names
  from int to atomic_t.

  kernel BUG at fs/namei.c:262!
  Call Trace:
  ...
   ? putname+0x68/0x70
   audit_reset_context.part.0.constprop.0+0xe1/0x300
   __audit_uring_exit+0xda/0x1c0
   io_issue_sqe+0x1f3/0x450
   ? lock_timer_base+0x3b/0xd0
   io_wq_submit_work+0x8d/0x2b0
   ? __try_to_del_timer_sync+0x67/0xa0
   io_worker_handle_work+0x17c/0x2b0
   io_wqe_worker+0x10a/0x350

  Cc: sta...@vger.kernel.org
  Link: 
https://lore.kernel.org/lkml/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/
  Fixes: 5bd2182d58e9 ("audit,io_uring,io-wq: add some basic audit support 
to io_uring")
  Signed-off-by: Dan Clash 
  Link: 
https://lore.kernel.org/r/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net
  Reviewed-by: Jens Axboe 
  Signed-off-by: Christian Brauner 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043841/+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 2047153] [NEW] Intel TPM: tpm_crb: probe of MSFT0101:00 failed with error 378

[Dan Podeanu]

Public bug reported:

Linux kernel 6.2.0-37 introduces a regression which breaks Intel TPM
detection at boot. This was reported in the upstream kernel, and a fix
is available.

https://bugzilla.kernel.org/show_bug.cgi?id=217804
https://github.com/torvalds/linux/commit/8f7f35e5aa6f2182eabcfa3abef4d898a48e9aa8

# dmesg|grep -i tpm
[0.00] efi: ACPI=0x7564 ACPI 2.0=0x75640014 TPMFinalLog=0x7560f000 
SMBIOS=0x75cc8000 SMBIOS 3.0=0x75cc7000 MEMATTR=0x6e49a018 ESRT=0x6e8b3198 
RNG=0x754fe018 TPMEventLog=0x6e2a2018 
[0.014972] ACPI: TPM2 0x7550 4C (v04 ALASKA A M I
0001 AMI  )
[0.015001] ACPI: Reserving TPM2 table memory at [mem 0x7550-0x7550004b]
[0.391710] tpm_crb: probe of MSFT0101:00 failed with error 378
[1.119989] ima: No TPM chip found, activating TPM-bypass!

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Fri Dec 22 00:01:29 2023
InstallationDate: Installed on 2023-04-09 (256 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230217.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-6.2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy uec-images

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

Title:
  Intel TPM: tpm_crb: probe of MSFT0101:00 failed with error 378

Status in linux-signed-hwe-6.2 package in Ubuntu:
  New

Bug description:
  Linux kernel 6.2.0-37 introduces a regression which breaks Intel TPM
  detection at boot. This was reported in the upstream kernel, and a fix
  is available.

  https://bugzilla.kernel.org/show_bug.cgi?id=217804
  
https://github.com/torvalds/linux/commit/8f7f35e5aa6f2182eabcfa3abef4d898a48e9aa8

  # dmesg|grep -i tpm
  [0.00] efi: ACPI=0x7564 ACPI 2.0=0x75640014 
TPMFinalLog=0x7560f000 SMBIOS=0x75cc8000 SMBIOS 3.0=0x75cc7000 
MEMATTR=0x6e49a018 ESRT=0x6e8b3198 RNG=0x754fe018 TPMEventLog=0x6e2a2018 
  [0.014972] ACPI: TPM2 0x7550 4C (v04 ALASKA A M I
0001 AMI  )
  [0.015001] ACPI: Reserving TPM2 table memory at [mem 
0x7550-0x7550004b]
  [0.391710] tpm_crb: probe of MSFT0101:00 failed with error 378
  [1.119989] ima: No TPM chip found, activating TPM-bypass!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Fri Dec 22 00:01:29 2023
  InstallationDate: Installed on 2023-04-09 (256 days ago)
  InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release 
amd64 (20230217.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2047153/+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 2043841] Re: kernel BUG: io_uring openat triggers audit reference count underflow

[Dan Clash]

This bug is a in the Linux kernel, specifically in the filesystem /
io_uring / audit areas.

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

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

Title:
  kernel BUG: io_uring openat triggers audit reference count underflow

Status in linux-azure-6.2 package in Ubuntu:
  New

Bug description:
  I first encountered a bug in 6.2.0-1012-azure #12~22.04.1-Ubuntu that
  occurs during io_uring openat audit processing.  I have a kernel patch
  that was accepted into the upstream kernel as well as the v6.6,
  v6.5.9, and v6.1.60 releases.  The bug was first introduced in the
  upstream v5.16 kernel.

  I do not see the change yet in:

  * The Ubuntu-azure-6.2-6.2.0-1017.17_22.04.1 tag in the jammy kernel 
repository.
  * The Ubuntu-azure-6.5.0-1009.9 tag in the mantic kernel repository.

  Can this upstream commit be cherry picked?

  The upstream commit is:

  03adc61edad49e1bbecfb53f7ea5d78f398fe368

  The upstream patch thread is:

  
https://lore.kernel.org/audit/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net/T/#u

  The maintainer pull request thread is:

  https://lore.kernel.org/lkml/20231019-kampfsport-
  metapher-e5211d7be247@brauner

  The pre-patch discussion thread is:

  https://lore.kernel.org/io-
  
uring/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/T/#u

  The commit log message is:

  commit 03adc61edad49e1bbecfb53f7ea5d78f398fe368
  Author: Dan Clash 
  Date:   Thu Oct 12 14:55:18 2023 -0700

  audit,io_uring: io_uring openat triggers audit reference count
  underflow

  An io_uring openat operation can update an audit reference count
  from multiple threads resulting in the call trace below.

  A call to io_uring_submit() with a single openat op with a flag of
  IOSQE_ASYNC results in the following reference count updates.

  These first part of the system call performs two increments that
  do not race.

  do_syscall_64()
__do_sys_io_uring_enter()
  io_submit_sqes()
io_openat_prep()
  __io_openat_prep()
getname()
  getname_flags()   /* update 1 (increment) */
__audit_getname()   /* update 2 (increment) */

  The openat op is queued to an io_uring worker thread which starts the
  opportunity for a race.  The system call exit performs one decrement.

  do_syscall_64()
syscall_exit_to_user_mode()
  syscall_exit_to_user_mode_prepare()
__audit_syscall_exit()
  audit_reset_context()
 putname()  /* update 3 (decrement) */

  The io_uring worker thread performs one increment and two decrements.
  These updates can race with the system call decrement.

  io_wqe_worker()
io_worker_handle_work()
  io_wq_submit_work()
io_issue_sqe()
  io_openat()
io_openat2()
  do_filp_open()
path_openat()
  __audit_inode()   /* update 4 (increment) */
  putname() /* update 5 (decrement) */
  __audit_uring_exit()
audit_reset_context()
  putname() /* update 6 (decrement) */

  The fix is to change the refcnt member of struct audit_names
  from int to atomic_t.

  kernel BUG at fs/namei.c:262!
  Call Trace:
  ...
   ? putname+0x68/0x70
   audit_reset_context.part.0.constprop.0+0xe1/0x300
   __audit_uring_exit+0xda/0x1c0
   io_issue_sqe+0x1f3/0x450
   ? lock_timer_base+0x3b/0xd0
   io_wq_submit_work+0x8d/0x2b0
   ? __try_to_del_timer_sync+0x67/0xa0
   io_worker_handle_work+0x17c/0x2b0
   io_wqe_worker+0x10a/0x350

  Cc: sta...@vger.kernel.org
  Link: 
https://lore.kernel.org/lkml/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/
  Fixes: 5bd2182d58e9 ("audit,io_uring,io-wq: add some basic audit support 
to io_uring")
  Signed-off-by: Dan Clash 
  Link: 
https://lore.kernel.org/r/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net
  Reviewed-by: Jens Axboe 
  Signed-off-by: Christian Brauner 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure-6.2/+bug/2043841/+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 2040106] Re: firmware broken after upgrade to Ubuntu 23.10

[Dan]

@Juerg, here's to you the logs that I grabbed from /var/log/syslog.
I pasted what I believe it's the useful part in 
https://pastebin.com/raw/KRLAkS4J - anyway, it keeps going and going.

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

Title:
  firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

   * Focal preinstalled systems with OEM kernel, if force upgraded to
  interim releases, before transitional packages have been made
  available resulted in systems having been stuck on focal oem kernel
  and not getting any kernel updates.

   * Reintroduce all focal oem kernel transitionals to trigger upgrade
  to hwe kernel in all stable releases for the oem-20.04* kernels

  [ Test Plan ]

   * Starting with focal, install linux-image-oem-20.04* 
linux-headers-oem-20.04* metapackages
   * Force upgrade to mantic
   * Observe that all oem-20.04 meta packages got upgraded and rolled to 
generic hwe kernel (of appropriate version for jammy & mantic)

  [ Where problems could occur ]

   * This may trigger dkms package recompilation, and nvidia driver missmatches
   * Likely users will have to rerun `ubuntu-drivers` or use additional drivers 
GUI to reinstall nvidia drivers
   * Users may experience jump from v5.10 kernel to v6.5 kernel

  [ Other Info ]

   * Original bug report

  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  apt-cache policy linux-firmware
  linux-firmware:
    Installed: 20230919.git3672ccab-0ubuntu2.1
    Candidate: 20230919.git3672ccab-0ubuntu2.1
    Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  dmi.sys.vendor: Dell Inc.

To 

[Kernel-packages] [Bug 2040106] Re: firmware broken after upgrade to Ubuntu 23.10

[Dan]

Hello everyone, just chiming in to say that my Ubuntu was installed by me, no 
OEM at all, and I am on 6.5.0-10-generic, and still I was affected by this 
issue.
Manually copying iwlwifi* and intel/ibt-* from linux-firmware-20230804.tar.xz 
solved the issue for me.

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

Title:
  firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

   * Focal preinstalled systems with OEM kernel, if force upgraded to
  interim releases, before transitional packages have been made
  available resulted in systems having been stuck on focal oem kernel
  and not getting any kernel updates.

   * Reintroduce all focal oem kernel transitionals to trigger upgrade
  to hwe kernel in all stable releases for the oem-20.04* kernels

  [ Test Plan ]

   * Starting with focal, install linux-image-oem-20.04* 
linux-headers-oem-20.04* metapackages
   * Force upgrade to mantic
   * Observe that all oem-20.04 meta packages got upgraded and rolled to 
generic hwe kernel (of appropriate version for jammy & mantic)

  [ Where problems could occur ]

   * This may trigger dkms package recompilation, and nvidia driver missmatches
   * Likely users will have to rerun `ubuntu-drivers` or use additional drivers 
GUI to reinstall nvidia drivers
   * Users may experience jump from v5.10 kernel to v6.5 kernel

  [ Other Info ]

   * Original bug report

  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  apt-cache policy linux-firmware
  linux-firmware:
    Installed: 20230919.git3672ccab-0ubuntu2.1
    Candidate: 20230919.git3672ccab-0ubuntu2.1
    Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  

[Kernel-packages] [Bug 1518457] Re: kswapd0 100% CPU usage

[Dan Streetman]

** Changed in: linux (Ubuntu)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: linux (Ubuntu Xenial)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

** Changed in: linux (Ubuntu Yakkety)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

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

Title:
  kswapd0 100% CPU usage

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  As per bug 721896 and various others:

  I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory).
  Occasionally (about once a day), kswapd0 falls into a busy loop and
  spins on 100% CPU usage indefinitely. This can be provoked by
  copying/writing large files (e.g. dding a 256MB file), but it happens
  occasionally otherwise. System memory usage (not including
  buffers/caches) currently sits at 36%, which is typical[1]. Initially
  I had no swap space configured; I've since tried enabling a 256MB swap
  file, but the problem continues to occur and no swap space is used.
  The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`.

  Happy to provide further information/take further debugging actions.

  
  [1] Full output from `free`:
   total   used   free sharedbuffers cached
  Mem:   1014936 483448 531488  28556   9756 112700
  -/+ buffers/cache: 360992 653944
  Swap:   262140  0 262140

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 19 19:40 seq
   crw-rw 1 root audio 116, 33 Nov 19 19:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Fri Nov 20 20:44:30 2015
  Ec2AMI: ami-1c552a76
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: t2.micro
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 
net.ifnames=0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1518457/+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 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

[Dan]

Can confirm it affected me as well for what regards the wireless. I don't use 
Bluetooth so I can't confirm on that side.
The solution with linux-firmware-20230804.tar.xz worked for me.

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

Title:
  Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  
  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  
  apt-cache policy linux-firmware
  linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2040106/+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 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

[Dan O'Neill]

Description: Ubuntu 22.04.3 LTS
Release: 22.04

uname -a output:
Linux olive 6.2.0-36-generic #37~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct  9 
15:34:04 UTC 2 x86_64 x86_64 x86_64 GNU/Linux


I modified /etc/default/grub with
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0 
intel_idle.max_cstate=2"

and it only made the problem worse.

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

Title:
  [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0
  intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.19 package in Ubuntu:
  Fix Released
Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux-hwe-5.19 source package in Lunar:
  Invalid
Status in linux-hwe-6.2 source package in Lunar:
  Invalid

Bug description:
  Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @
  18/1/2022

  Booting into desktop gets heavy screen flickering and disforming (unusable)
  both booting on xorg and wayland

  on kernel 5.13 it did not occur so heavy (only little glitches once in
  a while see bug 1948778)

  adding the kernel parameter i915.enable_dc=0 intel_idle.max_cstate=2
  fixed this

  i had these same bugs on this machine before:

  https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644

  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1201 F pipewire-media-
    lotuspsychje   1207 F pulseaudio
   /dev/snd/seq:lotuspsychje   1193 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 04:22:00 2022
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N7x0WU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash 
intel_idle.max_cstate=4 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.release: 7.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N7x0WU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.14
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N7x0WU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+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 2038939] [NEW] Kernels are not compiled with V4L2 support

[Dan]

Public bug reported:

 * Distribution: VM Distribution is Ubuntu 22.04 x86_64, Host
Distribution is Ubuntu 22.04 x86_64

# Issue description

I can't install the v4l2loopback kernel modules in the VM because the
kernel was compiled without v4l2 support. Please compile the kernel with
v4l2 support or tell me how to do this. Please see this [relevant
issue](https://github.com/umlaeute/v4l2loopback/issues/59#issuecomment-351082960)
in v4l2loopback alotting to kernel compilation without v4l2 support


# Steps to reproduce

 1. `lxc launch ubuntu:22.04 ubuntu-vm --vm`
 2. `lxc exec ubuntu-vm -- su - ubuntu`
 3. `sudo apt update`
 4. `sudo apt install -y gcc make build-essential`
 5. `git clone https://github.com/umlaeute/v4l2loopback`
 6. `cd v4l2loopback`
 7. `make`

# Information to attach

```
ubuntu@ubuntu-vm:~/doc/v4l2loopback$ make
Building v4l2-loopback driver...
make -C /lib/modules/`uname -r`/build M=/home/ubuntu/doc/v4l2loopback 
KCPPFLAGS="-DSNAPSHOT_VERSION='"0.12.7-398-g5bb9bed"'" modules
make[1]: Entering directory '/usr/src/linux-headers-5.15.0-1044-kvm'
  CC [M]  /home/ubuntu/doc/v4l2loopback/v4l2loopback.o
  MODPOST /home/ubuntu/doc/v4l2loopback/Module.symvers
ERROR: modpost: "video_ioctl2" [/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] 
undefined!
ERROR: modpost: "v4l2_event_unsubscribe" 
[/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] undefined!
ERROR: modpost: "v4l2_event_pending" 
[/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] undefined!
ERROR: modpost: "v4l2_fh_add" [/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] 
undefined!
ERROR: modpost: "v4l2_fh_init" [/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] 
undefined!
ERROR: modpost: "v4l2_format_info" 
[/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] undefined!
ERROR: modpost: "v4l2_fh_exit" [/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] 
undefined!
ERROR: modpost: "v4l2_fh_del" [/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] 
undefined!
ERROR: modpost: "video_devdata" [/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] 
undefined!
ERROR: modpost: "__video_register_device" 
[/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] undefined!
WARNING: modpost: suppressed 14 unresolved symbol warnings because there were 
too many)
make[2]: *** [scripts/Makefile.modpost:133: 
/home/ubuntu/doc/v4l2loopback/Module.symvers] Error 1
make[2]: *** Deleting file '/home/ubuntu/doc/v4l2loopback/Module.symvers'
make[1]: *** [Makefile:1830: modules] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.15.0-1044-kvm'
make: *** [Makefile:53: v4l2loopback.ko] Error 2
```

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

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

Title:
  Kernels are not compiled with V4L2 support

Status in linux-meta-kvm package in Ubuntu:
  New

Bug description:
   * Distribution: VM Distribution is Ubuntu 22.04 x86_64, Host
  Distribution is Ubuntu 22.04 x86_64

  # Issue description

  I can't install the v4l2loopback kernel modules in the VM because the
  kernel was compiled without v4l2 support. Please compile the kernel
  with v4l2 support or tell me how to do this. Please see this [relevant
  
issue](https://github.com/umlaeute/v4l2loopback/issues/59#issuecomment-351082960)
  in v4l2loopback alotting to kernel compilation without v4l2 support


  # Steps to reproduce

   1. `lxc launch ubuntu:22.04 ubuntu-vm --vm`
   2. `lxc exec ubuntu-vm -- su - ubuntu`
   3. `sudo apt update`
   4. `sudo apt install -y gcc make build-essential`
   5. `git clone https://github.com/umlaeute/v4l2loopback`
   6. `cd v4l2loopback`
   7. `make`

  # Information to attach

  ```
  ubuntu@ubuntu-vm:~/doc/v4l2loopback$ make
  Building v4l2-loopback driver...
  make -C /lib/modules/`uname -r`/build M=/home/ubuntu/doc/v4l2loopback 
KCPPFLAGS="-DSNAPSHOT_VERSION='"0.12.7-398-g5bb9bed"'" modules
  make[1]: Entering directory '/usr/src/linux-headers-5.15.0-1044-kvm'
CC [M]  /home/ubuntu/doc/v4l2loopback/v4l2loopback.o
MODPOST /home/ubuntu/doc/v4l2loopback/Module.symvers
  ERROR: modpost: "video_ioctl2" 
[/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] undefined!
  ERROR: modpost: "v4l2_event_unsubscribe" 
[/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] undefined!
  ERROR: modpost: "v4l2_event_pending" 
[/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] undefined!
  ERROR: modpost: "v4l2_fh_add" [/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] 
undefined!
  ERROR: modpost: "v4l2_fh_init" 
[/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] undefined!
  ERROR: modpost: "v4l2_format_info" 
[/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] undefined!
  ERROR: modpost: "v4l2_fh_exit" 
[/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] undefined!
  ERROR: modpost: "v4l2_fh_del" [/home/ubuntu/doc/v4l2loopback/v4l2loopback.ko] 
undefined!
  ERROR: modpost: "video_devdata" 

[Kernel-packages] [Bug 2033944] Re: Thinkpad X1 Carbon sound is still tinny

[Dan Gillmor]

** Description changed:

  This is not a new issue, and despite the fix reported in
  https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108 the
- sound remains thin and lacking bass in Thinkpad Xi Carbon models up to
+ sound remains thin and lacking bass in Thinkpad X1 Carbon models up to
  and including the latest generations.
  
  Hoping that this will be dealt with eventually, but definitely not
  holding my breath. (I've had this issue on X1 Carbon Generation 7, 9,
  and now 11.
  
  Running Ubuntu 22.04.3
  alsa-ucm-conf:
-   Installed: 1.2.6.3-1ubuntu1.7
-   Candidate: 1.2.6.3-1ubuntu1.7
-   Version table:
-  *** 1.2.6.3-1ubuntu1.7 500
- 500 http://jp.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
- 500 http://jp.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
- 100 /var/lib/dpkg/status
-  1.2.6.3-1ubuntu1 500
- 500 http://jp.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
- 500 http://jp.archive.ubuntu.com/ubuntu jammy/main i386 Packages
+   Installed: 1.2.6.3-1ubuntu1.7
+   Candidate: 1.2.6.3-1ubuntu1.7
+   Version table:
+  *** 1.2.6.3-1ubuntu1.7 500
+ 500 http://jp.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
+ 500 http://jp.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
+ 100 /var/lib/dpkg/status
+  1.2.6.3-1ubuntu1 500
+ 500 http://jp.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
+ 500 http://jp.archive.ubuntu.com/ubuntu jammy/main i386 Packages
  
  What I expect: Sound from all speakers including some bass
  What happens: Very thin, tinny sound, no bass.

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

Title:
  Thinkpad X1 Carbon sound is still tinny

Status in alsa-ucm-conf package in Ubuntu:
  New

Bug description:
  This is not a new issue, and despite the fix reported in
  https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108
  the sound remains thin and lacking bass in Thinkpad X1 Carbon models
  up to and including the latest generations.

  Hoping that this will be dealt with eventually, but definitely not
  holding my breath. (I've had this issue on X1 Carbon Generation 7, 9,
  and now 11.

  Running Ubuntu 22.04.3
  alsa-ucm-conf:
    Installed: 1.2.6.3-1ubuntu1.7
    Candidate: 1.2.6.3-1ubuntu1.7
    Version table:
   *** 1.2.6.3-1ubuntu1.7 500
  500 http://jp.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://jp.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.2.6.3-1ubuntu1 500
  500 http://jp.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://jp.archive.ubuntu.com/ubuntu jammy/main i386 Packages

  What I expect: Sound from all speakers including some bass
  What happens: Very thin, tinny sound, no bass.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2033944/+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 2033944] [NEW] Thinkpad X1 Carbon sound is still tinny

[Dan Gillmor]

Public bug reported:

This is not a new issue, and despite the fix reported in
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108 the
sound remains thin and lacking bass in Thinkpad Xi Carbon models up to
and including the latest generations.

Hoping that this will be dealt with eventually, but definitely not
holding my breath. (I've had this issue on X1 Carbon Generation 7, 9,
and now 11.

Running Ubuntu 22.04.3
alsa-ucm-conf:
  Installed: 1.2.6.3-1ubuntu1.7
  Candidate: 1.2.6.3-1ubuntu1.7
  Version table:
 *** 1.2.6.3-1ubuntu1.7 500
500 http://jp.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://jp.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
100 /var/lib/dpkg/status
 1.2.6.3-1ubuntu1 500
500 http://jp.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
500 http://jp.archive.ubuntu.com/ubuntu jammy/main i386 Packages

What I expect: Sound from all speakers including some bass
What happens: Very thin, tinny sound, no bass.

** Affects: alsa-ucm-conf (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Thinkpad X1 Carbon sound is still tinny

Status in alsa-ucm-conf package in Ubuntu:
  New

Bug description:
  This is not a new issue, and despite the fix reported in
  https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108
  the sound remains thin and lacking bass in Thinkpad Xi Carbon models
  up to and including the latest generations.

  Hoping that this will be dealt with eventually, but definitely not
  holding my breath. (I've had this issue on X1 Carbon Generation 7, 9,
  and now 11.

  Running Ubuntu 22.04.3
  alsa-ucm-conf:
Installed: 1.2.6.3-1ubuntu1.7
Candidate: 1.2.6.3-1ubuntu1.7
Version table:
   *** 1.2.6.3-1ubuntu1.7 500
  500 http://jp.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://jp.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.2.6.3-1ubuntu1 500
  500 http://jp.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://jp.archive.ubuntu.com/ubuntu jammy/main i386 Packages

  What I expect: Sound from all speakers including some bass
  What happens: Very thin, tinny sound, no bass.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2033944/+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 1990621] Re: PXE Boot contains wrong suggested link to ISO for live file system

[Dan Bungert]

Hi Dominik,

Some suggestions:
* I like that we are disambiguating obtaining 22.04.0 versus something that 
acquires the latest version.  I think that's a nice improvement overall, not 
just for casper.
* I believe that creating the backend for those -latest URLs would need 
ubuntu-cdimage changes
* Assuming the above will be done, we'll want that -latest support in casper on 
main branch first.  But presumably constrained to LTS ISOs.
* A debdiff is entirely fine, or you may find it more convenient to propose MPs 
against https://git.launchpad.net/casper

In the meantime I'm unsubscribing Ubuntu Sponsors, please consider all
the above.  Thanks!

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

Title:
  PXE Boot contains wrong suggested link to ISO for live file system

Status in casper package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in casper source package in Jammy:
  Triaged
Status in linux source package in Jammy:
  Invalid

Bug description:
  When PXE booting without pulling in squashfs correctly the system
  tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release
  contains a link to the old version which is not present anymore.

  ---
  Unable to find a medium containing a live file system
  Attempt interactive netboot from a URL?
  yes no (default yes): 
  Two methods available for IP configuration:
* static: for static IP configuration
* dhcp: for automatic IP configuration
  static dhcp (default 'dhcp'): 
  vlan id (optional): 
   https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso 
(default)
   https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso
  url: 
  http_proxy (optional): 
  [  125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: RX/TX
  [  125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
  Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount 
https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ... 

  BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs) Connecting to releases.ubuntu.com (185.125.190.37:443)
  wget: server returned error: HTTP/1.1 404 Not Found
  done.
  Unable to find a medium containing a live file system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1990621/+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 2017328] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r

[Dan Bowkley]

Same issue for me, I think.

** Attachment added: "make.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017328/+attachment/5666968/+files/make.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/2017328

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While upgrading to ubuntu 23.04
  System status reported as "possibly unstable"
  not good

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sat Apr 22 06:39:48 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37+italia-whl+X37.1+italia-+X37.2
  ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2019-09-23 (1306 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic 
root=UUID=19d37003-0d66-4336-ba14-e62e0854596d 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.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-04-22 (0 days ago)
  dmi.bios.date: 12/08/2021
  dmi.bios.release: 1.17
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.17.0
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.0:bd12/08/2021:br1.17:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:sku08AF:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017328/+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 1973098] Re: [i915] Intermittent freezing and LSPCON init failed kernel messages

[Dan]

Same issue here (very similar to above)

System-manufacturer : LENOVO
System-product-name : 20SUS51107
System-version : ThinkPad T15g Gen 1
Bios-release-date : 12/14/2022
Bios-version : N30ET49W (1.32)

5.19.0-38-generic #39~22.04.1-Ubuntu

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

Title:
  [i915] Intermittent freezing and LSPCON init failed kernel messages

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-oem-5.14 package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Lenovo ThinkPad model 20ST0055AU

  Boot messages show:
  [6.397804] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
  [6.397901] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on 
minor 0

  During normal operation there will intermittently be a freeze for a
  second or two and then more of these messages display in the kernel
  logs:

  [  505.487006] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
  [  505.487072] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D
  [  506.747930] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
  [  506.748018] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D

  The system will then become operational again.

  The system is still usable, but it is annoying.

  I've switched onto this OEM kernel from the generic kernel (5.13), as
  I had other problems with 5.13 regarding external displays not coming
  back after idle timeouts.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.14.0-1036-oem 5.14.0-1036.40
  ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21
  Uname: Linux 5.14.0-1036-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 12 10:29:31 2022
  InstallationDate: Installed on 2021-05-05 (371 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-oem-5.14
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973098/+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 1998103]

[dan]

I can confirm similar same results as Toni A. with a Qualcomm Atheros
QCA6390 (Dell XPS 15 9500)on Kernels 6.2.7-arch1-1 and 6.1.20-1-lts.

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

Title:
  Intel 8087:07dc Bluetooth highly unreliable

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

Bug description:
  I've been experiencing all sorts of strange behaviour since upgrading
  to linux mint 21.

  * adapter failing to power on after suspend/resume
  * random errors littering dmesg
  * now it went ballistic and caused my UI to freeze, not from anything I could 
identify that I did.

  inxi -EbA

  System:
    Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
  Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
  Machine:
    Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
  serial: 
    Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: 
  UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015
  CPU:
    Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292
  min/max: 800/3500
  Audio:
    Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
  driver: snd_hda_intel
    Device-2: Intel 8 Series/C220 Series High Definition Audio
  driver: snd_hda_intel
    Sound Server-1: ALSA v: k5.15.0-53-generic running: yes
    Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Bluetooth:
    Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
    Report: hciconfig ID: hci0 rfk-id: 0 state: down
  bt-service: enabled,running rfk-block: hardware: no software: yes
  address: 30:3A:64:EA:9C:EA

  attached kernel logs

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1998103/+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 2008142] Re: bcmwl driver not installed

[Dan Bungert]

Marking wontfix for Lunar, as I don't believe there is action Subiquity
can take yet.  With future MOK key enrollment we can tacke this, but the
above "ubuntu-drivers install" item needs to be resolved first.

** Changed in: subiquity (Ubuntu Lunar)
   Status: New => Won't Fix

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

Title:
  bcmwl driver not installed

Status in ubuntu-desktop-installer:
  New
Status in broadcom-sta package in Ubuntu:
  New
Status in subiquity package in Ubuntu:
  New
Status in broadcom-sta source package in Lunar:
  New
Status in subiquity source package in Lunar:
  Won't Fix

Bug description:
  I was testing an installation in qemu and shared a broadcom wireless
  device with the virtual machine and the drivers for it were not
  installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-desktop-installer (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.24.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 22 16:23:38 2023
  InstallationDate: Installed on 2023-02-23 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230221)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-desktop-installer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2008142/+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 2009815] Re: No HDMI audio anymore

[Dan Cooper]

Some forums report that the boot option pcie_port_pm=off might help.

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

Title:
  No HDMI audio anymore

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 22.10
  Release:  22.10

  Wayland

  5.19.0-35-generic does not work
  5.19.0-32-generic does work

  If following messages occures during boot, no HDMI audio :
  hdaudio hdaudioC1D0: no AFG or MFG node found
  snd_hda_intel :01:00.1: no codecs initialized

  No HDMI Audio does mean : 
  Via lspci -nnk I get the following device :

  01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Baffin 
HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] [1002:aae0]
Subsystem: ASUSTeK Computer Inc. Baffin HDMI/DP Audio [Radeon RX 550 
640SP / RX 560/560X] [1043:aae0]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  But this device will neither be indicated via pavucontrol nor via
  audio settings (mainsettings).

  Before I did installed the Ubuntu 22.10 on my system, I did test the
  live system. It did work without problems. And two audio devices, that
  is what I expect, will be indicated in the audio settings (one of
  them, the given above via lspci -nnk, is necessary to have audio via
  HDMI)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-35-generic 5.19.0-35.36
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  richard1402 F wireplumber
   /dev/snd/seq:richard1399 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  9 10:11:41 2023
  InstallationDate: Installed on 2023-03-04 (4 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=df59b1c2-c5b9-483d-b033-7c6b2264dc75 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-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4802
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev x.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4802:bd09/18/2013:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MPRO:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009815/+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 2008142] Re: bcmwl driver not installed

[Dan Bungert]

Sure, this is the scenario that we were considering for handling of MOK
key enrollment, which isn't implemented yet.

I think something else may be going on though.  With the 22.04.2 desktop
ISO, I can go to a command line and "sudo ubuntu-drivers install", and
when it's done I have a wireless interface.  I cannot do the same with
lunar desktop dailies, instead I get the "All the available drivers are
already installed" comment.  "mokutil --sb-state" reports "This system
doesn't support Secure Boot".

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

Title:
  bcmwl driver not installed

Status in ubuntu-desktop-installer:
  New
Status in broadcom-sta package in Ubuntu:
  New
Status in subiquity package in Ubuntu:
  New
Status in broadcom-sta source package in Lunar:
  New
Status in subiquity source package in Lunar:
  New

Bug description:
  I was testing an installation in qemu and shared a broadcom wireless
  device with the virtual machine and the drivers for it were not
  installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-desktop-installer (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.24.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 22 16:23:38 2023
  InstallationDate: Installed on 2023-02-23 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230221)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-desktop-installer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2008142/+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 2008142] Re: bcmwl driver not installed

[Dan Bungert]

broadcom-sta-dkms can be found on the ISO pool on both lunar-desktop and
lunar-desktop-legacy.  In the live session, "ubuntu-drivers install"
reports that "All the available drivers are already installed", but
broadcom-sta-dkms isn't installed.  "ubuntu-drivers debug" reports
broadcom-sta-dkms as needed.

manual installation of broadcom-sta-dkms does complete but the system
still has no wireless interface and dmesg reports that 'wl: module
verification failed: signature and/or required key missing - tainting
kernel'.  The reconfigure/kmodsign/modprobe workaround in
https://discourse.ubuntu.com/t/dkms-package-support-extra-drivers-does-
not-work-in-ubuntu-22-10-install-media/31655 does result in a loadable
driver but not a wireless interface.

Am I missing something?

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

Title:
  bcmwl driver not installed

Status in ubuntu-desktop-installer:
  New
Status in broadcom-sta package in Ubuntu:
  New
Status in subiquity package in Ubuntu:
  New
Status in broadcom-sta source package in Lunar:
  New
Status in subiquity source package in Lunar:
  New

Bug description:
  I was testing an installation in qemu and shared a broadcom wireless
  device with the virtual machine and the drivers for it were not
  installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-desktop-installer (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.24.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 22 16:23:38 2023
  InstallationDate: Installed on 2023-02-23 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230221)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-desktop-installer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2008142/+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 2008142] Re: bcmwl driver not installed

[Dan Bungert]

** Also affects: broadcom-sta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  bcmwl driver not installed

Status in ubuntu-desktop-installer:
  New
Status in broadcom-sta package in Ubuntu:
  New
Status in subiquity package in Ubuntu:
  New
Status in broadcom-sta source package in Lunar:
  New
Status in subiquity source package in Lunar:
  New

Bug description:
  I was testing an installation in qemu and shared a broadcom wireless
  device with the virtual machine and the drivers for it were not
  installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-desktop-installer (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.24.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 22 16:23:38 2023
  InstallationDate: Installed on 2023-02-23 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230221)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-desktop-installer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2008142/+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 2007030] [NEW] evolve III touchpad stopped working after update

[Dan McMahill]

Public bug reported:

The system notified me there were package updates available, I accepted
the updates and then the touchpad stopped working.  Presumably something
in the LTS kernel changed just recently.  After a reboot the touchpad
may sort of work erratically on the login screen but then completely
stops after.  The system info collected by the bug tool will show a usb
mouse plugged in.  I only did that to be able to use the laptop enough
to file the report.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-60-generic 5.15.0-60.66
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Sun Feb 12 11:49:44 2023
InstallationDate: Installed on 2022-08-10 (185 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
MachineType: OEM Default string000 OEM Default string000
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-60-generic N/A
 linux-backports-modules-5.15.0-60-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/23/2021
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E3-BI-11.6-Y116ARX320-006-F
dmi.board.asset.tag: OEM Default string000
dmi.board.name: OEM Default string000
dmi.board.vendor: OEM Default string000
dmi.board.version: OEM Default string000
dmi.chassis.asset.tag: OEM Default string000
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Default string000
dmi.chassis.version: OEM Default string000
dmi.ec.firmware.release: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE3-BI-11.6-Y116ARX320-006-F:bd01/23/2021:br5.12:efr1.0:svnOEMDefaultstring000:pnOEMDefaultstring000:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
dmi.product.family: OEM Default string000
dmi.product.name: OEM Default string000
dmi.product.sku: OEM Default string000
dmi.product.version: OEM Default string000
dmi.sys.vendor: OEM Default string000

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


** Tags: amd64 apport-bug jammy

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

Title:
  evolve III touchpad stopped working after update

Status in linux package in Ubuntu:
  New

Bug description:
  The system notified me there were package updates available, I
  accepted the updates and then the touchpad stopped working.
  Presumably something in the LTS kernel changed just recently.  After a
  reboot the touchpad may sort of work erratically on the login screen
  but then completely stops after.  The system info collected by the bug
  tool will show a usb mouse plugged in.  I only did that to be able to
  use the laptop enough to file the report.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-60-generic 5.15.0-60.66
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Sun Feb 12 11:49:44 2023
  InstallationDate: Installed on 2022-08-10 (185 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: OEM Default string000 OEM Default string000
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-60-generic N/A
   linux-backports-modules-5.15.0-60-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2021
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E3-BI-11.6-Y116ARX320-006-F
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM 

[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 1999930] [NEW] UBSAN: invalid-load in /build/linux-MUxl3y/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:488:16

[Dan Cooper]

Public bug reported:

Hello,
I get the following messages in dmesg:

user@dc7100:~$ sudo dmesg |grep ath
[   41.044737] ath5k :05:09.0: registered as 'phy0'
[   41.685132] ath: EEPROM regdomain: 0x809c
[   41.685142] ath: EEPROM indicates we should expect a country code
[   41.685144] ath: doing EEPROM country->regdmn map search
[   41.685147] ath: country maps to regdmn code: 0x52
[   41.685150] ath: Country alpha2 being used: CN
[   41.685153] ath: Regpair used: 0x52
[   41.692867] ath5k: phy0: Atheros AR2414 chip found (MAC: 0x79, PHY: 0x45)
[   41.703932] ath5k :05:09.0 wlp5s9: renamed from wlan0
[   60.184098] UBSAN: invalid-load in 
/build/linux-MUxl3y/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:497:16
[   60.184270]  ath5k_vif_iter.cold+0x67/0x70 [ath5k]
[   60.184286]  ath5k_update_bssid_mask_and_opmode+0x63/0x150 [ath5k]
[   60.184298]  ath5k_add_interface+0x1bb/0x260 [ath5k]
[   60.190081] UBSAN: invalid-load in 
/build/linux-MUxl3y/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:488:16
[   60.190515]  ath5k_vif_iter.cold+0x13/0x70 [ath5k]
[   60.190649]  ? ath5k_tasklet_ani+0x40/0x40 [ath5k]
[   60.190773]  ath5k_configure_filter+0x114/0x190 [ath5k]
[   65.580713] UBSAN: array-index-out-of-bounds in 
/build/linux-MUxl3y/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20
[   65.580996]  ath5k_tx_frame_completed.constprop.0+0x27d/0x2d0 [ath5k]
[   65.581018]  ath5k_tx_processq+0xb1/0x1c0 [ath5k]
[   65.581037]  ath5k_tasklet_tx+0x7b/0xf0 [ath5k]
[  441.942613] ath5k: ath5k_hw_get_isr: ISR: 0x0400 IMR: 0x
user@dc7100:~$ 

I have a wireless NIC Ethernet controller [0200]: Qualcomm Atheros
AR5212/5213/2414 Wireless Network Adapter [168c:0013] (rev 01) that
seems to work find.

kind regards
Dan Cooper

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
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  djkuhpisse741 F pulseaudio
CasperMD5CheckResult: unknown
Date: Fri Dec 16 19:15:24 2022
HibernationDevice: RESUME=UUID=387643d1-541a-42fb-bc20-1aca96522efd
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Hewlett-Packard HP Compaq dc7100 CMT(DX438AV)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgdc7100-root ro
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.7
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2021-04-24 (601 days ago)
dmi.bios.date: 08/07/2008
dmi.bios.release: 2.15
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786C1 v02.15
dmi.board.name: 0968h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786C1v02.15:bd08/07/2008:br2.15:svnHewlett-Packard:pnHPCompaqdc7100CMT(DX438AV):pvr:rvnHewlett-Packard:rn0968h:rvr:cvnHewlett-Packard:ct6:cvr:sku:
dmi.product.name: HP Compaq dc7100 CMT(DX438AV)
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug ath5k jammy

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

Title:
  UBSAN: invalid-load in /build/linux-
  MUxl3y/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:488:16

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,
  I get the following messages in dmesg:

  user@dc7100:~$ sudo dmesg |grep ath
  [   41.044737] ath5k :05:09.0: registered as 'phy0'
  [   41.685132] ath: EEPROM regdomain: 0x809c
  [   41.685142] ath: EEPROM indicates we should expect a country code
  [   41.685144] ath: doing EEPROM country->regdmn map search
  [   41.685147] ath: country maps to regdmn code: 0x52
  [   41.685150] ath: Country alpha2 being used: CN
  [   41.685153] ath: Regpair used: 0x52
  [   41.692867] ath5k: phy0: Atheros AR2414 chip found (MAC: 0x79, PHY: 0x45)
  [   41.703932] ath5k :05:09.0 wlp5s9: renamed from wlan0
  [   60.184098] UBSAN: invalid-load in 
/build/linux-MUxl3y/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:497:16
  [   60.184270]  ath5k_vif_iter.cold+0x67/0x70 [ath5k]
  [   60.184286]  ath5k_update_bssid_mask_and_opmode+0x63/0x150 [ath5k]
  [   60.184298]  ath5k_add_interface+0x1bb/0x260 [ath5k]
  [   60.190081] UBSAN: invalid-load in 
/build/linux-MUxl3y/linux-

[Kernel-packages] [Bug 1998168] Re: System went crash during Ubuntu 20.04.5 installation

[Dan Bungert]

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

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

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

Title:
  System went crash during Ubuntu 20.04.5 installation

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

Bug description:
  Configuration:
   OS:ubuntu-20.04.5-live-server-amd64.iso
   CPU:INTEL(R)XEON(R)PLATINUM8470QSAPPHIRERAPIDSE3105MB52cFC-LGA350WQ16Q 
EV-QS*2
   SSD:Intel S4620 2.5'1.92T Mainstream SATA 6Gb Hot Swap SSD* 2
   Boot mode:UEFI
  Reproduce Steps:
   Install ubuntu 22.04 on disk
  Current behaviors:
   System will crash during installation

  2022-09-28 22:18:59,807 INFO subiquitycore.common.errorreport:406 saving 
crash report 'install failed crashed with CalledProcessError' to 
/var/crash/1664403539.805207491.install_fail.crash
  2022-09-28 22:18:59,807 ERROR root:39 finish: subiquity/Install/install: 
FAIL: Command '['systemd-run', '--wait', '--same-dir', '--property', 
'SyslogIdentifier=subiquity_log.5855', '--property', 'PrivateMounts=yes', 
'--setenv', 
'PATH=/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/bin',
 '--setenv', 
'PYTHONPATH=:/snap/subiquity/3698/lib/python3.8/site-packages:/snap/subiquity/3698/lib/python3.8/site-packages',
 '--setenv', 'PYTHON=/snap/subiquity/3698/usr/bin/python3.8', '--setenv', 
'SNAP=/snap/subiquity/3698', '--', '/snap/subiquity/3698/usr/bin/python3.8', 
'-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity": 
{"type": "journald", "identifier": "curtin_event.5855.2"}}', 'in-target', '-t', 
'/tmp/tmpq8qjbbe5/mount', '--', 'apt-get', 'update']' returned non-zer
 o exit status 100.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1998168/+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 1993818] Re: Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10

[Dan Meyers]

Still no crashes/freezes after almost day of usage, so I think we're
good in that respect.

I also resolved the distortion issue I was having by adding the
"i915.enable_psr=0" kernel option. I was detecting some slight lag w/
the mouse periodically and found that as a potential solution -- it
seems to fix both the lag AND the distortion!

Anyhow, at the moment my system feels much like the sturdy/stable system
I had with 22.04. Thanks again for the help!

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

Title:
  Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Been experiencing random hangs since upgraded to 22.10.

  Looking at /var/log/kern.log after crash I'm seeing general protection
  fault from /var/log/kern.log.

  Oct 21 20:41:38 tyrant kernel: [  281.051619] general protection fault, 
probably for non-canonical address 0x258d1b207028:  [#1] PREEMPT SMP 
NOPTI
  Oct 21 20:41:38 tyrant kernel: [  281.051629] CPU: 13 PID: 2445 Comm: 
gnome-shell Tainted: GW 5.19.0-21-generic #21-Ubuntu
  Oct 21 20:41:38 tyrant kernel: [  281.051633] Hardware name: LENOVO 
21CBCTO1WW/21CBCTO1WW, BIOS N3AET67W (1.32 ) 09/27/2022
  Oct 21 20:41:38 tyrant kernel: [  281.051636] RIP: 0010:rm_hole+0x1a7/0x340 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.051676] Code: 8b 78 08 eb 1c 48 89 50 
28 48 8b 10 48 89 d0 48 83 e0 fc 48 83 fa 03 76 32 48 8b 48 10 48 8b 78 08 48 
8b 50 20 48 85 c9 74 0b <48> 8b 49 28 48 39 ca 48 0f 42 d1 48 85 ff 74 0b 48 8b 
4f 28 48 39
  Oct 21 20:41:38 tyrant kernel: [  281.051679] RSP: 0018:ac26834ab9c0 
EFLAGS: 00010206
  Oct 21 20:41:38 tyrant kernel: [  281.051683] RAX: 90258161d1b0 RBX: 
902580fd7800 RCX: 258d1b207000
  Oct 21 20:41:38 tyrant kernel: [  281.051686] RDX: 0003ccf0 RSI: 
9025a4351528 RDI: 0090
  Oct 21 20:41:38 tyrant kernel: [  281.051688] RBP: ac26834ab9e0 R08: 
 R09: 
  Oct 21 20:41:38 tyrant kernel: [  281.051690] R10: 902580fd7870 R11: 
902581747740 R12: 902580fd7858
  Oct 21 20:41:38 tyrant kernel: [  281.051692] R13: 9025a4351528 R14: 
9025a43515f8 R15: 0011
  Oct 21 20:41:38 tyrant kernel: [  281.051694] FS:  7f553c5d45c0() 
GS:902cbf74() knlGS:
  Oct 21 20:41:38 tyrant kernel: [  281.051697] CS:  0010 DS:  ES:  
CR0: 80050033
  Oct 21 20:41:38 tyrant kernel: [  281.051700] CR2: 7f35e73685c0 CR3: 
00013119a001 CR4: 00770ee0
  Oct 21 20:41:38 tyrant kernel: [  281.051702] PKRU: 5554
  Oct 21 20:41:38 tyrant kernel: [  281.051704] Call Trace:
  Oct 21 20:41:38 tyrant kernel: [  281.051707]  
  Oct 21 20:41:38 tyrant kernel: [  281.051711]  
drm_mm_insert_node_in_range+0x26a/0x500 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.051745]  
_i915_gem_object_stolen_init+0x28c/0x2e0 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.051871]  
__i915_gem_object_create_region+0xb2/0x170 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.051977]  
i915_gem_object_create_region+0x1e/0x30 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052080]  
i915_gem_object_create_stolen+0x19/0x30 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052184]  intel_dpt_create+0x20b/0x2c0 
[i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052299]  
intel_framebuffer_init+0x749/0x960 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052408]  ? 
kmem_cache_alloc_trace+0x189/0x310
  Oct 21 20:41:38 tyrant kernel: [  281.052414]  
intel_framebuffer_create+0x40/0x90 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052521]  
intel_user_framebuffer_create+0xf8/0x1d0 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052626]  
drm_internal_framebuffer_create+0xb3/0x150 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052667]  drm_mode_addfb2+0x44/0xd0 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052705]  ? 
drm_mode_addfb_ioctl+0x20/0x20 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052743]  drm_mode_addfb2_ioctl+0xe/0x20 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052780]  drm_ioctl_kernel+0xd3/0x180 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052811]  drm_ioctl+0x29d/0x4d0 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052840]  ? 
drm_mode_addfb_ioctl+0x20/0x20 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052879]  __x64_sys_ioctl+0x9d/0xe0
  Oct 21 20:41:38 tyrant kernel: [  281.052884]  do_syscall_64+0x58/0x90
  Oct 21 20:41:38 tyrant kernel: [  281.052888]  ? __do_sys_kcmp+0x208/0x550
  Oct 21 20:41:38 tyrant kernel: [  281.052894]  ? 
exit_to_user_mode_prepare+0x30/0xb0
  Oct 21 20:41:38 tyrant kernel: [  281.052899]  ? 
syscall_exit_to_user_mode+0x26/0x50
  Oct 21 20:41:38 tyrant kernel: [  281.052902]  ? __x64_sys_kcmp+0x1f/0x30
  Oct 21 20:41:38 tyrant kernel: [  281.052905]  ? do_syscall_64+0x67/0x90
  Oct 21 20:41:38 

[Kernel-packages] [Bug 1905261] Re: Openssl ignores order from /etc/nsswitch.conf

[Dan Bungert]

While my strace output looks similar, it may be still working as
intended.  I added a hosts entry for ubuntu.com pointing to a different
server, and received output indicating that I connected to the other
server.  Perhaps that has been fixed since the bug was filed?
Alternately, would you update with more steps to reproduce?

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

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

Title:
  Openssl ignores order from /etc/nsswitch.conf

Status in linux-meta package in Ubuntu:
  Incomplete
Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  
  I'm issuing command like below:
  openssl s_client -connect subdomain.domain.example.com

  I have following nsswitch.confg defined:
  '''
  $ cat /etc/nsswitch.conf 
  # /etc/nsswitch.conf
  #
  # Example configuration of GNU Name Service Switch functionality.
  # If you have the `glibc-doc-reference' and `info' packages installed, try:
  # `info libc "Name Service Switch"' for information about this file.

  passwd: compat systemd
  group:  compat systemd
  shadow: compat

  hosts:  files mdns4_minimal [NOTFOUND=return] resolve 
[!UNAVAIL=return] dns myhostname
  networks:   files

  protocols:  db files
  services:   db files
  ethers: db files
  rpc:db files

  netgroup:   nis
  '''

  
  For host resolution /etc/hosts file should take precedence. But it doesn't 
work that way and when I have some unresolvable name it tries to connect to DNS 
ignoring local hosts file. The order can be clearly visible in strace:

  
  '''openat(AT_FDCWD, "/usr/lib/ssl/ct_log_list.cnf", O_RDONLY) = -1 ENOENT (No 
such file or directory)
  openat(AT_FDCWD, "/usr/lib/ssl/cert.pem", O_RDONLY) = -1 ENOENT (No such file 
or directory)
  socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
  connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 
ENOENT (No such file or directory)
  close(5)= 0
  socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
  connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 
ENOENT (No such file or directory)
  close(5)= 0
  openat(AT_FDCWD, "/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=560, ...}) = 0
  read(5, "# /etc/nsswitch.conf\n#\n# Example"..., 4096) = 560
  read(5, "", 4096)   = 0
  close(5)= 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=64, ...}) = 0
  openat(AT_FDCWD, "/etc/host.conf", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=93, ...}) = 0
  read(5, "# The \"order\" line is only used "..., 4096) = 93
  read(5, "", 4096)   = 0
  close(5)= 0
  futex(0x7f3d2d2b5ba4, FUTEX_WAKE_PRIVATE, 2147483647) = 0
  openat(AT_FDCWD, "/etc/resolv.conf", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=64, ...}) = 0
  read(5, "# Generated by NetworkManager\nse"..., 4096) = 64
  read(5, "", 4096)   = 0
  close(5)= 0
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=335124, ...}) = 0
  mmap(NULL, 335124, PROT_READ, MAP_PRIVATE, 5, 0) = 0x7f3d2de05000
  close(5)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libnss_files.so.2", 
O_RDONLY|O_CLOEXEC) = 5
  read(5, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P#\0\0\0\0\0\0"..., 
832) = 832
  fstat(5, {st_mode=S_IFREG|0644, st_size=47568, ...}) = 0
  mmap(NULL, 2168632, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 5, 0) = 
0x7f3d2cab
  mprotect(0x7f3d2cabb000, 2093056, PROT_NONE) = 0
  mmap(0x7f3d2ccba000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0xa000) = 0x7f3d2ccba000
  mmap(0x7f3d2ccbc000, 22328, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3d2ccbc000
  close(5)= 0
  mprotect(0x7f3d2ccba000, 4096, PROT_READ) = 0
  munmap(0x7f3d2de05000, 335124)  = 0
  openat(AT_FDCWD, "/etc/hosts", O_RDONLY|O_CLOEXEC) = 5
  '''

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssl 1.1.1-1ubuntu2.1~18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18
  Uname: Linux 4.15.0-124-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.20
  Architecture: amd64
  Date: Mon Nov 23 10:49:41 2020
  InstallationDate: Installed on 2015-05-08 (2026 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
 

[Kernel-packages] [Bug 1905261] Re: Openssl ignores order from /etc/nsswitch.conf

[Dan Bungert]

Looks like the linux-meta task was added recently, was that intended?
I'm not certain that this would be a kernel bug.   Marking that part
incomplete - additional info would help.

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

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

Title:
  Openssl ignores order from /etc/nsswitch.conf

Status in linux-meta package in Ubuntu:
  Incomplete
Status in openssl package in Ubuntu:
  New

Bug description:
  
  I'm issuing command like below:
  openssl s_client -connect subdomain.domain.example.com

  I have following nsswitch.confg defined:
  '''
  $ cat /etc/nsswitch.conf 
  # /etc/nsswitch.conf
  #
  # Example configuration of GNU Name Service Switch functionality.
  # If you have the `glibc-doc-reference' and `info' packages installed, try:
  # `info libc "Name Service Switch"' for information about this file.

  passwd: compat systemd
  group:  compat systemd
  shadow: compat

  hosts:  files mdns4_minimal [NOTFOUND=return] resolve 
[!UNAVAIL=return] dns myhostname
  networks:   files

  protocols:  db files
  services:   db files
  ethers: db files
  rpc:db files

  netgroup:   nis
  '''

  
  For host resolution /etc/hosts file should take precedence. But it doesn't 
work that way and when I have some unresolvable name it tries to connect to DNS 
ignoring local hosts file. The order can be clearly visible in strace:

  
  '''openat(AT_FDCWD, "/usr/lib/ssl/ct_log_list.cnf", O_RDONLY) = -1 ENOENT (No 
such file or directory)
  openat(AT_FDCWD, "/usr/lib/ssl/cert.pem", O_RDONLY) = -1 ENOENT (No such file 
or directory)
  socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
  connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 
ENOENT (No such file or directory)
  close(5)= 0
  socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
  connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 
ENOENT (No such file or directory)
  close(5)= 0
  openat(AT_FDCWD, "/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=560, ...}) = 0
  read(5, "# /etc/nsswitch.conf\n#\n# Example"..., 4096) = 560
  read(5, "", 4096)   = 0
  close(5)= 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=64, ...}) = 0
  openat(AT_FDCWD, "/etc/host.conf", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=93, ...}) = 0
  read(5, "# The \"order\" line is only used "..., 4096) = 93
  read(5, "", 4096)   = 0
  close(5)= 0
  futex(0x7f3d2d2b5ba4, FUTEX_WAKE_PRIVATE, 2147483647) = 0
  openat(AT_FDCWD, "/etc/resolv.conf", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=64, ...}) = 0
  read(5, "# Generated by NetworkManager\nse"..., 4096) = 64
  read(5, "", 4096)   = 0
  close(5)= 0
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=335124, ...}) = 0
  mmap(NULL, 335124, PROT_READ, MAP_PRIVATE, 5, 0) = 0x7f3d2de05000
  close(5)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libnss_files.so.2", 
O_RDONLY|O_CLOEXEC) = 5
  read(5, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P#\0\0\0\0\0\0"..., 
832) = 832
  fstat(5, {st_mode=S_IFREG|0644, st_size=47568, ...}) = 0
  mmap(NULL, 2168632, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 5, 0) = 
0x7f3d2cab
  mprotect(0x7f3d2cabb000, 2093056, PROT_NONE) = 0
  mmap(0x7f3d2ccba000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0xa000) = 0x7f3d2ccba000
  mmap(0x7f3d2ccbc000, 22328, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3d2ccbc000
  close(5)= 0
  mprotect(0x7f3d2ccba000, 4096, PROT_READ) = 0
  munmap(0x7f3d2de05000, 335124)  = 0
  openat(AT_FDCWD, "/etc/hosts", O_RDONLY|O_CLOEXEC) = 5
  '''

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssl 1.1.1-1ubuntu2.1~18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18
  Uname: Linux 4.15.0-124-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.20
  Architecture: amd64
  Date: Mon Nov 23 10:49:41 2020
  InstallationDate: Installed on 2015-05-08 (2026 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssl
  UpgradeStatus: Upgraded to bionic on 2018-08-26 (819 days ago)

To manage 

[Kernel-packages] [Bug 1993818] Re: Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10

[Dan Meyers]

Hi Andrea, I was seeing the problem quite frequently (maybe every 5-10
minutes), although I haven't seen it in the past 30 minutes, since I've
updated to your kernel.

And since this is related to i915, I'm also going to mention that I see
some visual distortions on the screen when I move my mouse across a
specific area of the screen. The distortions are multi-colored
horizontal lines that stretch all the way across the display. This issue
also existed prior to installing your test kernel. Anyhow, just thought
I'd mention it in case it could be somehow related to something that
went missing along the way (22.04 works beautifully for me).

Thanks for the quick fix on the stability issues!

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

Title:
  Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Been experiencing random hangs since upgraded to 22.10.

  Looking at /var/log/kern.log after crash I'm seeing general protection
  fault from /var/log/kern.log.

  Oct 21 20:41:38 tyrant kernel: [  281.051619] general protection fault, 
probably for non-canonical address 0x258d1b207028:  [#1] PREEMPT SMP 
NOPTI
  Oct 21 20:41:38 tyrant kernel: [  281.051629] CPU: 13 PID: 2445 Comm: 
gnome-shell Tainted: GW 5.19.0-21-generic #21-Ubuntu
  Oct 21 20:41:38 tyrant kernel: [  281.051633] Hardware name: LENOVO 
21CBCTO1WW/21CBCTO1WW, BIOS N3AET67W (1.32 ) 09/27/2022
  Oct 21 20:41:38 tyrant kernel: [  281.051636] RIP: 0010:rm_hole+0x1a7/0x340 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.051676] Code: 8b 78 08 eb 1c 48 89 50 
28 48 8b 10 48 89 d0 48 83 e0 fc 48 83 fa 03 76 32 48 8b 48 10 48 8b 78 08 48 
8b 50 20 48 85 c9 74 0b <48> 8b 49 28 48 39 ca 48 0f 42 d1 48 85 ff 74 0b 48 8b 
4f 28 48 39
  Oct 21 20:41:38 tyrant kernel: [  281.051679] RSP: 0018:ac26834ab9c0 
EFLAGS: 00010206
  Oct 21 20:41:38 tyrant kernel: [  281.051683] RAX: 90258161d1b0 RBX: 
902580fd7800 RCX: 258d1b207000
  Oct 21 20:41:38 tyrant kernel: [  281.051686] RDX: 0003ccf0 RSI: 
9025a4351528 RDI: 0090
  Oct 21 20:41:38 tyrant kernel: [  281.051688] RBP: ac26834ab9e0 R08: 
 R09: 
  Oct 21 20:41:38 tyrant kernel: [  281.051690] R10: 902580fd7870 R11: 
902581747740 R12: 902580fd7858
  Oct 21 20:41:38 tyrant kernel: [  281.051692] R13: 9025a4351528 R14: 
9025a43515f8 R15: 0011
  Oct 21 20:41:38 tyrant kernel: [  281.051694] FS:  7f553c5d45c0() 
GS:902cbf74() knlGS:
  Oct 21 20:41:38 tyrant kernel: [  281.051697] CS:  0010 DS:  ES:  
CR0: 80050033
  Oct 21 20:41:38 tyrant kernel: [  281.051700] CR2: 7f35e73685c0 CR3: 
00013119a001 CR4: 00770ee0
  Oct 21 20:41:38 tyrant kernel: [  281.051702] PKRU: 5554
  Oct 21 20:41:38 tyrant kernel: [  281.051704] Call Trace:
  Oct 21 20:41:38 tyrant kernel: [  281.051707]  
  Oct 21 20:41:38 tyrant kernel: [  281.051711]  
drm_mm_insert_node_in_range+0x26a/0x500 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.051745]  
_i915_gem_object_stolen_init+0x28c/0x2e0 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.051871]  
__i915_gem_object_create_region+0xb2/0x170 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.051977]  
i915_gem_object_create_region+0x1e/0x30 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052080]  
i915_gem_object_create_stolen+0x19/0x30 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052184]  intel_dpt_create+0x20b/0x2c0 
[i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052299]  
intel_framebuffer_init+0x749/0x960 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052408]  ? 
kmem_cache_alloc_trace+0x189/0x310
  Oct 21 20:41:38 tyrant kernel: [  281.052414]  
intel_framebuffer_create+0x40/0x90 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052521]  
intel_user_framebuffer_create+0xf8/0x1d0 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052626]  
drm_internal_framebuffer_create+0xb3/0x150 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052667]  drm_mode_addfb2+0x44/0xd0 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052705]  ? 
drm_mode_addfb_ioctl+0x20/0x20 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052743]  drm_mode_addfb2_ioctl+0xe/0x20 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052780]  drm_ioctl_kernel+0xd3/0x180 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052811]  drm_ioctl+0x29d/0x4d0 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052840]  ? 
drm_mode_addfb_ioctl+0x20/0x20 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052879]  __x64_sys_ioctl+0x9d/0xe0
  Oct 21 20:41:38 tyrant kernel: [  281.052884]  do_syscall_64+0x58/0x90
  Oct 21 20:41:38 tyrant kernel: [  281.052888]  ? __do_sys_kcmp+0x208/0x550
  Oct 21 20:41:38 tyrant kernel: [  281.052894]  ? 
exit_to_user_mode_prepare+0x30/0xb0
  Oct 21 20:41:38 tyrant 

[Kernel-packages] [Bug 1991676] Re: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.)

[Dan Bungert]

** Tags added: foundations-todo

** Changed in: grub2-signed (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: grub2-signed (Ubuntu Bionic)
   Importance: Undecided => High

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

Title:
  Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from
  bionic-proposed fails to install/upgrade (grub-install: error:
  efibootmgr: not found.)

Status in ubuntu-kernel-tests:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in linux-hwe-5.4 package in Ubuntu:
  New
Status in grub2-signed source package in Bionic:
  Triaged
Status in linux-hwe-5.4 source package in Bionic:
  New

Bug description:
  The ADT tests for arm64 kernels in Bionic are failing during the setup
  phase with the following errors:

  Setting up grub-efi-arm64-signed (1.173.2~18.04.1+2.04-1ubuntu47.4) ...
  Installing for arm64-efi platform.
  grub-install: error: efibootmgr: not found.
  dpkg: error processing package grub-efi-arm64-signed (--configure):
   installed grub-efi-arm64-signed package post-installation script subprocess 
returned error exit status 1
  Setting up libx11-6:arm64 (2:1.6.4-3ubuntu0.5) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1.6) ...
  Errors were encountered while processing:
   grub-efi-arm64-signed
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  blame: 
  badpkg: testbed setup commands failed with status 100
  autopkgtest [15:12:03]: ERROR: erroneous package: testbed setup commands 
failed with status 100

  ADT test log:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/l/linux-hwe-5.4/20220930_151219_13ac3@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1991676/+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 1988966] Re: kiwi: kiwi-dracut-oem-dump/riscv64 has unsatisfiable dependency

[Dan Bungert]

The origin of that patch appears to be:
https://github.com/riscv-collab/kexec-tools/compare/master...riscv

There seems to be some ongoing conversation about that patch:
http://lists.infradead.org/pipermail/kexec/2022-August/025697.html

Given that it's been around for a year and not merged yet and still
under discussion with fundamental-looking changes needed, I though it
best to not apply the patch.

I have elected to remove the risc-v build from kiwi-dracut-oem-dump
until the above is resolved.

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

Title:
  kiwi: kiwi-dracut-oem-dump/riscv64 has unsatisfiable dependency

Status in kexec-tools package in Ubuntu:
  New
Status in kiwi package in Ubuntu:
  New
Status in kexec-tools package in Debian:
  New

Bug description:
  kiwi-dracut-oem-dump has a dependency on kexec-tools which is not
  built for riscv64.

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019254
  contains a patch from openSUSE

  https://build.opensuse.org/package/view_file/openSUSE:Factory:RISCV/kexec-
  tools/riscv.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1988966/+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 1969482] Re: zfs-2.1.4+ sru

[Dan Podeanu]

The updated kernel was released, and it fixes the performance
regression. Thank you!

# uname -a
Linux arpa 5.15.0-43-generic #46-Ubuntu SMP Tue Jul 12 10:30:17 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux

# zfs --version
zfs-2.1.4-0ubuntu0.1
zfs-kmod-2.1.4-0ubuntu0.1

# grep . /sys/module/icp/parameters/*impl*
/sys/module/icp/parameters/icp_aes_impl:cycle [fastest] generic x86_64 aesni 
/sys/module/icp/parameters/icp_gcm_impl:cycle [fastest] avx generic pclmulqdq 

# dd if=14GBfile.tmp of=/dev/null bs=1M
13411+1 records in
13411+1 records out
14062902185 bytes (14 GB, 13 GiB) copied, 12.6139 s, 1.1 GB/s

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

Title:
  zfs-2.1.4+ sru

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Upstream stable point release update with bugfixes, performance
  fixes, and newer kernel support as needed already in the OEM kernel
  and will be needed in the future HWE kernels.

  [Test Plan]

   * autopkgtest pass

   * kernel regression zfs testsuite pass

   * zsys integration test pass

  [Where problems could occur]

   * The stable branches maintain api/abi. Certain bugfixes do change
  userspace visible behavior of either succeeeding (when previously
  operations failed), or return errors when previously succeeding in
  error. For example there are changes when unlinking files in full
  volumes; changes to fallocate behaviour, etc. Overall they are minor
  corner cases, and bugfixes to correct the bahaviour to what is
  universally expected and how things behave on other filesystems (i.e.
  ext4).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969482/+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 1977699] Re: zfs icp has deselected all optimized aes & gcm impls

[Dan Podeanu]

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

** This bug has been marked a duplicate of bug 1969482
   zfs-2.1.4+ sru

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

Title:
  zfs icp has deselected all optimized aes & gcm impls

Status in linux package in Ubuntu:
  Incomplete
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  In an upgrade from Jammy kernel 5.15.0-27-generic to 5.15.0-35-generic
  on x86_64 (AMD threadripper pro 39x5wx series), a 40x performance
  regression in the first read of cached writes to an encrypted dataset
  revealed that zfs is no longer configured to choose any
  implementations from advanced instruction sets:

  $ grep . /sys/module/icp/parameters/*impl*
  /sys/module/icp/parameters/icp_aes_impl:cycle [fastest] generic x86_64
  /sys/module/icp/parameters/icp_gcm_impl:cycle [fastest] generic

  With correct configuration, the output should read as follows:

  $ grep . /sys/module/icp/parameters/*impl*
  /sys/module/icp/parameters/icp_aes_impl:cycle [fastest] generic x86_64 aesni
  /sys/module/icp/parameters/icp_gcm_impl:cycle [fastest] avx generic pclmulqdq

  The immediate ill effects are the use of gcm_generic_mul instead of
  the dedicated instruction, consuming 50% CPU and slowing reads of data
  cached in ram to less than 20% of what they would be even reading
  directly from disk.

  openzfs changed its configure process to detect cpu features
  differently recently to adapt to the kernel api change. It seems that
  the upstream changes that unexport the needed symbols and the
  downstream changes in openzfs that stop using them were not
  cherrypicked in sync.

  https://github.com/openzfs/zfs/pull/13147
  https://github.com/openzfs/zfs/pull/13236

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977699/+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 1978347] Re: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27

[Dan Podeanu]

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

** This bug is no longer a duplicate of bug 1977699
   zfs icp has deselected all optimized aes & gcm impls
** This bug has been marked a duplicate of bug 1969482
   zfs-2.1.4+ sru

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

Title:
  horrible IO degradation with encrypted zfs root on kernels past
  5.15.0-27

Status in linux package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  IO on encrypted zfs root has fallen off a cliff in kernel versions
  after 5.15.0-27 (the degradation is observed since version 5.15.0-30,
  also seen on -33 and -37, -25 and -27 work like a charm). Heavy usage
  almost hangs a new laptop (building large singularity images or
  synthetic testing with dd).

  I have confirmed that things are working as expected on a default +
  upgraded Ubuntu 22.04 desktop LVM+LUKS installation using another NVMe
  SSD on the same laptop. There seems to be a regression when using the
  native zfs encryption (did aes-ni acceleration get turned off?)

  How to reproduce:

  - install ubuntu 22.04 desktop from iso, don't install web updates, check use 
zfs and encryption
  - sudo apt update && apt install dstat htop
  - create a dataset with compression disabled so that dd actually writes 
things to disk

  * sudo zfs create rpool/dummy
  * sudo zfs set compress=off rpool/dummy
  * sudo chown -R myusername. /dummy

  - start dstat and htop in the background (show kernel threads in the htop 
config)
  - dd if=/dev/zero of=/dummy/bigfile bs=1M count=16384

  - sudo apt upgradeand reboot on the latest kernel, repeat

  Expected: some cpu load, dstat reports write speeds about as much as
  the SSD can sustain (2.9-3GiB/s with a 2TiB Samsung 970 EVO Plus for a
  16GiB write test, 1.4GiB/s for a few seconds then 800MiB/s sustained
  for whatever WD 512GiB model I had laying around).

  Observed on versions -30 and later: 700% or more system cpu load,
  mostly in z_wr_iss threads, writes top at around 150-180MiB/s, the
  system becomes somewhat unresponsive. Reads are also not good but I
  have not benchmarked. Booting the system and launching apps seems
  about normal due to the low IO load.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-37-generic 5.15.0-37.39
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laperlej   4100 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 10 15:52:12 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2022-05-10 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: HP HP EliteBook 850 G8 Notebook PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rgwvzq@/vmlinuz-5.15.0-37-generic 
root=ZFS=rpool/ROOT/ubuntu_rgwvzq ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-37-generic N/A
   linux-backports-modules-5.15.0-37-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2022
  dmi.bios.release: 8.0
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.08.00
  dmi.board.name: 8846
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.37.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.55
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.08.00:bd01/11/2022:br8.0:efr48.55:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.37.00:cvnHP:ct10:cvr:sku4V1S3UP#ABL:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 850 G8 Notebook PC
  dmi.product.sku: 4V1S3UP#ABL
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978347/+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 1969482] Re: zfs-2.1.4+ sru

[Dan Podeanu]

Got it, thank you. It sounds like testing encrypted zfs performance
could perhaps be added to the validation suite for kernels.

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

Title:
  zfs-2.1.4+ sru

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Upstream stable point release update with bugfixes, performance
  fixes, and newer kernel support as needed already in the OEM kernel
  and will be needed in the future HWE kernels.

  [Test Plan]

   * autopkgtest pass

   * kernel regression zfs testsuite pass

   * zsys integration test pass

  [Where problems could occur]

   * The stable branches maintain api/abi. Certain bugfixes do change
  userspace visible behavior of either succeeeding (when previously
  operations failed), or return errors when previously succeeding in
  error. For example there are changes when unlinking files in full
  volumes; changes to fallocate behaviour, etc. Overall they are minor
  corner cases, and bugfixes to correct the bahaviour to what is
  universally expected and how things behave on other filesystems (i.e.
  ext4).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969482/+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 1969482] Re: zfs-2.1.4+ sru

[Dan Podeanu]

@dmitri

Thank you! Quick question, the Jammy kernel version was just bumped, but
it still does not include 2.1.4 zfs module

# uname -a
Linux arpa 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux

# zfs --version
zfs-2.1.4-0ubuntu0.1
zfs-kmod-2.1.2-1ubuntu3

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

Title:
  zfs-2.1.4+ sru

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Upstream stable point release update with bugfixes, performance
  fixes, and newer kernel support as needed already in the OEM kernel
  and will be needed in the future HWE kernels.

  [Test Plan]

   * autopkgtest pass

   * kernel regression zfs testsuite pass

   * zsys integration test pass

  [Where problems could occur]

   * The stable branches maintain api/abi. Certain bugfixes do change
  userspace visible behavior of either succeeeding (when previously
  operations failed), or return errors when previously succeeding in
  error. For example there are changes when unlinking files in full
  volumes; changes to fallocate behaviour, etc. Overall they are minor
  corner cases, and bugfixes to correct the bahaviour to what is
  universally expected and how things behave on other filesystems (i.e.
  ext4).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969482/+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 1900391] Re: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled

[Dan L.]

I'm also experiencing this bug, started with the latest kernel update.

$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="20.04.4 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.4 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

$ uname -a
Linux FULGUR-KUBUNTU 5.15.0-41-generic #44~20.04.1-Ubuntu SMP Fri Jun 24 
13:27:29 
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Processor: Intel i7-5820K
Motherboard: ASRock X99 Extreme4 LGA 2011-v3
Chipset: x99

ECC RAM is not supported on my system (only on Xeon processors)

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

Title:
  EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is
  disabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4.589406] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but 
ECC is disabled
  [4.589410] EDAC sbridge: Couldn't find mci handler
  [4.589411] EDAC sbridge: Failed to register device with error -19.

  but x79 doesn't have ecc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-23-generic 5.8.0-23.24
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat2032 F pulseaudio
   /dev/snd/controlC0:  navycat2032 F pulseaudio
   /dev/snd/controlC1:  navycat2032 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Oct 19 10:19:05 2020
  InstallationDate: Installed on 2020-10-07 (11 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic 
root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed 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.8.0-23-generic N/A
   linux-backports-modules-5.8.0-23-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 150-SE-E789
  dmi.board.vendor: EVGA
  dmi.board.version: Patsburg
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
  dmi.product.family: X86 AT
  dmi.product.name: MODEL_NAME
  dmi.product.sku: PROJECT_SUB_TAG
  dmi.product.version: BASE_BOARD_VERSION
  dmi.sys.vendor: BASE_BOARD_MANUFACTURER

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900391/+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 1978347] Re: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27

[Dan Podeanu]

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

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

Title:
  horrible IO degradation with encrypted zfs root on kernels past
  5.15.0-27

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

Bug description:
  IO on encrypted zfs root has fallen off a cliff in kernel versions
  after 5.15.0-27 (the degradation is observed since version 5.15.0-30,
  also seen on -33 and -37, -25 and -27 work like a charm). Heavy usage
  almost hangs a new laptop (building large singularity images or
  synthetic testing with dd).

  I have confirmed that things are working as expected on a default +
  upgraded Ubuntu 22.04 desktop LVM+LUKS installation using another NVMe
  SSD on the same laptop. There seems to be a regression when using the
  native zfs encryption (did aes-ni acceleration get turned off?)

  How to reproduce:

  - install ubuntu 22.04 desktop from iso, don't install web updates, check use 
zfs and encryption
  - sudo apt update && apt install dstat htop
  - create a dataset with compression disabled so that dd actually writes 
things to disk

  * sudo zfs create rpool/dummy
  * sudo zfs set compress=off rpool/dummy
  * sudo chown -R myusername. /dummy

  - start dstat and htop in the background (show kernel threads in the htop 
config)
  - dd if=/dev/zero of=/dummy/bigfile bs=1M count=16384

  - sudo apt upgradeand reboot on the latest kernel, repeat

  Expected: some cpu load, dstat reports write speeds about as much as
  the SSD can sustain (2.9-3GiB/s with a 2TiB Samsung 970 EVO Plus for a
  16GiB write test, 1.4GiB/s for a few seconds then 800MiB/s sustained
  for whatever WD 512GiB model I had laying around).

  Observed on versions -30 and later: 700% or more system cpu load,
  mostly in z_wr_iss threads, writes top at around 150-180MiB/s, the
  system becomes somewhat unresponsive. Reads are also not good but I
  have not benchmarked. Booting the system and launching apps seems
  about normal due to the low IO load.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-37-generic 5.15.0-37.39
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laperlej   4100 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 10 15:52:12 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2022-05-10 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: HP HP EliteBook 850 G8 Notebook PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rgwvzq@/vmlinuz-5.15.0-37-generic 
root=ZFS=rpool/ROOT/ubuntu_rgwvzq ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-37-generic N/A
   linux-backports-modules-5.15.0-37-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2022
  dmi.bios.release: 8.0
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.08.00
  dmi.board.name: 8846
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.37.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.55
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.08.00:bd01/11/2022:br8.0:efr48.55:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.37.00:cvnHP:ct10:cvr:sku4V1S3UP#ABL:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 850 G8 Notebook PC
  dmi.product.sku: 4V1S3UP#ABL
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978347/+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 1978347] Re: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27

[Dan Podeanu]

For more context, openssl using aes-256-cbc (not aes-256-gcm, which is
unsupported by default) appears to behave identically between the two
kernels, and faster than when disabling aes-ni, therefore aes-ni appears
to be enabled in both.

# uname -a
Linux aero 5.15.0-37-generic #39-Ubuntu SMP Wed Jun 1 19:16:45 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux

# openssl speed aes-256-cbc
Doing aes-256-cbc for 3s on 16 size blocks: 186683511 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 64 size blocks: 50188595 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 256 size blocks: 12770138 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 1024 size blocks: 3204571 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 8192 size blocks: 400190 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 16384 size blocks: 199936 aes-256-cbc's in 3.00s
version: 3.0.2
built on: Thu May  5 08:04:52 2022 UTC
options: bn(64,64)
compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack -g 
-O2 -ffile-prefix-map=/build/openssl-Ke3YUO/openssl-3.0.2=. -flto=auto 
-ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong 
-Wformat -Werror=format-security -DOPENSSL_TLS_SECURITY_LEVEL=2 
-DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL 
-DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2
CPUINFO: OPENSSL_ia32cap=0x7ffef3eb:0x818d39ef7eb
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes256 bytes   1024 bytes   8192 bytes  
16384 bytes
aes-256-cbc 995645.39k  1070690.03k  1089718.44k  1093826.90k  1092785.49k  
1091917.14k

# uname -a
Linux aero 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux

# openssl speed aes-256-cbc
Doing aes-256-cbc for 3s on 16 size blocks: 186867669 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 64 size blocks: 50246758 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 256 size blocks: 12765344 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 1024 size blocks: 3204376 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 8192 size blocks: 399400 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 16384 size blocks: 200109 aes-256-cbc's in 3.00s
version: 3.0.2
built on: Thu May  5 08:04:52 2022 UTC
options: bn(64,64)
compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack -g 
-O2 -ffile-prefix-map=/build/openssl-Ke3YUO/openssl-3.0.2=. -flto=auto 
-ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong 
-Wformat -Werror=format-security -DOPENSSL_TLS_SECURITY_LEVEL=2 
-DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL 
-DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2
CPUINFO: OPENSSL_ia32cap=0x7ffef3eb:0x818d39ef7eb
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes256 bytes   1024 bytes   8192 bytes  
16384 bytes
aes-256-cbc 996627.57k  1071930.84k  1089309.35k  1093760.34k  1090628.27k  
1092861.95k

# OPENSSL_ia32cap= openssl speed aes-256-cbc
Doing aes-256-cbc for 3s on 16 size blocks: 20600986 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 64 size blocks: 5866219 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 256 size blocks: 1517023 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 1024 size blocks: 885706 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 8192 size blocks: 112410 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 16384 size blocks: 56135 aes-256-cbc's in 3.00s
version: 3.0.2
built on: Thu May  5 08:04:52 2022 UTC
options: bn(64,64)
compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack -g 
-O2 -ffile-prefix-map=/build/openssl-Ke3YUO/openssl-3.0.2=. -flto=auto 
-ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong 
-Wformat -Werror=format-security -DOPENSSL_TLS_SECURITY_LEVEL=2 
-DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL 
-DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2
CPUINFO: OPENSSL_ia32cap=0x400:0x0 env:
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes256 bytes   1024 bytes   8192 bytes  
16384 bytes
aes-256-cbc 109871.93k   125146.01k   129452.63k   302320.98k   306954.24k  
 306571.95k

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

Title:
  horrible IO degradation with encrypted zfs root on kernels past
  5.15.0-27

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  IO on encrypted zfs root has fallen off a cliff in kernel versions
  after 5.15.0-27 (the degradation is observed since version 5.15.0-30,
  also seen on -33 and -37, -25 and -27 work like a charm). Heavy usage
  almost hangs a new laptop (building large singularity images or
  synthetic testing with dd).

  I have confirmed that things are working as expected on a default +
  upgraded Ubuntu 22.04 

[Kernel-packages] [Bug 1978347] Re: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27

[Dan Podeanu]

Test script "zfs-test.sh"

- "zfs-test.sh enc" creates a 2x8 GB ZFS mirror pool, backed by two files in 
tmpfs, followed by a ZFS encrypted filesystem using the default aes-256-gcm
- "zfs-test.sh" creates a 2x8 GB ZFS mirror pool, backed by two files in tmpfs, 
followed by a ZFS unencrypted filesystem

** Attachment added: "zfs-test.sh"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978347/+attachment/5597249/+files/zfs-test.sh

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

Title:
  horrible IO degradation with encrypted zfs root on kernels past
  5.15.0-27

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  IO on encrypted zfs root has fallen off a cliff in kernel versions
  after 5.15.0-27 (the degradation is observed since version 5.15.0-30,
  also seen on -33 and -37, -25 and -27 work like a charm). Heavy usage
  almost hangs a new laptop (building large singularity images or
  synthetic testing with dd).

  I have confirmed that things are working as expected on a default +
  upgraded Ubuntu 22.04 desktop LVM+LUKS installation using another NVMe
  SSD on the same laptop. There seems to be a regression when using the
  native zfs encryption (did aes-ni acceleration get turned off?)

  How to reproduce:

  - install ubuntu 22.04 desktop from iso, don't install web updates, check use 
zfs and encryption
  - sudo apt update && apt install dstat htop
  - create a dataset with compression disabled so that dd actually writes 
things to disk

  * sudo zfs create rpool/dummy
  * sudo zfs set compress=off rpool/dummy
  * sudo chown -R myusername. /dummy

  - start dstat and htop in the background (show kernel threads in the htop 
config)
  - dd if=/dev/zero of=/dummy/bigfile bs=1M count=16384

  - sudo apt upgradeand reboot on the latest kernel, repeat

  Expected: some cpu load, dstat reports write speeds about as much as
  the SSD can sustain (2.9-3GiB/s with a 2TiB Samsung 970 EVO Plus for a
  16GiB write test, 1.4GiB/s for a few seconds then 800MiB/s sustained
  for whatever WD 512GiB model I had laying around).

  Observed on versions -30 and later: 700% or more system cpu load,
  mostly in z_wr_iss threads, writes top at around 150-180MiB/s, the
  system becomes somewhat unresponsive. Reads are also not good but I
  have not benchmarked. Booting the system and launching apps seems
  about normal due to the low IO load.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-37-generic 5.15.0-37.39
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laperlej   4100 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 10 15:52:12 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2022-05-10 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: HP HP EliteBook 850 G8 Notebook PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rgwvzq@/vmlinuz-5.15.0-37-generic 
root=ZFS=rpool/ROOT/ubuntu_rgwvzq ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-37-generic N/A
   linux-backports-modules-5.15.0-37-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2022
  dmi.bios.release: 8.0
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.08.00
  dmi.board.name: 8846
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.37.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.55
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.08.00:bd01/11/2022:br8.0:efr48.55:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.37.00:cvnHP:ct10:cvr:sku4V1S3UP#ABL:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 850 G8 Notebook PC
  dmi.product.sku: 4V1S3UP#ABL
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978347/+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 1978347] Re: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27

[Dan Podeanu]

Output from "apport-cli --save 5.15.0-37-generic.apport -p linux --file-
bug"

** Attachment added: "5.15.0-37-generic.apport"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978347/+attachment/5597248/+files/5.15.0-37-generic.apport

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

Title:
  horrible IO degradation with encrypted zfs root on kernels past
  5.15.0-27

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  IO on encrypted zfs root has fallen off a cliff in kernel versions
  after 5.15.0-27 (the degradation is observed since version 5.15.0-30,
  also seen on -33 and -37, -25 and -27 work like a charm). Heavy usage
  almost hangs a new laptop (building large singularity images or
  synthetic testing with dd).

  I have confirmed that things are working as expected on a default +
  upgraded Ubuntu 22.04 desktop LVM+LUKS installation using another NVMe
  SSD on the same laptop. There seems to be a regression when using the
  native zfs encryption (did aes-ni acceleration get turned off?)

  How to reproduce:

  - install ubuntu 22.04 desktop from iso, don't install web updates, check use 
zfs and encryption
  - sudo apt update && apt install dstat htop
  - create a dataset with compression disabled so that dd actually writes 
things to disk

  * sudo zfs create rpool/dummy
  * sudo zfs set compress=off rpool/dummy
  * sudo chown -R myusername. /dummy

  - start dstat and htop in the background (show kernel threads in the htop 
config)
  - dd if=/dev/zero of=/dummy/bigfile bs=1M count=16384

  - sudo apt upgradeand reboot on the latest kernel, repeat

  Expected: some cpu load, dstat reports write speeds about as much as
  the SSD can sustain (2.9-3GiB/s with a 2TiB Samsung 970 EVO Plus for a
  16GiB write test, 1.4GiB/s for a few seconds then 800MiB/s sustained
  for whatever WD 512GiB model I had laying around).

  Observed on versions -30 and later: 700% or more system cpu load,
  mostly in z_wr_iss threads, writes top at around 150-180MiB/s, the
  system becomes somewhat unresponsive. Reads are also not good but I
  have not benchmarked. Booting the system and launching apps seems
  about normal due to the low IO load.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-37-generic 5.15.0-37.39
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laperlej   4100 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 10 15:52:12 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2022-05-10 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: HP HP EliteBook 850 G8 Notebook PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rgwvzq@/vmlinuz-5.15.0-37-generic 
root=ZFS=rpool/ROOT/ubuntu_rgwvzq ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-37-generic N/A
   linux-backports-modules-5.15.0-37-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2022
  dmi.bios.release: 8.0
  dmi.bios.vendor: HP
  dmi.bios.version: T76 Ver. 01.08.00
  dmi.board.name: 8846
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 30.37.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 48.55
  dmi.modalias: 
dmi:bvnHP:bvrT76Ver.01.08.00:bd01/11/2022:br8.0:efr48.55:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.37.00:cvnHP:ct10:cvr:sku4V1S3UP#ABL:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 850 G8 Notebook PC
  dmi.product.sku: 4V1S3UP#ABL
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978347/+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 1978347] Re: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27

[Dan Podeanu]

I can confirm 100% repro of this bug, on several systems.

Data for a Xeon Silver 4215R on Supermicro X11SPi-TF. The only change
between 5.15.0-37-generic and 5.15.0-27-generic is booting the same
machine with a different kernel.

Write to encrypted ramdisk:
- 5.15.0-37-generic: 186 MB/s
- 5.15.0-27-generic: 1.2 GB/s (6.5x faster)

Read from encrypted RAIDz1 on 8 x ST16000NM000J, arc cache cold:
- 5.15.0-37-generic: 61.1 MB/s
- 5.15.0-27-generic: 490 MB/s (8x faster)

It only appears to affect ZFS when encryption is enabled:

Write to unencrypted ramdisk:
- 5.15.0-37-generic: 1.6 GB/s
- 5.15.0-27-generic: 1.6 GB/s (identical)

I am getting very similar data on Xeon E3-1240 v6 / Supermicro X11SSM-F
and EPYC 7282 / Supermicro H12SSL-i

I am attaching a test script and output from "apport-cli --save
5.15.0-37-generic.apport -p linux --file-bug"


Methodology below:

# uname -a
Linux aero 5.15.0-37-generic #39-Ubuntu SMP Wed Jun 1 19:16:45 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux

# Create encrypted ZFS to ramdisk using the the attached "zfs-test.sh
enc"

Write speed to encrypted ramdisk:

# dd if=/dev/zero of=/tmp/mount/zero bs=1M
dd: error writing '/tmp/mount/zero': No space left on device
7432+0 records in
7431+0 records out
7792885760 bytes (7.8 GB, 7.3 GiB) copied, 41.9707 s, 186 MB/s


# Create unencrypted ZFS to ramdisk using the the attached "zfs-test.sh"

Write speed to unencrypted ramdisk:

# dd if=/dev/zero of=/tmp/mount/zero bs=1M
dd: error writing '/tmp/mount/zero': No space left on device
7439+0 records in
7438+0 records out
7799308288 bytes (7.8 GB, 7.3 GiB) copied, 4.93472 s, 1.6 GB/s


Read speed from encrypted RAIDz1 on 8 x ST16000NM000J, arc cache cold:

# dd if=/storage/kits/ubuntu-20.04.1-desktop-amd64.iso of=/dev/null bs=1M
2656+0 records in
2656+0 records out
2785017856 bytes (2.8 GB, 2.6 GiB) copied, 45.6045 s, 61.1 MB/s


# uname -a
Linux aero 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux

# Create encrypted ZFS to ramdisk using the the attached "zfs-test.sh
enc"

Write speed to encrypted ramdisk:

# dd if=/dev/zero of=/tmp/mount/zero bs=1M
dd: error writing '/tmp/mount/zero': No space left on device
7433+0 records in
7432+0 records out
7793016832 bytes (7.8 GB, 7.3 GiB) copied, 6.28478 s, 1.2 GB/s


# Create unencrypted ZFS to ramdisk using the the attached "zfs-test.sh"

Write speed to unencrypted ramdisk:

# dd if=/dev/zero of=/tmp/mount/zero bs=1M
dd: error writing '/tmp/mount/zero': No space left on device
7439+0 records in
7438+0 records out
7799308288 bytes (7.8 GB, 7.3 GiB) copied, 4.76863 s, 1.6 GB/s

Read speed from encrypted RAIDz1 on 8 x ST16000NM000J, arc cache cold:

# dd if=/storage/kits/ubuntu-20.04.1-desktop-amd64.iso of=/dev/null bs=1M
2656+0 records in
2656+0 records out
2785017856 bytes (2.8 GB, 2.6 GiB) copied, 5.68203 s, 490 MB/s

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

Title:
  horrible IO degradation with encrypted zfs root on kernels past
  5.15.0-27

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  IO on encrypted zfs root has fallen off a cliff in kernel versions
  after 5.15.0-27 (the degradation is observed since version 5.15.0-30,
  also seen on -33 and -37, -25 and -27 work like a charm). Heavy usage
  almost hangs a new laptop (building large singularity images or
  synthetic testing with dd).

  I have confirmed that things are working as expected on a default +
  upgraded Ubuntu 22.04 desktop LVM+LUKS installation using another NVMe
  SSD on the same laptop. There seems to be a regression when using the
  native zfs encryption (did aes-ni acceleration get turned off?)

  How to reproduce:

  - install ubuntu 22.04 desktop from iso, don't install web updates, check use 
zfs and encryption
  - sudo apt update && apt install dstat htop
  - create a dataset with compression disabled so that dd actually writes 
things to disk

  * sudo zfs create rpool/dummy
  * sudo zfs set compress=off rpool/dummy
  * sudo chown -R myusername. /dummy

  - start dstat and htop in the background (show kernel threads in the htop 
config)
  - dd if=/dev/zero of=/dummy/bigfile bs=1M count=16384

  - sudo apt upgradeand reboot on the latest kernel, repeat

  Expected: some cpu load, dstat reports write speeds about as much as
  the SSD can sustain (2.9-3GiB/s with a 2TiB Samsung 970 EVO Plus for a
  16GiB write test, 1.4GiB/s for a few seconds then 800MiB/s sustained
  for whatever WD 512GiB model I had laying around).

  Observed on versions -30 and later: 700% or more system cpu load,
  mostly in z_wr_iss threads, writes top at around 150-180MiB/s, the
  system becomes somewhat unresponsive. Reads are also not good but I
  have not benchmarked. Booting the system and launching apps seems
  about normal due to the low IO load.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  

[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22

[dan the person]

i'm intrigued, how do you 'sudo grub-reboot' when the machine is
crashed?

And if anyone knows how to get the grub boot menu to respond to the
keyboard over the serial console on GCP that'd be great, as it would
have having to attach the disk to another instance to change the boot
kernel or options

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

Title:
  Docker container creation causes kernel oops on linux-aws
  5.13.0.1028.31~20.04.22

Status in linux-aws-5.13 package in Ubuntu:
  Confirmed
Status in linux-azure-5.13 package in Ubuntu:
  Confirmed
Status in linux-gcp-5.13 package in Ubuntu:
  Confirmed
Status in linux-intel-iotg-5.15 package in Ubuntu:
  Confirmed
Status in linux-oracle-5.13 package in Ubuntu:
  Confirmed
Status in linux-aws-5.13 source package in Focal:
  Fix Committed
Status in linux-azure-5.13 source package in Focal:
  Fix Committed
Status in linux-gcp-5.13 source package in Focal:
  Fix Committed
Status in linux-intel-iotg-5.15 source package in Focal:
  Won't Fix
Status in linux-oracle-5.13 source package in Focal:
  Fix Committed

Bug description:
  Running the attached script on the latest AWS AMI for Ubuntu 20.04, I
  get a kernel panic and hard reset of the node.

  [   12.314552] VFS: Close: file count is 0
  [   12.351090] [ cut here ]
  [   12.351093] kernel BUG at include/linux/fs.h:3104!
  [   12.355272] invalid opcode:  [#1] SMP PTI
  [   12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws 
#31~20.04.1-Ubuntu
  [   12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017
  [   12.371130] RIP: 0010:__fput+0x247/0x250
  [   12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff 
e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 
1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48
  [   12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246
  [   12.393425] RAX:  RBX: 000a801d RCX: 
9152e0716000
  [   12.398679] RDX: 9152cf075280 RSI: 0001 RDI: 

  [   12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 
9152dfcba2c8
  [   12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 
9152d04e9d00
  [   12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 
9152dfc2e180
  [   12.419533] FS:  () GS:9153ea90() 
knlGS:
  [   12.426937] CS:  0010 DS:  ES:  CR0: 80050033
  [   12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 
007706e0
  [   12.436716] DR0:  DR1:  DR2: 

  [   12.441941] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   12.447170] PKRU: 5554
  [   12.450355] Call Trace:
  [   12.453408]  
  [   12.456296]  fput+0xe/0x10
  [   12.459633]  task_work_run+0x70/0xb0
  [   12.463157]  do_exit+0x37b/0xaf0
  [   12.466570]  do_group_exit+0x43/0xb0
  [   12.470142]  __x64_sys_exit_group+0x18/0x20
  [   12.473989]  do_syscall_64+0x61/0xb0
  [   12.477565]  ? exit_to_user_mode_prepare+0x9b/0x1c0
  [   12.481734]  ? do_user_addr_fault+0x1d0/0x650
  [   12.485665]  ? irqentry_exit_to_user_mode+0x9/0x20
  [   12.489790]  ? irqentry_exit+0x19/0x30
  [   12.493443]  ? exc_page_fault+0x8f/0x170
  [   12.497199]  ? asm_exc_page_fault+0x8/0x30
  [   12.501013]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   12.505289] RIP: 0033:0x7f80d42a1bd6
  [   12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac.
  [   12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 
00e7
  [   12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 
7f80d42a1bd6
  [   12.526115] RDX:  RSI: 003c RDI: 

  [   12.531328] RBP:  R08: 00e7 R09: 
fe98
  [   12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 
7f80d45a4740
  [   12.541687] R13: 0002 R14: 7f80d45ad708 R15: 

  [   12.546916]  
  [   12.549829] Modules linked in: xt_conntrack xt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c 
bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul 
ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc 
input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr 
drm ip_tables x_tables autofs4
  [   12.583913] ---[ end trace 77367fed4d782aa4 ]---
  [   12.587963] RIP: 0010:__fput+0x247/0x250
  [   12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff 
e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 

[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22

[dan the person]

For those who can't update, because the machine starts docker at startup
and so crashes before you can get a shell open to upgrade to 1031,
here's my method (on gcp)

stop and edit machine to detach disk
attach to another machine boot that and mount somewhere
edit /boot/grub/grub.cfg and add single as a kernel commandline 
parameter
shutdown temp box and detach disk
reattach disk to original machine and boot
connect via serial console
sudo systemctl disable docker
remove single from grub.cfg and reboot
ssh in and update to latest kernel and reboot
sudo systemctl enable docker

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

Title:
  Docker container creation causes kernel oops on linux-aws
  5.13.0.1028.31~20.04.22

Status in linux-aws-5.13 package in Ubuntu:
  Confirmed
Status in linux-azure-5.13 package in Ubuntu:
  Confirmed
Status in linux-gcp-5.13 package in Ubuntu:
  Confirmed
Status in linux-intel-iotg-5.15 package in Ubuntu:
  Confirmed
Status in linux-oracle-5.13 package in Ubuntu:
  Confirmed
Status in linux-aws-5.13 source package in Focal:
  Fix Committed
Status in linux-azure-5.13 source package in Focal:
  Fix Committed
Status in linux-gcp-5.13 source package in Focal:
  Fix Committed
Status in linux-intel-iotg-5.15 source package in Focal:
  Won't Fix
Status in linux-oracle-5.13 source package in Focal:
  Fix Committed

Bug description:
  Running the attached script on the latest AWS AMI for Ubuntu 20.04, I
  get a kernel panic and hard reset of the node.

  [   12.314552] VFS: Close: file count is 0
  [   12.351090] [ cut here ]
  [   12.351093] kernel BUG at include/linux/fs.h:3104!
  [   12.355272] invalid opcode:  [#1] SMP PTI
  [   12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws 
#31~20.04.1-Ubuntu
  [   12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017
  [   12.371130] RIP: 0010:__fput+0x247/0x250
  [   12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff 
e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 
1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48
  [   12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246
  [   12.393425] RAX:  RBX: 000a801d RCX: 
9152e0716000
  [   12.398679] RDX: 9152cf075280 RSI: 0001 RDI: 

  [   12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 
9152dfcba2c8
  [   12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 
9152d04e9d00
  [   12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 
9152dfc2e180
  [   12.419533] FS:  () GS:9153ea90() 
knlGS:
  [   12.426937] CS:  0010 DS:  ES:  CR0: 80050033
  [   12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 
007706e0
  [   12.436716] DR0:  DR1:  DR2: 

  [   12.441941] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   12.447170] PKRU: 5554
  [   12.450355] Call Trace:
  [   12.453408]  
  [   12.456296]  fput+0xe/0x10
  [   12.459633]  task_work_run+0x70/0xb0
  [   12.463157]  do_exit+0x37b/0xaf0
  [   12.466570]  do_group_exit+0x43/0xb0
  [   12.470142]  __x64_sys_exit_group+0x18/0x20
  [   12.473989]  do_syscall_64+0x61/0xb0
  [   12.477565]  ? exit_to_user_mode_prepare+0x9b/0x1c0
  [   12.481734]  ? do_user_addr_fault+0x1d0/0x650
  [   12.485665]  ? irqentry_exit_to_user_mode+0x9/0x20
  [   12.489790]  ? irqentry_exit+0x19/0x30
  [   12.493443]  ? exc_page_fault+0x8f/0x170
  [   12.497199]  ? asm_exc_page_fault+0x8/0x30
  [   12.501013]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   12.505289] RIP: 0033:0x7f80d42a1bd6
  [   12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac.
  [   12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 
00e7
  [   12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 
7f80d42a1bd6
  [   12.526115] RDX:  RSI: 003c RDI: 

  [   12.531328] RBP:  R08: 00e7 R09: 
fe98
  [   12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 
7f80d45a4740
  [   12.541687] R13: 0002 R14: 7f80d45ad708 R15: 

  [   12.546916]  
  [   12.549829] Modules linked in: xt_conntrack xt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c 
bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul 
ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc 
input_leds parport ena serio_raw sch_fq_codel ipmi_devintf 

[Kernel-packages] [Bug 1945011] Re: kernel BUG at fs/inode.c:1676! during Live CD ubiquity partman with NTFS partitions

[Dan Bungert]

I suggest retesting this based on the Jammy ISO.

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

Title:
  kernel BUG at fs/inode.c:1676! during Live CD ubiquity partman with
  NTFS partitions

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On this computer with ext4, FAT and NTFS partitions :

  I successfully booted from the Live CD of Ubuntu Desktop 21.10 (Impish
  Indri) beta with full graphics.

  I started the ubiquity graphical interface and successfully completed
  the first screens.

  But on the 'Updates and other software screen', after clicking on
  Continue, ubiquity does NOT show the next screen (which on previous
  versions was Partitioning).

  ubiquity seems to be blocked inside partman.
  I attach the partman log file.

  syslog contains following message :
  kernel BUG at fs/inode.c:1676!

  Notably, this kernel bug message is preceeded by 2 warnings :
  WARNING: CPU: 7 PID: 18634 at fs/block_dev.c:1610 blkdev_put+0x130/0x140
  WARNING: CPU: 7 PID: 18634 at fs/block_dev.c:1576 __blkdev_put+0x1dc/0x1f0

  Thanks in advance for investigating and correcting this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 6322 F pulseaudio
   /dev/snd/controlC1:  ubuntu 6322 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 24 21:25:08 2021
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.200
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:skuSKU:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945011/+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 1946828] Re: ntfsresize hang and call traces in syslog

[Dan Bungert]

I retested this today using my same failing VM.

Test scenario:
* hardware: kvm with windows 10 on disk, UEFI
* boot Ubiquity ISO
* "try ubuntu"
* launch installer
* press the "continue" button until one of the following happens:
  * "installation type" screen shows
  or
  * hang at the "updates and other software screen" -
wait 1 minute and look for ntfsresize in process state 'D'

Results:
* Impish: 3/10 success rate ("installation type" screen reached)
* Jammy: 10/10 success rate

Based on this I consider this fixed in Jammy.

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

** Changed in: ntfs-3g (Ubuntu Jammy)
   Status: Confirmed => Invalid

** Changed in: ubiquity (Ubuntu Jammy)
   Status: Confirmed => Fix Released

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

** Changed in: ntfs-3g (Ubuntu Kinetic)
   Status: Confirmed => Invalid

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

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

Title:
  ntfsresize hang and call traces in syslog

Status in linux package in Ubuntu:
  Invalid
Status in ntfs-3g package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in ntfs-3g source package in Jammy:
  Invalid
Status in ubiquity source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Invalid
Status in ntfs-3g source package in Kinetic:
  Invalid
Status in ubiquity source package in Kinetic:
  Invalid

Bug description:
  Attempting to boot the impish final iso on my kvm VM setup with a
  windows 10 install on the virtual disk.  The install process hangs at
  the "updates and other software" screen, apparently on a ntfsresize
  call.  Mind you, this is before I have chosen disks to partition - I'm
  at the step where I can choose a Normal or Minimal installation.

  While this is not a 100% reproduction rate issue, the rate seems high
  - above 50% I would guess.  If I try to quickly click thru the
  installer on boot it might be a little more likely.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-19-generic 5.13.0-19.19
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4609 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 13 02:40:56 2021
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   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
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-5.2
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.2:sku:cvnQEMU:ct1:cvrpc-q35-5.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-5.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946828/+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 1973357] Re: Kernel update to 4.15.0-177 fails to load some kernel modules

[Dan]

I just experienced the same problem today on my Asus G752VT Republic of
Gaming laptop.  I ended up having to force a power-off by holding down
the power button for five seconds because it was stuck trying to booting
up.  It also wouldn't properly reboot with ALT+CTRL+DEL, getting stuck
doing that as well.  Once I powered it back on again, I could regain
control once I had GRUB boot into the previous kernel again
(4.15.0-176).  I was able to repeat the same problem by letting it boot
into the newer kernel (4.15.0-177) and had to repeat the same steps to
regain control again.

miles@unicron:~$ uname -a
Linux unicron 4.15.0-176-generic #185-Ubuntu SMP Tue Mar 29 17:40:04 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux

miles@unicron:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.6 LTS
Release:18.04
Codename:   bionic

Some lshw details on the model:
  *-core
   description: Motherboard
   product: G752VT
   vendor: ASUSTeK COMPUTER INC.
   physical id: 0
   version: 1.0
   serial: BSN12345678901234567
   slot: MIDDLE
 *-firmware
  description: BIOS
  vendor: American Megatrends Inc.
  physical id: 0
  version: G752VT.213
  date: 01/06/2016
  size: 64KiB
  capacity: 5952KiB
  capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd 
int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard 
int14serial int17printer acpi usb smartbattery biosbootspecification uefi

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

Title:
  Kernel update to 4.15.0-177 fails to load some kernel modules

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After update and reboot, severe delay occurs to log in due to network
  not available.  After about 2-3 minutes login worked.  No network, no
  sound and maybe other items.  Upon further troubleshooting, the
  network module is not being loaded.  Loading it enabled network.
  Details below:

  Linux Mint Cinnamon 19.1

  kernel: from 4.15.0-176-generic to 4.15.0-177-generic

  4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64
  x86_64 x86_64 GNU/Linux

  Lenovo ideapad 330S laptop

  lsb_release -rd

  Description:  Linux Mint 19.1 Tessa
  Release:  19.1

  1) cat /proc/version_signature > version.log

  Ubuntu 4.15.0-176.185-generic 4.15.18

  2) sudo lspci -vnvn > lspci-vnvn.log

  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5914] (rev 08)
Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host 
Bridge/DRAM Registers [17aa:383b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 
[8086:5917] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Lenovo UHD Graphics 620 [17aa:396b]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 14
PASIDCtl: Enable- Exec- Priv-
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 8000, Page Request 

[Kernel-packages] [Bug 1969853] Re: No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works)

[Dan Wood]

Thank you. The proposed firmware linux-firmware
20220329.git681281e4-0ubuntu3 has fixed Bluetooth (and also WiFi) on my
Dell XPS 13 L322X machine.

I haven't noticed any new problems, so I think the proposed fix is good
to go.

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

Title:
  No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works)

Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-firmware source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  No bluetooth found on QCA9565.

  [Test Case]

  See below.

  [Fix]

  Provide ar3k/* firmware blobs.

  [Where Problems Could Occur]

  None expected, this is a regression from Impish.

  [Original Description]

  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
     Docs: man:bluetoothd(8)
     Main PID: 1100 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2220 F pulseaudio
   /dev/snd/pcmC0D0p:   diego  2220 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15-3567
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 2.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.18.0
  dmi.board.name: 0MM5K1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+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 1950914] Re: [daily jammy-live-server-amd64] Hangs at start of VM installation

[Dan Bungert]

I will be happy to provide logs, however as the system fails boot ~1s in
I'm not sure how to do so.  Marking Confirmed to override.

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

Title:
  [daily jammy-live-server-amd64] Hangs at start of VM installation

Status in subiquity:
  Invalid
Status in libvirt package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I downloaded  the 2021.11.14 daily:

  -rw-rwxr--+ 1 doug doug 1277655040 Nov 14 09:12 jammy-live-server-
  amd64.iso

  I tried to install it as a VM on a debian 11 server host and an Ubuntu
  20.04.3 server host, both were up to date as of a few days ago.
  Command used (pretty much the same command I have used for years):

  virt-install -n serv-jj -r 8192 \
  --disk path=/home/doug/vm/serv-jj.img,bus=virtio,size=50 \
  -c jammy-live-server-amd64-2021-11-14.iso \
  --network bridge=br0,model=virtio,mac=52:54:00:27:1c:6e \
  --video=vmvga --graphics vnc,listen=0.0.0.0 --noautoconsole -v --vcpus=4

  On both hosts it just hangs a after a couple of seconds. "virsh list"
  shows it running and "virsh destroy" does work.

  Note: I have never used the new installer before, I have always used
  the legacy Debain installer in the past, but I gather is is no longer
  supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1950914/+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 1950914] Re: [daily jammy-live-server-amd64] Hangs at start of VM installation

[Dan Bungert]

I can reproduce this as written using Focal as the host and the 22.04 
live-server iso.
If I remove the "--video=vmvga" it actually boots, and an install completed 
without issue.
This doesn't seem Subiquity specific, however.


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

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

** Changed in: subiquity
   Status: New => Invalid

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

Title:
  [daily jammy-live-server-amd64] Hangs at start of VM installation

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

Bug description:
  I downloaded  the 2021.11.14 daily:

  -rw-rwxr--+ 1 doug doug 1277655040 Nov 14 09:12 jammy-live-server-
  amd64.iso

  I tried to install it as a VM on a debian 11 server host and an Ubuntu
  20.04.3 server host, both were up to date as of a few days ago.
  Command used (pretty much the same command I have used for years):

  virt-install -n serv-jj -r 8192 \
  --disk path=/home/doug/vm/serv-jj.img,bus=virtio,size=50 \
  -c jammy-live-server-amd64-2021-11-14.iso \
  --network bridge=br0,model=virtio,mac=52:54:00:27:1c:6e \
  --video=vmvga --graphics vnc,listen=0.0.0.0 --noautoconsole -v --vcpus=4

  On both hosts it just hangs a after a couple of seconds. "virsh list"
  shows it running and "virsh destroy" does work.

  Note: I have never used the new installer before, I have always used
  the legacy Debain installer in the past, but I gather is is no longer
  supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1950914/+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 1970052] Re: No Bluetooth available in fresh install of Ubuntu 22.04

[Dan Wood]

I think this may be the same bug as #1970117

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

Title:
  No Bluetooth available in fresh install of Ubuntu 22.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A fresh install of Ubuntu 22.04 on a Dell XPS 13 (L322X) laptop, which
  according to lsusb has an Atheros Bluetooth device 0cf3:3004

  The system thinks there is no Bluetooth available and prompts for a
  dongle.

  Bluetooth worked perfectly with Ubuntu 20.04 LTS. The hardware is
  unchanged.

  Thanks,
  Dan.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-25-generic 5.15.0-25.25
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1032 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sat Apr 23 20:10:19 2022
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. XPS L322X
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/vgubuntu-root 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-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970052/+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 1970117] Re: Atheros firmware missing in Ubuntu 22.04

[Dan Wood]

I think bug #1970052 is the same problem.

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

Title:
  Atheros firmware missing in Ubuntu 22.04

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  linux-firmware 20220329.git681281e4-0ubuntu1 used by Ubuntu 22.04 does not 
contain drivers for some Atheros WiFi/Bluetooth chipsets, which were included 
in the previous Ubuntu releases.
  The package is missing some files from 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree,
 specifically:
  - ar3k (whole directory, was present in impish, missing in jammy)
  - ar*.fw - firmware for AR7010, AR9170 and AR9271 (can't find in the impish 
version)

  Because of that Bluetooth can't be enabled and WiFi is unstable on
  devices equipped with Atheros chipsets. In my case the following
  errors are reported by dmesg:

  [3.653613] usb 1-1.1: Direct firmware load for ar3k/AthrBT_0x1102.dfu 
failed with error -2
  [3.653619] Bluetooth: Patch file not found ar3k/AthrBT_0x1102.dfu
  [3.653626] Bluetooth: Loading patch file failed
  [3.653631] ath3k: probe of 1-1.1:1.0 failed with error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 20220329.git681281e4-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  krzys  1642 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sun Apr 24 17:32:11 2022
  Dependencies: firmware-sof-signed 2.0-1ubuntu2
  InstallationDate: Installed on 2018-11-06 (1265 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Aspire E1-571G
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=ee6503b7-82f1-4ece-9e74-935ca46a08f4 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-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (0 days ago)
  dmi.bios.date: 12/25/2012
  dmi.bios.release: 2.11
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.11
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.11:bd12/25/2012:br2.11:efr0.0:svnAcer:pnAspireE1-571G:pvrV2.11:rvnAcer:rnEA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.11:skuAspireE1-571G_064C_V2.11:
  dmi.product.family: Type1Family
  dmi.product.name: Aspire E1-571G
  dmi.product.sku: Aspire E1-571G_064C_V2.11
  dmi.product.version: V2.11
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1970117/+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 1970052] [NEW] No Bluetooth available in fresh install of Ubuntu 22.04

[Dan Wood]

Public bug reported:

A fresh install of Ubuntu 22.04 on a Dell XPS 13 (L322X) laptop, which
according to lsusb has an Atheros Bluetooth device 0cf3:3004

The system thinks there is no Bluetooth available and prompts for a
dongle.

Bluetooth worked perfectly with Ubuntu 20.04 LTS. The hardware is
unchanged.

Thanks,
Dan.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-25-generic 5.15.0-25.25
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dan1032 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sat Apr 23 20:10:19 2022
InstallationDate: Installed on 2022-04-23 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Dell Inc. XPS L322X
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/vgubuntu-root 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-25-generic N/A
 linux-backports-modules-5.15.0-25-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/28/2013
dmi.bios.release: 0.1
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0PJHXN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
dmi.product.family: ChiefRiver System
dmi.product.name: XPS L322X
dmi.product.sku: XPS L322X
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug jammy

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

Title:
  No Bluetooth available in fresh install of Ubuntu 22.04

Status in linux package in Ubuntu:
  New

Bug description:
  A fresh install of Ubuntu 22.04 on a Dell XPS 13 (L322X) laptop, which
  according to lsusb has an Atheros Bluetooth device 0cf3:3004

  The system thinks there is no Bluetooth available and prompts for a
  dongle.

  Bluetooth worked perfectly with Ubuntu 20.04 LTS. The hardware is
  unchanged.

  Thanks,
  Dan.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-25-generic 5.15.0-25.25
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1032 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sat Apr 23 20:10:19 2022
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. XPS L322X
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/vgubuntu-root 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-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970052/+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 1956821] Re: System hangs on reboot and shutdown

[Dan]

Can confirm the same! kernel version 5.13.0-28-generic fixes it!

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

Title:
  System hangs on reboot and shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from kernel 5.13.0-22-generic to 5.13.0-23-generic,
  the system cannot be powered down or rebooted, just hangs
  indefinitely.

  A screenshot with the final screen is shown here:
  https://askubuntu.com/questions/1385794/system-hangs-on-reboot-and-poweroff

  I can restore the previous behavior (i.e. a correct shutdown) with
  choosing the previous kernel in the grub menu on boot.

  
  Is there anything I can do to provide more information and debug this further?

  My system information:
  Description:  Ubuntu 21.10
  Release:  21.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  petr   1146 F pulseaudio
   /dev/snd/controlC0:  petr   1146 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-07 (62 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20YA
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic 
root=/dev/mapper/vgxubuntu-root ro
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.3
  Tags:  impish
  Uname: Linux 5.13.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2021
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMCN21WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: ThinkBook 13s G3 ACN
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMCN21WW:bd04/07/2021:br1.21:efr1.16:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN:
  dmi.product.family: ThinkBook 13s G3 ACN
  dmi.product.name: 20YA
  dmi.product.sku: LENOVO_MT_20YA_BU_idea_FM_ThinkBook 13s G3 ACN
  dmi.product.version: ThinkBook 13s G3 ACN
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956821/+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 1958724] Re: System Shutdown and resume hangs since Kernel linux-image-5.13.0-23-generic

[Dan]

Hey everyone! kernel version 5.13.0-28-generic is out and it seems to
fix this issue! Myself and another user were already able to confirm
that. Good luck everyone!

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

Title:
  System Shutdown and resume hangs since Kernel linux-
  image-5.13.0-23-generic

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  on my Medion E14304 Ubuntu was working fine until Kernel 5.13.0.21.
  Since Version 5.13.0.23 System Shutdown and resume hangs. The System
  does not stop also after a long time.

  The last messages in recovery mode on the root console are:

  Reached target Power-off
  ... systemd-udevd[295]: ... Worker [311] processing SEQNUM=3047 is taking time
  Waiting for process systemd-udevd, systemd-udevd 

  Perhaps my attached dmesg and lsmod helps. All messages are in one file.
   
  Thank you very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 22 16:59:05 2022
  InstallationDate: Installed on 2021-12-25 (27 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958724/+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 1958724] Re: System Shutdown and resume hangs since Kernel linux-image-5.13.0-23-generic

[Dan]

Hi John,

Ideally you’ll be able to read specific references to fixes within the
kernel release notes but in practice they are not that organized per se.
That said, in the other ticket I referenced above, one or two users
mentioned that kernel 5.14.X fixes this issue (which seems to be part of
ubuntu 20.04.4 that’s suppose to be released on February 24). So I’m
guessing unless the kernel is updated earlier, at the latest this should
be fixed by end of February.

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

Title:
  System Shutdown and resume hangs since Kernel linux-
  image-5.13.0-23-generic

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  on my Medion E14304 Ubuntu was working fine until Kernel 5.13.0.21.
  Since Version 5.13.0.23 System Shutdown and resume hangs. The System
  does not stop also after a long time.

  The last messages in recovery mode on the root console are:

  Reached target Power-off
  ... systemd-udevd[295]: ... Worker [311] processing SEQNUM=3047 is taking time
  Waiting for process systemd-udevd, systemd-udevd 

  Perhaps my attached dmesg and lsmod helps. All messages are in one file.
   
  Thank you very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 22 16:59:05 2022
  InstallationDate: Installed on 2021-12-25 (27 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958724/+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 1956882] Re: Ubuntu does not boot after upgrade to Linux 5.13-0-23

[Dan]

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

** This bug has been marked a duplicate of bug 1958724
   System Shutdown and resume hangs since Kernel linux-image-5.13.0-23-generic

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

Title:
  Ubuntu does not boot after upgrade to Linux 5.13-0-23

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the latest upgrade to Linux 5.13.0-23 the disk shows some
  activity, but the screen remains black and powers off. To be sure I
  reinstalled Ubuntu from scratch and I have the same error again. My
  hardware is a Ryzen 3 2200G

  I only can boot from Linux 5.13.0-19. On the precious installation I
  could reboot from Linux 5.13.0-22, but -23 failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  9 16:11:04 2022
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2022-01-09 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956882/+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 1956821] Re: System hangs on reboot and shutdown

[Dan]

This is the same as https://bugs.launchpad.net/ubuntu/+source/linux-
signed-hwe-5.13/+bug/1958724 which is also linked to a bunch more
related issues. All seem to be AMD systems. Not marking either as
duplicates of one another to maintain proper visibility (though I think
they definitely are).

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

Title:
  System hangs on reboot and shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from kernel 5.13.0-22-generic to 5.13.0-23-generic,
  the system cannot be powered down or rebooted, just hangs
  indefinitely.

  A screenshot with the final screen is shown here:
  https://askubuntu.com/questions/1385794/system-hangs-on-reboot-and-poweroff

  I can restore the previous behavior (i.e. a correct shutdown) with
  choosing the previous kernel in the grub menu on boot.

  
  Is there anything I can do to provide more information and debug this further?

  My system information:
  Description:  Ubuntu 21.10
  Release:  21.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  petr   1146 F pulseaudio
   /dev/snd/controlC0:  petr   1146 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-07 (62 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20YA
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic 
root=/dev/mapper/vgxubuntu-root ro
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.3
  Tags:  impish
  Uname: Linux 5.13.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2021
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMCN21WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: ThinkBook 13s G3 ACN
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMCN21WW:bd04/07/2021:br1.21:efr1.16:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN:
  dmi.product.family: ThinkBook 13s G3 ACN
  dmi.product.name: 20YA
  dmi.product.sku: LENOVO_MT_20YA_BU_idea_FM_ThinkBook 13s G3 ACN
  dmi.product.version: ThinkBook 13s G3 ACN
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956821/+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 1956821] Re: System hangs on reboot and shutdown

[Dan]

Same for me since 5.13.0-27-generic.
PC: ASUS PN-50
CPU: AMD Ryzen 5 4800U with Radeon Graphics
Kernel: 5.13.0-27-generic, UBUNTU 20.04

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

Title:
  System hangs on reboot and shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from kernel 5.13.0-22-generic to 5.13.0-23-generic,
  the system cannot be powered down or rebooted, just hangs
  indefinitely.

  A screenshot with the final screen is shown here:
  https://askubuntu.com/questions/1385794/system-hangs-on-reboot-and-poweroff

  I can restore the previous behavior (i.e. a correct shutdown) with
  choosing the previous kernel in the grub menu on boot.

  
  Is there anything I can do to provide more information and debug this further?

  My system information:
  Description:  Ubuntu 21.10
  Release:  21.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  petr   1146 F pulseaudio
   /dev/snd/controlC0:  petr   1146 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-07 (62 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20YA
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic 
root=/dev/mapper/vgxubuntu-root ro
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.3
  Tags:  impish
  Uname: Linux 5.13.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2021
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMCN21WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: ThinkBook 13s G3 ACN
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMCN21WW:bd04/07/2021:br1.21:efr1.16:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN:
  dmi.product.family: ThinkBook 13s G3 ACN
  dmi.product.name: 20YA
  dmi.product.sku: LENOVO_MT_20YA_BU_idea_FM_ThinkBook 13s G3 ACN
  dmi.product.version: ThinkBook 13s G3 ACN
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956821/+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 1957018] Re: System hangs on reboot and shutdown

[Dan]

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

** This bug has been marked a duplicate of bug 1958724
   System Shutdown and resume hangs since Kernel linux-image-5.13.0-23-generic

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

Title:
  System hangs on reboot and shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from kernel 5.13.0-22-generic to 5.13.0-25-generic,
  the system cannot be powered down or rebooted, just hangs
  indefinitely.

   This is a possible duplicate of the link below

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956821

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957018/+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 1958768] Re: System fails to shutdown or reboot

[Dan]

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

** This bug has been marked a duplicate of bug 1958724
   System Shutdown and resume hangs since Kernel linux-image-5.13.0-23-generic

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

Title:
  System fails to shutdown or reboot

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  My system has suddenly stopped from powering off or rebooting. It hangs on 
"systemd-shutdown: waiting for process"
  I have tried several suggestions on the ubuntu forum to alleviate this - but 
none work.
  This seemed to begin after an update last week.
  I have waited 30 minutes or more and the messages :waiting for 
process:system-udevdworker[###] contine to be posted on the command line, but 
no stutdown occurs

  I have removed "quiet splash" from grub and can see that Shutdown
  Target is reached but then the system hangs before actual poweroff.

  Ubuntu 20.04.3 LTS Release 20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 23 11:23:43 2022
  InstallationDate: Installed on 2021-04-17 (281 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958768/+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 1958724] Re: System Shutdown and resume hangs since Kernel linux-image-5.13.0-23-generic

[Dan]

I think this bug specifically affects AMD processor based systems.
Whoever picks it up should look into it from that angle IMO.

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

Title:
  System Shutdown and resume hangs since Kernel linux-
  image-5.13.0-23-generic

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  on my Medion E14304 Ubuntu was working fine until Kernel 5.13.0.21.
  Since Version 5.13.0.23 System Shutdown and resume hangs. The System
  does not stop also after a long time.

  The last messages in recovery mode on the root console are:

  Reached target Power-off
  ... systemd-udevd[295]: ... Worker [311] processing SEQNUM=3047 is taking time
  Waiting for process systemd-udevd, systemd-udevd 

  Perhaps my attached dmesg and lsmod helps. All messages are in one file.
   
  Thank you very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 22 16:59:05 2022
  InstallationDate: Installed on 2021-12-25 (27 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958724/+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 1958007] Re: Regression in 5.13.0-23: laptop cannot suspend or turn off

[Dan]

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

** This bug has been marked a duplicate of bug 1958724
   System Shutdown and resume hangs since Kernel linux-image-5.13.0-23-generic

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

Title:
  Regression in 5.13.0-23: laptop cannot suspend or turn off

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Starting from 5.13.0-23-lowlatency my laptop fails to suspend, turn
  off or reboot.

  On suspend the screen turns off, but the power button LED stays on (it
  should be blinking when suspended), the keyboard backlight and the CPU
  fan stays on. I cannot resume the laptop by pressing the power button
  or any other button.

  On power off and restart I see the splash screen and nothing happens.

  The last working Ubuntu kernel is 5.13.0-22-lowlatency. 5.13.0-23-lowlatency 
and 5.13.0-25-lowlatency are broken.
  I also tried the latest upstream mainline kernel, 
linux-image-unsigned-5.16.0-051600-lowlatency_5.16.0-051600.202201091830_amd64.deb,
 and it doesn't have this regression.

  This happens on a Lenovo IdeaPad Flex 5, the AMD variant (Ryzen 7
  4700U).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-lowlatency 5.13.0.25.36
  ProcVersionSignature: Ubuntu 5.13.0-23.23-lowlatency 5.13.19
  Uname: Linux 5.13.0-23-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dszoboszlay   2528 F pulseaudio
   /dev/snd/controlC0:  dszoboszlay   2528 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 09:01:15 2022
  InstallationDate: Installed on 2020-06-04 (589 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81X2
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-23-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-lowlatency N/A
   linux-backports-modules-5.13.0-23-lowlatency  N/A
   linux-firmware1.201.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-29 (77 days ago)
  dmi.bios.date: 10/15/2020
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EECN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Flex 5 14ARE05
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrEECN29WW:bd10/15/2020:br1.29:efr1.19:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05:skuLENOVO_MT_81X2_BU_idea_FM_IdeaPadFlex514ARE05:
  dmi.product.family: IdeaPad Flex 5 14ARE05
  dmi.product.name: 81X2
  dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05
  dmi.product.version: IdeaPad Flex 5 14ARE05
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958007/+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 1959070] Re: NO standby or shutdown possible (5.13.0.27)

[Dan]

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

** This bug has been marked a duplicate of bug 1958724
   System Shutdown and resume hangs since Kernel linux-image-5.13.0-23-generic

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

Title:
  NO standby or shutdown possible (5.13.0.27)

Status in linux package in Ubuntu:
  New

Bug description:
  I am using Xubuntu (actual LTS-version) with AMD-Ryzen
  with Kernel: 5.13.0.27 there is no regular powerdwn or Standby possible:
  The system does not switch off with: "tl@tl-as:~$ shutdown now -h" too;
  If I boot with the last version in the boot options (5.11.0.46) I can use 
Standby, Powerdown again  normally
  Additional infos: 
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  -Systemstarts-
  Wed Jan 26 07:44  : 5.13.0-27-generi
  Wed Jan 26 08:01  : 5.11.0-46-generi
  Wed Jan 26 06:55  : 5.13.0-27-generi
  Wed Jan 26 04:39  : 5.13.0-27-generi
  Tue Jan 25 20:33  : 5.13.0-27-generi
  Tue Jan 25 12:40  : 5.13.0-27-generi
  Tue Jan 25 06:53  : 5.13.0-27-generi
  Tue Jan 25 06:51  : 5.13.0-27-generi
  Tue Jan 25 06:46  : 5.13.0-27-generi
  Tue Jan 25 04:31  : 5.13.0-27-generi
  Mon Jan 24 22:15  : 5.13.0-27-generi
  Mon Jan 24 11:42  : 5.13.0-27-generi
  Mon Jan 24 08:38  : 5.13.0-27-generi
  Sun Jan 23 06:27  : 5.11.0-46-generi
  Wed Jan 19 09:16  : 5.11.0-46-generi
  Tue Jan 18 19:19  : 5.11.0-46-generi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959070/+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 1958724] Re: System Shutdown and resume hangs since Kernel linux-image-5.13.0-23-generic

[Dan]

I believe I’m having the same issue. I see the same failure regarding
systemd-udevd, systemd-udevd. This did not happen on the last version I
had - 5.11.0-46-generic.

Also it tells me that systemd-udevd worker (541)processing SEQNUM=3327 killed. 
And that worker 541 terminated by signal 9 (kill) and worker (541) failed. 

All this happens as I’m trying to reboot. It just shows this error while
the system hangs indefinitely.


System runs AMD Ryzen 7 4800U
Ubuntu 20.04.3
Uname: 5.13.0-27-generic

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

Title:
  System Shutdown and resume hangs since Kernel linux-
  image-5.13.0-23-generic

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  on my Medion E14304 Ubuntu was working fine until Kernel 5.13.0.21.
  Since Version 5.13.0.23 System Shutdown and resume hangs. The System
  does not stop also after a long time.

  The last messages in recovery mode on the root console are:

  Reached target Power-off
  ... systemd-udevd[295]: ... Worker [311] processing SEQNUM=3047 is taking time
  Waiting for process systemd-udevd, systemd-udevd 

  Perhaps my attached dmesg and lsmod helps. All messages are in one file.
   
  Thank you very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 22 16:59:05 2022
  InstallationDate: Installed on 2021-12-25 (27 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958724/+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 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

[Dan Lenski]

@Stuart-ward wrote…

> This is still a current problem
> 
> $ dpkg -l | grep -i openvpn
> ii network-manager-openvpn 1.8.14-1 amd64 network management framework 
> (OpenVPN plugin core)
> ii network-manager-openvpn-gnome 1.8.14-1 amd64 network management framework 
> (OpenVPN plugin GNOME GUI)
> ii openvpn 2.5.1-3ubuntu1 amd64 virtual private network daemon

Once again, OpenConnect and OpenVPN are *not* the same thing. At all.

For your VPN connection, are you using OpenConenct (the original subject
of this bug report), or are you using OpenVPN (completely different and
should have a separate bug files)?

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

Title:
  SSH fails with connection timed out - in VPN and hangs here "expecting
  SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

Status in linux package in Ubuntu:
  Invalid
Status in openconnect package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Invalid
Status in openconnect source package in Xenial:
  Confirmed

Bug description:
  Hello Team,

  SSH timeout issue, once connect to VPN.

  Environment

  ==
  Dell XPS 9570 
  Ubuntu 16.04.6 Xenial Xerus)
  kernel - 4.15.0-55-generic

  $dpkg -l | grep -i openssh
  ii  openssh-client 1:7.2p2-4ubuntu2.8  --> 
  ii  openssh-server 1:7.2p2-4ubuntu2.8  
  ii  openssh-sftp-server  1:7.2p2-4ubuntu2.8

  
  VPN tunnel info 
  
  vpn0  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:IP  P-t-P:xx  Mask:255.255.252.0
inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1406  Metric:1
RX packets:962 errors:0 dropped:0 overruns:0 frame:0
TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:87839 (87.8 KB)  TX bytes:238740 (238.7 KB)

  Issue
  
  Unable to connect to any host via ssh or sftp after VPN connection 

  Tried 
  =

  Reinstalled the openssh-client package and still no luck. May I know
  why the default cipher is not taking/hanging? Please let me know .
  There were no recent changes.

  
  Workaround
  ===
  Able to connect to ssh / sftp $ssh -c aes128-ctr   user@IP

  
  Below is the debug ssh client logs ===
  ==

  $ssh -vvv  user@ip
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug2: resolving "IP" port 22
  debug2: ssh_connect_direct: needpriv 0
  debug1: Connecting to IP [IP] port 22.
  debug1: Connection established.
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 
Ubuntu-4ubuntu0.3
  debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400
  debug2: fd 3 setting O_NONBLOCK
  debug1: Authenticating to IP:22 as 'user'
  debug3: send packet: type 20
  debug1: SSH2_MSG_KEXINIT sent
  debug3: receive packet: type 20
  debug1: SSH2_MSG_KEXINIT received
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
  debug2: host key algorithms: 
ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
  debug2: ciphers ctos: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
  debug2: ciphers stoc: 

[Kernel-packages] [Bug 1907962] Re: The touchpad doesn't work and sometimes keyboard

[Dan Cooper]

The fix with the module i2c_hid does not work anymore on 21.10 with
kernel 5.13.0-22-generic.

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

Title:
  The touchpad doesn't work and sometimes keyboard

Status in linux package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  Ubuntu 5.4.0-58.64-generic 5.4.73

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oleksandr   1379 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 13 14:13:00 2020
  InstallationDate: Installed on 2020-12-11 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7410
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=be9b4d42-06a6-492c-a49c-b1f88b6c58c6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/23/2020
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 2.12
  dmi.board.name: FJNB2D4
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: A2
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.chassis.version: LIFEBOOK U7410
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/23/2020:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7410:pvr10601115935:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D4:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7410:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK U7410
  dmi.product.sku: SK00
  dmi.product.version: 10601115935
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907962/+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 1626838] Re: yakkety compiling failed on ubuntu trusty

[Dan Streetman]

** Changed in: trusty-backports
   Status: New => Won't Fix

** Changed in: yakkety-backports
   Status: New => 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/1626838

Title:
  yakkety compiling failed on ubuntu trusty

Status in trusty-backports:
  Won't Fix
Status in Ubuntu Server:
  New
Status in Yakkety Backports:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi ubuntu kernel team,

  I am compiling my own ubuntu kernel on ubuntu trusty, and I git clone 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/yakkety,  
the build almost success, but failed at the end with missing modules,  I 
haven't done any change for the source code :
  Then I start a docker container using xenial image,  try the same build 
steps,  I can successfullly build kernel deb pkgs .  Do you have idea why it 
throw missing module error on ubuntu trusty ?  Thanks .

  root@kbuild:~/yakkety# uname -a
  Linux kbuild 3.13.0-58-generic #97-Ubuntu SMP Wed Jul 8 02:56:15 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  root@kbuild:~/yakkety# apt-get build-dep linux-image-4.4.0-36-generic
  root@kbuild:~/yakkety# fakeroot debian/rules clean
  root@kbuild:~/yakkety# AUTOBUILD=1 fakeroot debian/rules binary-generic
  --ignore 
  make[2]: Leaving directory `/root/yakkety/debian/build/build-generic'
  make[1]: Leaving directory `/root/yakkety'
  Debug: module-check-generic
  install -d /root/yakkety/debian.master/abi/4.4.0-34.53/amd64
  find /root/yakkety/debian/build/build-generic/ -name \*.ko | \
  sed -e 's/.*\/\([^\/]*\)\.ko/\1/' | sort > 
/root/yakkety/debian.master/abi/4.4.0-34.53/amd64/generic.modules
  II: Checking modules for generic...
 reading new modules...read 4590 modules.
 reading old modules...
MISS: spl
MISS: splat
MISS: zavl
MISS: zcommon
MISS: zfs
MISS: znvpair
MISS: zpios
MISS: zunicode
read 4598 modules : new(0)  missing(8)
  EE: Missing modules (start begging for mercy)
  make: *** [module-check-generic] Error 1


  
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 23 03:51 seq
   crw-rw 1 root audio 116, 33 Sep 23 03:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-58-generic 
root=UUID=80575ee5-f6ee-41e2-bab6-e4af1c26d1c1 ro nofb nomodeset vga=normal 
console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-58-generic N/A
   linux-backports-modules-3.13.0-58-generic  N/A
   linux-firmware 1.127.16
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2015.1.2:cvnBochs:ct1:cvr:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 2015.1.2
  dmi.sys.vendor: OpenStack Foundation

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1626838/+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 1950214] [NEW] raspi 64 bit Impish image can't 'apt upgrade' without adding swap on pi zero 2

[Dan Bungert]

Public bug reported:

When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit Impish
image and nothing new installed to it, update-initramfs fails like so:

Setting up linux-firmware (1.201.1) ... 
 
update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi 
 
Killed  
 E: mkinitramfs failure 
zstd -q -19 -T0 137 
  

Adding a swap file to the setup allowed 'apt -f install' to run
successfully.

How the device was setup
1) xzcat | dd the sdcard with the impish 64 bit server image
2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, link 
getty@ttyGS0.service
) as suggested in 
https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console
3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest 
of the 16GB flash, e2fsck, resize2fs
4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per 
https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html
5) boot, connect to wireless, ssh in
6) apt update && apt upgrade
7) observe above issue

ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: linux-firmware 1.201.1
ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14
Uname: Linux 5.13.0-1009-raspi aarch64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Nov  8 19:47 seq
 crw-rw 1 root audio 116, 33 Nov  8 19:47 timer
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.13.0-1009-raspi.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu71
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:
CasperMD5CheckResult: unknown
Date: Mon Nov  8 21:00:59 2021
Dependencies:
 
ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
ImageMediaBuild: 20211013
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
 
Lspci-vt: -[:00]-
Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
PackageArchitecture: all
PciMultimedia:
 
ProcFB: 0 BCM2708 FB
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 
smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 
vc_mem.mem_size=0x2000  dwc_otg.lpm_enable=0 console=ttyS0,115200 
console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait 
fixrtc quiet splash modules-load=dwc2,g_serial
Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux-firmware
StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 
bcm2835_codec vc_sm_cma
Title: package linux-firmware 1.201.1 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:

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


** Tags: apport-package arm64 arm64-image impish raspi-image staging uec-images

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

Title:
  raspi 64 bit Impish image can't 'apt upgrade' without adding swap on
  pi zero 2

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit
  Impish image and nothing new installed to it, update-initramfs fails
  like so:

  Setting up linux-firmware (1.201.1) ...   
   
  update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi   
   
  Killed
   E: mkinitramfs failure 
zstd -q -19 -T0 137 
  

  Adding a swap file to the setup allowed 'apt -f install' to run
  successfully.

  How the device was setup
  1) xzcat | dd the sdcard with the impish 64 bit server image
  2) setup for serial over USB (dtoverlay=dwc2, 

[Kernel-packages] [Bug 1946828] Re: ntfsresize hang and call traces in syslog

[Dan Bungert]

** Tags added: fr-1823

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

Title:
  ntfsresize hang and call traces in syslog

Status in linux package in Ubuntu:
  Confirmed
Status in ntfs-3g package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Attempting to boot the impish final iso on my kvm VM setup with a
  windows 10 install on the virtual disk.  The install process hangs at
  the "updates and other software" screen, apparently on a ntfsresize
  call.  Mind you, this is before I have chosen disks to partition - I'm
  at the step where I can choose a Normal or Minimal installation.

  While this is not a 100% reproduction rate issue, the rate seems high
  - above 50% I would guess.  If I try to quickly click thru the
  installer on boot it might be a little more likely.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-19-generic 5.13.0-19.19
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4609 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 13 02:40:56 2021
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   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
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-5.2
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.2:sku:cvnQEMU:ct1:cvrpc-q35-5.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-5.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946828/+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 1946828] Re: ntfsresize hang and call traces in syslog

[Dan Bungert]

@Etienne - agree, probably a dupe

@Jeremy - I ran "ntfsresize -f -i /dev/sda4" manually before the
installer ran and ntfsresize had no issue.  Later during this same run,
I saw the hang when ntfsresize was run by Ubiquity.

@Jean-Pierre - I suspect this is a kernel bug more than I suspect a
ntfsresize one.

Here's a sample process tree:
   5991 S   sh -c ubiquity gtk_ui
   5992 S   /bin/sh /usr/lib/udisks2/udisks2-inhibit /usr/lib/ubiquit
   6002 Sl  /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity gtk_ui
   6411 Ss+ /bin/busybox tail -f /var/log/installer/debug -f /var/log
   8639 S   /usr/bin/perl -w /usr/bin/debconf-communicate -fnonintera
   9107 S   /usr/share/ubiquity/activate-dmraid && /bin/partman
   9108 S   /usr/share/ubiquity/activate-dmraid && /bin/partman
   9114 S   /bin/sh /bin/partman
  10014 S   /bin/sh /lib/partman/display.d/10initial_auto
  10060 S   /bin/sh /lib/partman/display.d/10initial_auto
  10062 S   /bin/sh /lib/partman/automatically_partition/10resize_use
  10131 D   [ntfsresize]

ntfsresize has been invoked as "ntfsresize -f -i /dev/sda4", where this
sda4 is a partition created by Windows 10, is NTFS, and is 508MiB.
Also, if I kill parent process of ntfsresize (pid 10062 in this case),
the install is able to continue.

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

Title:
  ntfsresize hang and call traces in syslog

Status in linux package in Ubuntu:
  Confirmed
Status in ntfs-3g package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Attempting to boot the impish final iso on my kvm VM setup with a
  windows 10 install on the virtual disk.  The install process hangs at
  the "updates and other software" screen, apparently on a ntfsresize
  call.  Mind you, this is before I have chosen disks to partition - I'm
  at the step where I can choose a Normal or Minimal installation.

  While this is not a 100% reproduction rate issue, the rate seems high
  - above 50% I would guess.  If I try to quickly click thru the
  installer on boot it might be a little more likely.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-19-generic 5.13.0-19.19
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4609 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 13 02:40:56 2021
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   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
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-5.2
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.2:sku:cvnQEMU:ct1:cvrpc-q35-5.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-5.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946828/+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 1947708] Re: Cannot configure suspend-then-hibernate

[Dan Streetman]

> [   82.230208] Lockdown: systemd-logind: hibernation is restricted;
see man kernel_lockdown.7

you're using UEFI secure boot, which puts the system into 'lockdown',
which disallows (unencrypted) hibernation.

So this isn't a problem with systemd, this requires the kernel to handle
encrypted hibernation.

I *think* that functionality isn't yet in the upstream kernel, as I think this 
thread was the last discussion about adding it:
https://lore.kernel.org/lkml/20210220013255.1083202-1-matthewgarr...@google.com/


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

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

Title:
  Cannot configure suspend-then-hibernate

Status in linux package in Ubuntu:
  New

Bug description:
  Previous bug 1947617 was closed because my swap space was
  insufficient. Swap was increased to 24G and the problem remains.

  Configuring login to suspend-then-hiberrnate when the lid is off and
  configuring sleep so that hibernate happens 10 seconds after suspend,
  when trying to test with:

  sudo systemctl suspend-then-hibernate

  I get:

  Failed to suspend system, hibernate later via logind: Sleep verb
  "suspend-then-hibernate" not supported

  This could be a security vulnerability. If the user expects the system
  to suspend (and then lock) when the lid is off and it does not work,
  somebody could then just reopen the lid and get access.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: systemd 248.3-1ubuntu8
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: i3
  Date: Tue Oct 19 11:51:50 2021
  InstallationDate: Installed on 2021-10-14 (4 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: HP HP ENVY x360 Convertible 13-ay0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=e85d08c2-ae82-4f0f-a625-a5012616c934 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2021
  dmi.bios.release: 15.20
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 876E
  dmi.board.vendor: HP
  dmi.board.version: 12.52
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 12.52
  dmi.modalias: 
dmi:bvnInsyde:bvrF.20:bd07/30/2021:br15.20:efr12.52:svnHP:pnHPENVYx360Convertible13-ay0xxx:pvrType1ProductConfigId:sku3V693EA#ABF:rvnHP:rn876E:rvr12.52:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 13-ay0xxx
  dmi.product.sku: 3V693EA#ABF
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.systemd.logind.conf: 2021-10-18T18:51:43.976989
  mtime.conffile..etc.systemd.sleep.conf: 2021-10-18T18:52:04.283409

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947708/+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 1906273] Re: iwlwifi - very slow for intel 9260/9560 wireless cards

[Dan]

You could try to disable 11n with the 8 option: `11n_disable=8`. It
worked for me.

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

Title:
  iwlwifi - very slow for intel 9260/9560 wireless cards

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I have tried 2 intel wifi cards (9260 and previously 9560, which i
  thought was broken) in my msi GF63 laptop. Both cards work fine when
  using windows, getting me a speed of 450 mbps consistently.

  But when using linux with ubuntu 20.04, this speed is reduced to max
  25 mbps (using the same 5G network).

  I'm using iwlwifi-9260-th-b0-jf-b0-46.ucode and kernel 5.6.19.

  I have tried with a previous version of the driver
  (iwlwifi-9260-th-b0-jf-b0-34.ucode), but unfortunately gave me the
  same result. I have also tried different kernels (5.4.0 that came with
  ubuntu 20.04 and also 5.3.18), to no avail.

  I've also tried fiddling with settings in /etc/modprobe.d/iwlwifi-
  opt.conf

  options iwlwifi 11n_disable=1
  options iwlwifi swcrypto=0
  options iwlwifi bt_coex_active=0
  options iwlwifi power_save=0
  options iwlwifi uapsd_disable=1
  options iwlmvm power_scheme=1

  These seem to get me the 'best' results, of merely 25 mbps.

  windows, when getting 450 mbps, uses this driver version 22.0.0.6
  (https://downloadcenter.intel.com/download/29902)

  I have disabled power-management so i don't think it's a power save
  issue like someone else suggested.

  From iw and iwconfig, the max bit rate seems to be 54.0 Mbps, but the
  card can surely do much faster.

  Any idea on how to fix this? Please let me know if more info is
  needed. Thanks!

  dmesg | grep iwl
  [2.287446] iwlwifi :04:00.0: enabling device ( -> 0002)
  [2.301450] iwlwifi :04:00.0: Found debug destination: EXTERNAL_DRAM
  [2.301452] iwlwifi :04:00.0: Found debug configuration: 0
  [2.301710] iwlwifi :04:00.0: loaded firmware version 46.6bf1df06.0 
9260-th-b0-jf-b0-46.ucode op_mode iwlmvm
  [2.356367] iwlwifi :04:00.0: Detected Intel(R) Wireless-AC 9260 
160MHz, REV=0x324
  [2.370323] iwlwifi :04:00.0: Applying debug destination EXTERNAL_DRAM
  [2.370983] iwlwifi :04:00.0: Allocated 0x0040 bytes for firmware 
monitor.
  [2.429183] iwlwifi :04:00.0: base HW address: f2:ac:12:fa:47:6f
  [2.496763] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
  [2.509009] iwlwifi :04:00.0 wlp4s0: renamed from wlan0
  [3.401664] iwlwifi :04:00.0: Applying debug destination EXTERNAL_DRAM
  [3.515240] iwlwifi :04:00.0: Applying debug destination EXTERNAL_DRAM
  [3.585957] iwlwifi :04:00.0: FW already configured (0) - 
re-configuring

  
  iw list
  Wiphy phy0
max # scan SSIDs: 20
max scan IEs length: 464 bytes
max # sched scan SSIDs: 20
max # match sets: 11
max # scan plans: 2
max scan plan interval: 65535
max scan plan iterations: 254
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Device supports AP-side u-APSD.
Device supports T-DLS.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
* GCMP-128 (00-0f-ac:8)
* GCMP-256 (00-0f-ac:9)
* CMAC (00-0f-ac:6)
* GMAC-128 (00-0f-ac:11)
* GMAC-256 (00-0f-ac:12)
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
 * IBSS
 * managed
 * AP
 * AP/VLAN
 * monitor
 * P2P-client
 * P2P-GO
 * P2P-device
Band 1:
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (22.0 dBm)
* 2417 MHz [2] (22.0 dBm)
* 2422 MHz [3] (22.0 dBm)
* 2427 MHz [4] (22.0 dBm)
* 2432 MHz [5] (22.0 dBm)
* 2437 MHz [6] (22.0 dBm)
* 2442 MHz [7] (22.0 dBm)
* 2447 MHz 

[Kernel-packages] [Bug 1946507] Re: Ubuntu Install Setup Freeze

[Dan Bungert]

Possibly the same as the one I filed (LP: #1946828)

@Men K - is this a 100% of the time issue for you, or does this possibly
go away upon reboot?

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

Title:
  Ubuntu Install Setup Freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  While trying to Install Ubuntu 21.10 , the setup freeze after clicking
  continue on Step 4 where it asks if you wish to install Updates , and
  i have selected Normal Installation when i click continue then setup
  freeze so im not able to click any other button just QUIT button is
  working , other buttons are grayed out and not clickable , i have
  tried many methods since 2 days been trying nomodeset acpi=off and
  other but nothing works for me , i need help .

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubiquity 21.10.6 [modified: 
lib/partman/automatically_partition/question]
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  8 15:56:06 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset 
file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946507/+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 1938474] Re: delve golang debugger can't read vvar on arm64

[Dan Bungert]

Should the 'dd' flag be set in this case?

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

Title:
  delve golang debugger can't read vvar on arm64

Status in Delve:
  Unknown
Status in delve package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Also documented upstream:
  https://github.com/go-delve/delve/issues/2630

  In version 1.6.1 of the delve golang debugger, a 'dump' feature was added.
  https://github.com/go-delve/delve/pull/2173

  Since that time, arm64 autopkgtest of delve has been failing like so:

  
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/d/delve/20210707_003312_d3699@/log.gz
  === RUN   TestDump
  proc_test.go:5117: testing normal dump
  proc_test.go:5029: bad DumpState 
{Mutex:sync.Mutex{state:0, sema:0x0}, Dumping:false, 
AllDone:true, Canceled:false, DoneChan:(chan struct {})(nil), ThreadsDone:5, 
ThreadsTotal:5, MemDone:0x657b000, MemTotal:0x657d000, Err:error(nil)}
  --- FAIL: TestDump (0.98s)

  The test fails becaue MemDone != MemTotal.
  The decision on what to dump or not is based on smaps.
  The failing item is vvar.
  err when attempting to read is
  error(syscall.Errno) golang.org/x/sys/unix.EIO (5)

  Notably however, this test passes in debian CI. (kernel 4.19)
  Also, running on older series such as bionic/focal does pass.

  vvar section from vm with kernel 5.4 (test pass):
  924a4000-924a5000 r--p  00:00 0  
[vvar]
  Size:  4 kB
  KernelPageSize:4 kB
  MMUPageSize:   4 kB
  Rss:   0 kB
  Pss:   0 kB
  Shared_Clean:  0 kB
  Shared_Dirty:  0 kB
  Private_Clean: 0 kB
  Private_Dirty: 0 kB
  Referenced:0 kB
  Anonymous: 0 kB
  LazyFree:  0 kB
  AnonHugePages: 0 kB
  ShmemPmdMapped:0 kB
  FilePmdMapped:0 kB
  Shared_Hugetlb:0 kB
  Private_Hugetlb:   0 kB
  Swap:  0 kB
  SwapPss:   0 kB
  Locked:0 kB
  THPeligible:0
  VmFlags: rd mr de

  vvar from failing case
  ac144000-ac146000 r--p  00:00 0  
[vvar]
  Size:  8 kB
  KernelPageSize:4 kB
  MMUPageSize:   4 kB
  Rss:   0 kB
  Pss:   0 kB
  Shared_Clean:  0 kB
  Shared_Dirty:  0 kB
  Private_Clean: 0 kB
  Private_Dirty: 0 kB
  Referenced:0 kB
  Anonymous: 0 kB
  LazyFree:  0 kB
  AnonHugePages: 0 kB
  ShmemPmdMapped:0 kB
  FilePmdMapped: 0 kB
  Shared_Hugetlb:0 kB
  Private_Hugetlb:   0 kB
  Swap:  0 kB
  SwapPss:   0 kB
  Locked:0 kB
  THPeligible:0
  VmFlags: rd mr pf de

  Two noticible differences
  1) 4kB vs 8kB size
  2) Failing case adds the "pf" flag ("pure PFN range")

  Open questions:
  1) Would we expect that a debugger could read vvar on arm64?
  2) Any thoughts on why this seems to work on older kernels?
  3) Do we believe this to be a kernel bug,
     or should the delve debugger not expect to read vvar?
  4) Is it sensible for a debugger to attempt to read things with the "pf"
     flag?  Note that the "dd" ("do not include area into core dump")
     flag is not set.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.11.0-20-generic 5.11.0-20.21+21.10.1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 29 21:21 seq
   crw-rw 1 root audio 116, 33 Jul 29 21:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu67
  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:
  CasperMD5CheckResult: pass
  Date: Thu Jul 29 21:34:34 2021
  InstallationDate: Installed on 2021-07-29 (0 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Alpha arm64 (20210729)
  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
  PciMultimedia:

  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-20-generic 

[Kernel-packages] [Bug 1946828] [NEW] ntfsresize hang and call traces in syslog

[Dan Bungert]

Public bug reported:

Attempting to boot the impish final iso on my kvm VM setup with a
windows 10 install on the virtual disk.  The install process hangs at
the "updates and other software" screen, apparently on a ntfsresize
call.  Mind you, this is before I have chosen disks to partition - I'm
at the step where I can choose a Normal or Minimal installation.

While this is not a 100% reproduction rate issue, the rate seems high -
above 50% I would guess.  If I try to quickly click thru the installer
on boot it might be a little more likely.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-19-generic 5.13.0-19.19
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu 4609 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.465
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 13 02:40:56 2021
IwConfig:
 lono wireless extensions.
 
 enp1s0no wireless extensions.
LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
 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
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed 
maybe-ubiquity quiet splash ---
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-19-generic N/A
 linux-backports-modules-5.13.0-19-generic  N/A
 linux-firmware 1.201
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2015
dmi.bios.release: 0.0
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-5.2
dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.2:sku:cvnQEMU:ct1:cvrpc-q35-5.2:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-5.2
dmi.sys.vendor: QEMU

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

** Affects: ntfs-3g (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug impish

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

** Also affects: ntfs-3g (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/1946828

Title:
  ntfsresize hang and call traces in syslog

Status in linux package in Ubuntu:
  Confirmed
Status in ntfs-3g package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New

Bug description:
  Attempting to boot the impish final iso on my kvm VM setup with a
  windows 10 install on the virtual disk.  The install process hangs at
  the "updates and other software" screen, apparently on a ntfsresize
  call.  Mind you, this is before I have chosen disks to partition - I'm
  at the step where I can choose a Normal or Minimal installation.

  While this is not a 100% reproduction rate issue, the rate seems high
  - above 50% I would guess.  If I try to quickly click thru the
  installer on boot it might be a little more likely.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-19-generic 5.13.0-19.19
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4609 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 13 02:40:56 2021
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, 

[Kernel-packages] [Bug 1945066] Re: package udev 245.4-4ubuntu3.11 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1

[Dan Streetman]

your system has kernel warnings and hung task errors, and you appear to
be using an unsupported 5.9 kernel, it seems the problem is there, not
with systemd/udevd.

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

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

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

Title:
  package udev 245.4-4ubuntu3.11 failed to install/upgrade: installed
  udev package post-installation script subprocess returned error exit
  status 1

Status in linux package in Ubuntu:
  Invalid

Bug description:
  The error explains itself, I think.

  Best regards.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.11
  Uname: Linux 5.9.10-050910-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  AptOrdering:
   udev:amd64: Install
   libudev1:amd64: Install
   libudev1:amd64: Configure
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 70-snap.stellarium-daily.rules 70-snap.hw-probe.rules 
70-snap.snapd.rules 70-snap.snap-store.rules 70-snap.zoom-client.rules 
70-snap.acestreamplayer.rules 70-snap.brave.rules
  Date: Sat Sep 25 16:37:14 2021
  ErrorMessage: installed udev package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2020-11-06 (323 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.9.10-050910-generic 
root=UUID=4ebadc28-5f91-4ef7-84ea-9f51b6e6b941 ro quiet splash 
amdgpu.exp_hw_support=1 vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3.11 failed to install/upgrade: installed 
udev package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2021
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN31WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945066/+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 1944712] Re: systemd/237-3ubuntu10.52 ADT test failure with linux-aws-5.4/5.4.0-1057.60~18.04.1

[Dan Bungert]

** Tags added: update-excuse

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

Title:
  systemd/237-3ubuntu10.52 ADT test failure with linux-
  aws-5.4/5.4.0-1057.60~18.04.1

Status in linux-aws-5.4 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux-aws-5.4/5.4.0-1057.60~18.04.1 on bionic. Whether this
  is caused by the dep8 tests of the tested source or the kernel has yet
  to be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/s/systemd/20210923_022411_52338@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.4/+bug/1944712/+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 1944785] Re: systemd adt runs triggered by linux-meta-* hitting timeouts

[Dan Bungert]

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

** This bug has been marked a duplicate of bug 1944712
   systemd/237-3ubuntu10.52 ADT test failure with 
linux-aws-5.4/5.4.0-1057.60~18.04.1

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

Title:
  systemd adt runs triggered by linux-meta-* hitting timeouts

Status in linux-meta package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Systemd amd64 autopkgtest runs, when triggered by non-linux-meta
  packages, usually pass.  You can find some failures on a possible
  flaky TEST-29-PORTABLE.  Ignore those for the moment.

  Systemd amd64 autopkgtest runs, triggered by linux-meta packages, usually 
fail and hit the 2 second timeout on the systemd upstream-1 (and sometimes 
upstream-2) test.  I did find an outlier that hit the same timeout:
  248.3-1ubuntu3e2fsprogs/1.46.3-1ubuntu3   2021-09-05 15:02:56 UTC 
6h 58m 46s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1944785/+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 1944712] Re: systemd/237-3ubuntu10.52 ADT test failure with linux-aws-5.4/5.4.0-1057.60~18.04.1

[Dan Bungert]

I filed one like this as well, so let me merge with this one.
My notes:

Systemd amd64 autopkgtest runs, when triggered by non-linux-meta
packages, usually pass. You can find some failures on a possible flaky
TEST-29-PORTABLE. Ignore those for the moment.

Systemd amd64 autopkgtest runs, triggered by linux-meta packages, usually fail 
and hit the 2 second timeout on the systemd upstream-1 (and sometimes 
upstream-2) test. I did find an outlier that hit the same timeout:
248.3-1ubuntu3 e2fsprogs/1.46.3-1ubuntu3 2021-09-05 15:02:56 UTC 6h 58m 46s

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

Title:
  systemd/237-3ubuntu10.52 ADT test failure with linux-
  aws-5.4/5.4.0-1057.60~18.04.1

Status in linux-aws-5.4 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux-aws-5.4/5.4.0-1057.60~18.04.1 on bionic. Whether this
  is caused by the dep8 tests of the tested source or the kernel has yet
  to be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/s/systemd/20210923_022411_52338@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.4/+bug/1944712/+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 1944785] [NEW] systemd adt runs triggered by linux-meta-* hitting timeouts

[Dan Bungert]

Public bug reported:

Systemd amd64 autopkgtest runs, when triggered by non-linux-meta
packages, usually pass.  You can find some failures on a possible flaky
TEST-29-PORTABLE.  Ignore those for the moment.

Systemd amd64 autopkgtest runs, triggered by linux-meta packages, usually fail 
and hit the 2 second timeout on the systemd upstream-1 (and sometimes 
upstream-2) test.  I did find an outlier that hit the same timeout:
248.3-1ubuntu3  e2fsprogs/1.46.3-1ubuntu3   2021-09-05 15:02:56 UTC 6h 58m 
46s

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

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


** Tags: update-excuse

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

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

Title:
  systemd adt runs triggered by linux-meta-* hitting timeouts

Status in linux-meta package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Systemd amd64 autopkgtest runs, when triggered by non-linux-meta
  packages, usually pass.  You can find some failures on a possible
  flaky TEST-29-PORTABLE.  Ignore those for the moment.

  Systemd amd64 autopkgtest runs, triggered by linux-meta packages, usually 
fail and hit the 2 second timeout on the systemd upstream-1 (and sometimes 
upstream-2) test.  I did find an outlier that hit the same timeout:
  248.3-1ubuntu3e2fsprogs/1.46.3-1ubuntu3   2021-09-05 15:02:56 UTC 
6h 58m 46s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1944785/+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 1940860] Re: Mellanox NIC interface names change between 5.4 and 5.8

[Dan Streetman]

> we should be careful to ignore NICs with randomly generated MACs (see
bug 1936972).

ugh nics with LAA?

yeah, it can be hard to 'uniquely' identify a nic, especially since it's
so common to clone macs for bonds, bridges, vlans, and in some cases
even duplicate hw devices with the same nic (e.g. bug 1843381).

> My initial thought is that perhaps subiquity installs should do what
MAAS installs do and configure netplan to always use the install-time
names.

I'm generally not a fan of how MAAS configures netplan to force-rename
interfaces; that sounds to me like it's destined for interface naming
collisions. But I don't have any better immediate suggestion for
'foolproof' matching of all possible nics that might exist across all
kernel driver versions, either.

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

Title:
  Mellanox NIC interface names change between 5.4 and 5.8

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

Bug description:
  I noticed on a couple of systems that my network interface names
  change when upgrading from the focal LTS (5.4) kernel to the focal HWE
  (both 5.8 & 5.11) kernels. Both systems have Mellanox Connect-X 5
  NICs.

  dannf@bizzy:~$ uname -a
  Linux bizzy 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 19:10:30 UTC 2021 
aarch64 aarch64 aarch64 GNU/Linux
  dannf@bizzy:~$ ls /sys/class/net
  enp1s0f0  enp1s0f1  enx3e8734bc294f  lo

  dannf@bizzy:~$ uname -a
  Linux bizzy 5.8.0-63-generic #71~20.04.1-Ubuntu SMP Thu Jul 15 17:46:44 UTC 
2021 aarch64 aarch64 aarch64 GNU/Linux
  dannf@bizzy:~$ ls /sys/class/net
  enp1s0f0np0  enp1s0f1np1  enx3e8734bc294f  lo

  dannf@bizzy:~$ uname -a
  Linux bizzy 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11 15:58:08 UTC 
2021 aarch64 aarch64 aarch64 GNU/Linux
  dannf@bizzy:~$ ls /sys/class/net
  enp1s0f0np0  enp1s0f1np1  enx3e8734bc294f  lo

  I bisected this down to a kernel change:
  # first bad commit: [c6acd629eec754a9679f922d51f90e44c769b80c] net/mlx5e: Add 
support for devlink-port in non-representors mode

  The impact is that your network can fail to come up after
  transitioning from the LTS kernel to the HWE kernel. Now, this isn't a
  huge problem for MAAS installs because MAAS configures netplan to
  always use the same names as were used at commissioning. It does
  impact subiquity based installs however, which do not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1940860/+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 1940860] Re: Mellanox NIC interface names change between 5.4 and 5.8

[Dan Streetman]

systemd/udevd appears to be working exactly as advertised, using the
phys_port_name when it's provided by the device's kernel driver; should
this be marked invalid for systemd, or is there actually some change
needed there?

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

Title:
  Mellanox NIC interface names change between 5.4 and 5.8

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

Bug description:
  I noticed on a couple of systems that my network interface names
  change when upgrading from the focal LTS (5.4) kernel to the focal HWE
  (both 5.8 & 5.11) kernels. Both systems have Mellanox Connect-X 5
  NICs.

  dannf@bizzy:~$ uname -a
  Linux bizzy 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 19:10:30 UTC 2021 
aarch64 aarch64 aarch64 GNU/Linux
  dannf@bizzy:~$ ls /sys/class/net
  enp1s0f0  enp1s0f1  enx3e8734bc294f  lo

  dannf@bizzy:~$ uname -a
  Linux bizzy 5.8.0-63-generic #71~20.04.1-Ubuntu SMP Thu Jul 15 17:46:44 UTC 
2021 aarch64 aarch64 aarch64 GNU/Linux
  dannf@bizzy:~$ ls /sys/class/net
  enp1s0f0np0  enp1s0f1np1  enx3e8734bc294f  lo

  dannf@bizzy:~$ uname -a
  Linux bizzy 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11 15:58:08 UTC 
2021 aarch64 aarch64 aarch64 GNU/Linux
  dannf@bizzy:~$ ls /sys/class/net
  enp1s0f0np0  enp1s0f1np1  enx3e8734bc294f  lo

  I bisected this down to a kernel change:
  # first bad commit: [c6acd629eec754a9679f922d51f90e44c769b80c] net/mlx5e: Add 
support for devlink-port in non-representors mode

  The impact is that your network can fail to come up after
  transitioning from the LTS kernel to the HWE kernel. Now, this isn't a
  huge problem for MAAS installs because MAAS configures netplan to
  always use the same names as were used at commissioning. It does
  impact subiquity based installs however, which do not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940860/+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 1938474] Re: delve golang debugger can't read vvar on arm64

[Dan Bungert]

** Tags added: update-excuse

** Description changed:

+ Also documented upstream:
+ https://github.com/go-delve/delve/issues/2630
+ 
  In version 1.6.1 of the delve golang debugger, a 'dump' feature was added.
  https://github.com/go-delve/delve/pull/2173
  
  Since that time, arm64 autopkgtest of delve has been failing like so:
  
  
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/d/delve/20210707_003312_d3699@/log.gz
  === RUN   TestDump
  proc_test.go:5117: testing normal dump
  proc_test.go:5029: bad DumpState 
{Mutex:sync.Mutex{state:0, sema:0x0}, Dumping:false, 
AllDone:true, Canceled:false, DoneChan:(chan struct {})(nil), ThreadsDone:5, 
ThreadsTotal:5, MemDone:0x657b000, MemTotal:0x657d000, Err:error(nil)}
  --- FAIL: TestDump (0.98s)
  
  The test fails becaue MemDone != MemTotal.
  The decision on what to dump or not is based on smaps.
  The failing item is vvar.
  err when attempting to read is
  error(syscall.Errno) golang.org/x/sys/unix.EIO (5)
  
  Notably however, this test passes in debian CI. (kernel 4.19)
  Also, running on older series such as bionic/focal does pass.
  
  vvar section from vm with kernel 5.4 (test pass):
  924a4000-924a5000 r--p  00:00 0  
[vvar]
  Size:  4 kB
  KernelPageSize:4 kB
  MMUPageSize:   4 kB
  Rss:   0 kB
  Pss:   0 kB
  Shared_Clean:  0 kB
  Shared_Dirty:  0 kB
  Private_Clean: 0 kB
  Private_Dirty: 0 kB
  Referenced:0 kB
  Anonymous: 0 kB
  LazyFree:  0 kB
  AnonHugePages: 0 kB
  ShmemPmdMapped:0 kB
  FilePmdMapped:0 kB
  Shared_Hugetlb:0 kB
  Private_Hugetlb:   0 kB
  Swap:  0 kB
  SwapPss:   0 kB
  Locked:0 kB
  THPeligible:0
  VmFlags: rd mr de
  
  vvar from failing case
  ac144000-ac146000 r--p  00:00 0  
[vvar]
  Size:  8 kB
  KernelPageSize:4 kB
  MMUPageSize:   4 kB
  Rss:   0 kB
  Pss:   0 kB
  Shared_Clean:  0 kB
  Shared_Dirty:  0 kB
  Private_Clean: 0 kB
  Private_Dirty: 0 kB
  Referenced:0 kB
  Anonymous: 0 kB
  LazyFree:  0 kB
  AnonHugePages: 0 kB
  ShmemPmdMapped:0 kB
  FilePmdMapped: 0 kB
  Shared_Hugetlb:0 kB
  Private_Hugetlb:   0 kB
  Swap:  0 kB
  SwapPss:   0 kB
  Locked:0 kB
  THPeligible:0
  VmFlags: rd mr pf de
  
  Two noticible differences
  1) 4kB vs 8kB size
  2) Failing case adds the "pf" flag ("pure PFN range")
  
  Open questions:
  1) Would we expect that a debugger could read vvar on arm64?
  2) Any thoughts on why this seems to work on older kernels?
  3) Do we believe this to be a kernel bug,
     or should the delve debugger not expect to read vvar?
  4) Is it sensible for a debugger to attempt to read things with the "pf"
-flag?  Note that the "dd" ("do not include area into core dump")
-flag is not set.
+    flag?  Note that the "dd" ("do not include area into core dump")
+    flag is not set.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.11.0-20-generic 5.11.0-20.21+21.10.1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 29 21:21 seq
   crw-rw 1 root audio 116, 33 Jul 29 21:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu67
  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:
  CasperMD5CheckResult: pass
  Date: Thu Jul 29 21:34:34 2021
  InstallationDate: Installed on 2021-07-29 (0 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Alpha arm64 (20210729)
  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
  PciMultimedia:
  
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
  
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-20-generic 
root=/dev/mapper/username--vg-username--lv ro
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-20-generic N/A
   linux-backports-modules-5.11.0-20-generic  N/A
   linux-firmware 1.199
  

[Kernel-packages] [Bug 1938474] [NEW] delve golang debugger can't read vvar on arm64

[Dan Bungert]

Public bug reported:

In version 1.6.1 of the delve golang debugger, a 'dump' feature was added.
https://github.com/go-delve/delve/pull/2173

Since that time, arm64 autopkgtest of delve has been failing like so:

https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/d/delve/20210707_003312_d3699@/log.gz
=== RUN   TestDump
proc_test.go:5117: testing normal dump
proc_test.go:5029: bad DumpState {Mutex:sync.Mutex{state:0, 
sema:0x0}, Dumping:false, AllDone:true, Canceled:false, DoneChan:(chan struct 
{})(nil), ThreadsDone:5, ThreadsTotal:5, MemDone:0x657b000, MemTotal:0x657d000, 
Err:error(nil)}
--- FAIL: TestDump (0.98s)

The test fails becaue MemDone != MemTotal.
The decision on what to dump or not is based on smaps.
The failing item is vvar.
err when attempting to read is
error(syscall.Errno) golang.org/x/sys/unix.EIO (5)

Notably however, this test passes in debian CI. (kernel 4.19)
Also, running on older series such as bionic/focal does pass.

vvar section from vm with kernel 5.4 (test pass):
924a4000-924a5000 r--p  00:00 0  [vvar]
Size:  4 kB
KernelPageSize:4 kB
MMUPageSize:   4 kB
Rss:   0 kB
Pss:   0 kB
Shared_Clean:  0 kB
Shared_Dirty:  0 kB
Private_Clean: 0 kB
Private_Dirty: 0 kB
Referenced:0 kB
Anonymous: 0 kB
LazyFree:  0 kB
AnonHugePages: 0 kB
ShmemPmdMapped:0 kB
FilePmdMapped:0 kB
Shared_Hugetlb:0 kB
Private_Hugetlb:   0 kB
Swap:  0 kB
SwapPss:   0 kB
Locked:0 kB
THPeligible:0
VmFlags: rd mr de

vvar from failing case
ac144000-ac146000 r--p  00:00 0  [vvar]
Size:  8 kB
KernelPageSize:4 kB
MMUPageSize:   4 kB
Rss:   0 kB
Pss:   0 kB
Shared_Clean:  0 kB
Shared_Dirty:  0 kB
Private_Clean: 0 kB
Private_Dirty: 0 kB
Referenced:0 kB
Anonymous: 0 kB
LazyFree:  0 kB
AnonHugePages: 0 kB
ShmemPmdMapped:0 kB
FilePmdMapped: 0 kB
Shared_Hugetlb:0 kB
Private_Hugetlb:   0 kB
Swap:  0 kB
SwapPss:   0 kB
Locked:0 kB
THPeligible:0
VmFlags: rd mr pf de

Two noticible differences
1) 4kB vs 8kB size
2) Failing case adds the "pf" flag ("pure PFN range")

Open questions:
1) Would we expect that a debugger could read vvar on arm64?
2) Any thoughts on why this seems to work on older kernels?
3) Do we believe this to be a kernel bug,
   or should the delve debugger not expect to read vvar?
4) Is it sensible for a debugger to attempt to read things with the "pf"
   flag?  Note that the "dd" ("do not include area into core dump")
   flag is not set.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.11.0-20-generic 5.11.0-20.21+21.10.1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic aarch64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jul 29 21:21 seq
 crw-rw 1 root audio 116, 33 Jul 29 21:21 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu67
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:
CasperMD5CheckResult: pass
Date: Thu Jul 29 21:34:34 2021
InstallationDate: Installed on 2021-07-29 (0 days ago)
InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Alpha arm64 (20210729)
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
PciMultimedia:

ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-20-generic 
root=/dev/mapper/username--vg-username--lv ro
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-20-generic N/A
 linux-backports-modules-5.11.0-20-generic  N/A
 linux-firmware 1.199
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2015
dmi.bios.release: 0.0
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: virt-5.2
dmi.modalias: 

[Kernel-packages] [Bug 1837937] Re: CRASH

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  CRASH

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The screen froze but the mouse was still moving then it all froze and
  said systemd-journal not able to write entry. I had to press the power
  button.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-9-generic 5.2.0-9.10
  ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1
  Uname: Linux 5.2.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  administrator   2068 F pulseaudio
   /dev/snd/controlC0:  administrator   2068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 25 15:11:47 2019
  InstallationDate: Installed on 2019-06-05 (50 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605)
  MachineType: HP HP Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-9-generic N/A
   linux-backports-modules-5.2.0-9-generic  N/A
   linux-firmware   1.181
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82F6
  dmi.board.vendor: HP
  dmi.board.version: 40.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: X7T78UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  administrator   2852 F pulseaudio
   /dev/snd/controlC0:  administrator   2852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-05 (51 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605)
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=512M-:192M 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-9-generic N/A
   linux-backports-modules-5.2.0-9-generic  N/A
   linux-firmware   1.181
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  eoan
  Uname: Linux 5.2.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/15/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82F6
  dmi.board.vendor: HP
  dmi.board.version: 40.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: X7T78UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  administrator   2852 F pulseaudio
   /dev/snd/controlC0:  administrator   2852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-05 (51 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605)
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1884281] Re: UC20 images do not use predictable interface names on RPi4

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  UC20 images do not use predictable interface names on RPi4

Status in snapd:
  Triaged
Status in linux-raspi package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Image tested: http://cdimage.ubuntu.com/ubuntu-core/20/dangerous-
  beta/pending/ubuntu-core-20-arm64+raspi.img.xz

  Boot the image and check the naming of the ethernet interfaces. On
  most devices (amd64, rpi3 etc) systemd predicatable interface naming
  is applied e.g. enxb827eb7d1eee. However on specifically RPi4 devices
  traditional naming is used e.g. eth0, eth1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1884281/+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 1861645] Re: PC fails to shutdown.

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  PC fails to shutdown.

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I have a pc with Motherboard Gigabyte H370M D3H, Processor Intel Core I3 8100 
3.6Ghz 6MbL3, RAM Corsair 16Mb 2400 Hz. I can reboot pc without any problem, 
but pc is stuck on ubuntu logo when I shutdown. while shutdown keyboard and 
mouse are turned off but pc remains on. I have to turn the mains power off to 
shutdown the pc. I think this is a major bug in Ubuntu 19.10. I searched for a 
solution on the internet but could not find any that works. Kindly help to fix 
it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  prakash1438 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-31 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 003: ID 1a2c:0e24 China Resource Semico Co., Ltd USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. H370M-D3H
  Package: systemd 242-7ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=a883551d-0fff-4cdb-bc6d-d442860a0ec0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  RfKill:
   
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: Default string
  dmi.board.name: H370M D3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnH370M-D3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH370MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: H370M-D3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861645/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  System with GeForce GT 520 failed to boot when nvidia-390 was
  installed

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  System booted OK with Nouveau driver.   I used Driver Manager to apply
  change of "Using NVIDIA driver metapackage from nvidia-
  driver-390(proprietary,tested)".   After the NVIDIA proprietary driver
  installation, system failed to boot.   All i get was a blank screen,
  with a blinking cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 12:02:15 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2020-02-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1864781/+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 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  zfs-initramfs fails with multiple rpool on separate disks

Status in grub2 package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  == Test Case ==
  1. On a multi disks setup, install Ubuntu with ZFS on disk 1
  2. Reboot and make sure everything works as expected
  3. Do a second installation and install Ubuntu with ZFS on disk 2
  4. Reboot

  * Expected Result *
  GRUB should display all the machines available and let the user select which 
installation to boot

  * Actual result *
  - Only one machine is listed
  - initramfs crashes because there are several pool with the same name but 
different IDs and import the pools by name
  - Same problem in the systemd generator which will try to import all the 
rpools.

  == Original Description ==

  I had an Ubuntu old installation that used a ZFS root, using the
  layout described in the ZFS on Linux docs. Consequently, the pool name
  for my Ubuntu installation was "rpool". I'm currently encountering an
  issue with that pool that only allows me to mount it read-only. So,
  I'd like to replicate the datasets from there to a new device.

  On the new device, I've set up a ZFS system using the Ubuntu 20.04
  daily installer (March 9, 2020). This setup creates a new pool named
  "rpool". So, with both devices inserted, I have two distinct pools
  each named "rpool", one of which will kernel panic if I try to mount
  it read-write.

  ZFS is fine with having multiple pools with the same name. In these
  cases, you use `zfs import` with the pool's GUID and give it a
  distinct pool name on import. However, the grub config for booting
  from ZFS doesn't appear to handle multiple pools with the same rpool
  name very well. Rather than using the pool's GUID, it uses the name,
  and as such, it's unable to boot properly when another pool with the
  name "rpool" is attached to the system.

  I think it'd be better if the config were written in such a way that
  `update-grub` generated boot config bound to whatever pool it found at
  the time of its invocation, and not start searching through all pools
  dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system
  with a ZFS root that boots just fine. But, the moment I attach the old
  pool, also named "rpool", I'm no longer able to boot up my system even
  though I haven't removed the good pool and I haven't re-run `update-
  grub`. Instead of booting, I'm thrown into the grub command line.

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

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

[Kernel-packages] [Bug 1902748] Re: ubuntu-seed / ubuntu-boot partition detection could be improved

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  ubuntu-seed / ubuntu-boot partition detection could be improved

Status in snapd:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  ubuntu-seed / ubuntu-boot partition detection could be improved

  Currently in the initrd, snapd-bootstrap searches for ubuntu-boot /
  ubuntu-seed partition by label or by UEFI variable that was set by sd-
  boot.

  sdboot uses devicepath UEFI protocol to establish MEDIA_DEVICE_PATH,
  HARDDRIVE_DEVICEPATH, GUID, Signature aka partuuid that was used to
  boot.

  
https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Protocol/DevicePath.h

  This is nice, but not unique enough. It would be nice if we were able
  to modify sd-boot stub to export something more specific that ideally
  maps to a sysfs path.

  For example PCI_DEVICE_PATH, SCSI_DEVICE_PATH, SATA_DEVICE_PATH,
  USB_DEVICE_PATH, NVME_NAMESPACE_DEVICE_PATH, SD_DEVICE_PATH,
  UFS_DEVICE_PATH, EMMC_DEVICE_PATH or some such.

  That way initrd would be able to resolve better which block device to
  key off.

  Given that EFI device handle is passed to the kernel, doesn't kernel
  also know where it came from? or not?

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1902748/+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