date:20230314

All autopkgtests for the newly accepted linux-meta-gcp-5.15 
(5.15.0.1031.38~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

lttng-modules/2.12.5-1ubuntu2~20.04.4 (arm64, amd64)
linux-gcp-5.15/5.15.0-1031.38~20.04.1 (arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs

2023-03-14 Thread Matthew Ruffell

Performing verification for Jammy.

I started a fresh Jammy VM, and installed 5.15.0-67-generic from
-updates.

I appended apparmor=0 to GRUB_CMDLINE_LINUX_DEFAULT, updated grub, and
rebooted.

>From there, I installed auditd, and stress-ng. I edited
/etc/audit/rules.d/audit.rules to include:

-a exit,always -F arch=b64 -S execve
-a exit,always -F arch=b32 -S execve

I then rebooted, and started stress-ng.

I checked the kmalloc-2k slab with:

$ watch "sudo cat /proc/meminfo | grep SUnreclaim"
$ watch "sudo cat /proc/slabinfo | grep kmalloc-2k"
$ sudo slabtop

Now, since this bug has been worked around by:

39cce16cfeed UBUNTU: SAUCE: LSM: Change Landlock from LSMBLOB_NEEDED to
LSMBLOB_NOT_NEEDED

in 5.15.0-53-generic, the kmalloc-k slab did not uncontrollably increase, but
that is okay, it is just the leak isn't reachable with landlock not using the
task_getsecid_obj hook.

This means this verification is more of a smoke test than checking root
cause.

I then enabled -proposed, and installed 5.15.0-68-generic, and rebooted.

I again ran stress-ng and checked the kmalloc-2k slab, and all was well, there
was no memory leak.

The core issue was fixed, but again, masked by the previous fix in 
5.15.0-53-generic. 

There was no smoke, and things ran as expected. Marking verified for
Jammy.

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

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

Title:
  Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in
  kmalloc-2k slabs

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

Bug description:
  Since updating to kernel 5.15.0-46-generic (package version
  5.15.0-46.49), all of our Ubuntu 22.04 LTS servers are leaking kernel
  memory; our first server with 8 GB of RAM just fatally OOMed, causing
  us to detect this. Inspection of OOM reports, /proc/meminfo, and
  /proc/slabinfo says that it's mostly going to unreclaimable kmalloc-2k
  slabs:

  Aug 23 12:51:11 cluster kernel: [361299.864757] Unreclaimable slab 
info:
  Aug 23 12:51:11 cluster kernel: [361299.864757] Name  
Used  Total
  [...]
  Aug 23 12:51:11 cluster kernel: [361299.864924] kmalloc-2k   
6676584KB6676596KB

  Most of our machines appear to be leaking slab memory at a rate of
  around 20 to 40 Mbytes/hour, with some machines leaking much faster;
  the champions are leaking kernel memory at 145 Mbytes/hour and 237
  Mbytes/hour.

  We aren't running any proprietary kernel modules and our only unusual
  kernel configuration is that we've disabled AppArmor with 'apparmor=0'
  on the kernel command line.

  /proc/version_signature:
  Ubuntu 5.15.0-46.49-generic 5.15.39

  Full kernel command line from the Dell R240 system that fatally OOMd:
  BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=3165564f-a2dd-4b39-935b-114f3e23ff54 ro console=ttyS0,115200 
console=tty0 apparmor=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987430/+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 2002757] Re: Dell precision 5560 screen can't back after suspend

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

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

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

Title:
  Dell precision 5560 screen can't back after suspend

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Kinetic:
  Expired

Bug description:
  The screen can't back on after suspend.

  Here is the kernel log error:

  [84090.414190] Asynchronous wait on fence 
:00:02.0:gnome-shell[2816]:1c469c timed out (hin  
t:intel_atomic_commit_ready [i915])
  [84090.414462] Asynchronous wait on fence 
:00:02.0:gnome-shell[2816]:1c469c timed out (hin  
t:intel_atomic_commit_ready [i915])
  [84094.705130] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in 
chrome [106889]
  [84094.705150] i915 :00:02.0: [drm] Resetting rcs0 for stopped heartbeat 
on rcs0
  [84094.705205] i915 :00:02.0: [drm] chrome[106889] context reset due to 
GPU hang
  [90008.508158] input: T8-L (AVRCP) as /devices/virtual/input/input50
  [90008.609265] input: T8-R (AVRCP) as /devices/virtual/input/input51

  There is a upstream bug reported the similar error.

  https://gitlab.freedesktop.org/drm/intel/-/issues/6757#note_1707377

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002757/+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 2002757] Re: Dell precision 5560 screen can't back after suspend

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

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

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

Title:
  Dell precision 5560 screen can't back after suspend

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Kinetic:
  Expired

Bug description:
  The screen can't back on after suspend.

  Here is the kernel log error:

  [84090.414190] Asynchronous wait on fence 
:00:02.0:gnome-shell[2816]:1c469c timed out (hin  
t:intel_atomic_commit_ready [i915])
  [84090.414462] Asynchronous wait on fence 
:00:02.0:gnome-shell[2816]:1c469c timed out (hin  
t:intel_atomic_commit_ready [i915])
  [84094.705130] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in 
chrome [106889]
  [84094.705150] i915 :00:02.0: [drm] Resetting rcs0 for stopped heartbeat 
on rcs0
  [84094.705205] i915 :00:02.0: [drm] chrome[106889] context reset due to 
GPU hang
  [90008.508158] input: T8-L (AVRCP) as /devices/virtual/input/input50
  [90008.609265] input: T8-R (AVRCP) as /devices/virtual/input/input51

  There is a upstream bug reported the similar error.

  https://gitlab.freedesktop.org/drm/intel/-/issues/6757#note_1707377

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-nvidia-tegra-5.15/5.15.0.1010.10~20.04.6)

All autopkgtests for the newly accepted linux-meta-nvidia-tegra-5.15 
(5.15.0.1010.10~20.04.6) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

lttng-modules/2.12.5-1ubuntu2~20.04.4 (arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2007219] Re: xfs: Preallocated ioend transactions cause deadlock due to log buffer exhaustion

2023-03-14 Thread Matthew Ruffell

Performing verification for Focal.

The customer in question installed 5.4.0-145-generic to their busy
production Kubernetes cluster, and have had no issues in the week and a
half the kernel has been running for. Before, they would suffer
deadlocks three or four times a day, so the kernel in -proposed fixes
the issue.

The customer is happy to mark this bug as verified for Focal.

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

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

Title:
  xfs: Preallocated ioend transactions cause deadlock due to log buffer
  exhaustion

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

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/2007219

  [Impact]

  A deadlock exists in the XFS filesystem that occurs when the XFS log
  buffer becomes completely exhausted.

  XFS maintains a circular ring buffer for the log, and it is a fixed
  size. To be able to create a transaction, you need to be able to
  reserve space on the log buffer.

  Certain ioend transactions, such as file append, can be preallocated
  for a negligible performance gain. This takes up space in the log
  buffer, and these preallocated ioends are placed on a workqueue,
  behind other ioends that are not preallocated.

  The deadlock occurs when the XFS log buffer is running low on space,
  and an ioend append transaction comes in. It is preallocated,
  consuming nearly all of the remaining XFS log buffer space, and is
  placed at the very end of the ioend workqueue. The kernel then takes a
  ioend from the top of the ioend workqeueue, creates a transaction,
  xfs_trans_alloc(), attempts to allocate space  for it,
  xfs_trans_reserve(), xfs_log_reserve(), and then waits in a while loop
  checking free space in the log, xlog_grant_head_check(),
  xlog_grant_head_wait().

  Since there is no space, the thread sleeps with schedule(). This
  happens with all ioend transactions, since the log is exhausted and
  I/O is not moving.

  Since I/O never moves, the thread is never woken up, and we get hung
  task timeouts, with system failure shortly afterward.

  An example hung task timeout is:

  INFO: task kworker/60:0:4002982 blocked for more than 360 seconds.
    Tainted: G   OE 5.4.0-137-generic #154-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  kworker/60:0D0 4002982  2 0x90004080
  Workqueue: xfs-conv/dm-3 xfs_end_io [xfs]
  Call Trace:
   __schedule+0x2e3/0x740
   schedule+0x42/0xb0
   xlog_grant_head_wait+0xb9/0x1e0 [xfs]
   xlog_grant_head_check+0xde/0x100 [xfs]
   xfs_log_reserve+0xc9/0x1e0 [xfs]
   xfs_trans_reserve+0x17a/0x1e0 [xfs]
   xfs_trans_alloc+0xda/0x170 [xfs]
   xfs_iomap_write_unwritten+0x128/0x2f0 [xfs]
   xfs_end_ioend+0x15b/0x1b0 [xfs]
   xfs_end_io+0xb1/0xe0 [xfs]
   process_one_work+0x1eb/0x3b0
   worker_thread+0x4d/0x400
   kthread+0x104/0x140
   ? process_one_work+0x3b0/0x3b0
   ? kthread_park+0x90/0x90
   ret_from_fork+0x1f/0x40

  There is no known workaround, other than to have a larger log buffer
  at filesystem creation, but even then, it only buys you time until you
  get high enough load to exhaust the log buffer.

  [Fix]

  This was fixed in 5.13-rc1 by the following patch:

  commit 7cd3099f4925d7c15887d1940ebd65acd66100f5
  Author: Brian Foster 
  Date:   Fri Apr 9 10:27:43 2021 -0700
  Subject: xfs: drop submit side trans alloc for append ioends
  Link: 
https://github.com/torvalds/linux/commit/7cd3099f4925d7c15887d1940ebd65acd66100f5

  The patch more or less removes all preallocated ioend transactions,
  and instead, when ioend appends are needed, they go to the standard
  workqueue like any other ioend, where transactions are allocated when
  they reach the top of the workqueue.

  The patch required some backporting for Focal. The changes to the
  patch itself is minimal and should be straightforward to read,
  however, the changes to the XFS ioend subsystem between 5.4 and
  5.13-rc1 were quite extreme, with a lot of refactoring taking place
  over very many commits.

  Additionally, the patch was part of a five part series, the first,
  fixes the deadlock, and the rest remove all the code to do with
  transaction preallocation.

  It is safe to leave the rest of the code in place. It will become dead
  code, but it will not be reachable, and not cause any risk of
  regression, due to ioend->io_append_trans always being NULL, and not
  entering into any of the if statements.

  [Testcase]

  There is currently no known testcase for this issue. The issue has
  only been seen in a customer production environment, running under
  heavy load. The issue has not been seen in a customer test
  environment, only production.

  The production workload is a busy Kubernetes cluster running
  containers

[Kernel-packages] [Bug 2011575] Re: Cursor used during log in after boot still on screen after log in on desktop

2023-03-14 Thread Daniel van Vugt

This is/was a common issue on AMD systems. I think the 5.14 OEM kernel
here is missing this fix:

  https://gitlab.gnome.org/GNOME/mutter/-/issues/1344#note_932943

But if it's still happening in later kernels then it might be related
to:

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6470

** Tags added: amdgpu cursor

** Package changed: xorg (Ubuntu) => linux-oem-5.14 (Ubuntu)

** Summary changed:

- Cursor used during log in after boot still on screen after log in on desktop
+ [amdgpu] Cursor used during log in after boot still on screen after log in on 
desktop

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1344
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1344

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6470
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6470

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

Title:
  [amdgpu] Cursor used during log in after boot still on screen after
  log in on desktop

Status in linux-oem-5.14 package in Ubuntu:
  New

Bug description:
  After booting up my laptop and logging in, the cursor that is used
  during the log in phase just freezes on the spot it last was after
  pressing the enter key to log in and stays there the whole usage time.
  It only disappears when I restart or shut down the laptop. It doesn't
  impair the usage of the desktop cursor, but stays on the screen, in
  front of every open window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1058.66-oem 5.14.21
  Uname: Linux 5.14.0-1058-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 14 13:53:12 2023
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1681] (rev 
d1) (prog-if 00 [VGA controller])
  MachineType: LENOVO 21CKCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1058-oem 
root=UUID=5579c05a-7872-4f21-8412-a225bea53a66 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2022
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET62W (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CKCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: ThinkPad
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.25:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1:
  dmi.product.family: ThinkPad P16s Gen 1
  dmi.product.name: 21CKCTO1WW
  dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1
  dmi.product.version: ThinkPad P16s Gen 1
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/2011575/+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 2011575] [NEW] Cursor used during log in after boot still on screen after log in on desktop

You have been subscribed to a public bug:

After booting up my laptop and logging in, the cursor that is used
during the log in phase just freezes on the spot it last was after
pressing the enter key to log in and stays there the whole usage time.
It only disappears when I restart or shut down the laptop. It doesn't
impair the usage of the desktop cursor, but stays on the screen, in
front of every open window.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.14.0-1058.66-oem 5.14.21
Uname: Linux 5.14.0-1058-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 14 13:53:12 2023
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1681] (rev 
d1) (prog-if 00 [VGA controller])
MachineType: LENOVO 21CKCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1058-oem 
root=UUID=5579c05a-7872-4f21-8412-a225bea53a66 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2022
dmi.bios.release: 1.32
dmi.bios.vendor: LENOVO
dmi.bios.version: R23ET62W (1.32 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CKCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: ThinkPad
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.25:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1:
dmi.product.family: ThinkPad P16s Gen 1
dmi.product.name: 21CKCTO1WW
dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1
dmi.product.version: ThinkPad P16s Gen 1
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 amdgpu apport-bug cursor focal ubuntu
-- 
Cursor used during log in after boot still on screen after log in on desktop
https://bugs.launchpad.net/bugs/2011575
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-oem-5.14 in Ubuntu.

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

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

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

lttng-modules/2.13.1-1ubuntu0.22.04.3 (amd64)
linux-ibm/5.15.0-1027.30 (amd64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2006370] Re: [nouveau] Terribly flicking and blicking HDMI-port display

2023-03-14 Thread Daniel van Vugt

Please try adding kernel parameter:

amd_iommu=off

Because I think this is basically bug 1965882 but we've never had it
reported on an AMD system before so don't yet know the solution.

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

Title:
[nouveau] Terribly flicking and blicking HDMI-port display

Status in linux package in Ubuntu:
Incomplete

Bug description:
Hi,
I have HP15 Gaming Pavilion bought 2-3 years ago.
I had Windows 10 before (not it is the second OS due to this bug [I can't use
Ubuntu with this bug]), and Win 10 has no problems.
No solution [that I found over the internet] worked.
I have to have at least two displays.
My connection technology:
PC HDMI output -> HDMI-VGA(+audio) transmitter -> LED 20' Display (external
monitor)
Win 10 have never had any problems with it (it has good drivers).
When I add any input to the second screen - it blinks and flickers so
terrible that I can see nothing - a white screen problem. If I do nothing - it
will turn to some picture in some time, but if I make any action at the second
monitor - flickering and the white screen problem appears again.
I think these are drivers. I tested the equipment in Win 10 after I found
this bug - and it works perfectly (so, the hardware is good).
It is a typical notebook and this bug is crucial. I use two monitors to type
codes and work on PC. I can't survive with just one monitor.
Right now when I am typing you this message the second monitor became white
again for quite a long time (I did nothing there).
I hope you will be able to fix this bug :)
Best wishes,
Alex,
Prague, Czech Republic, EU

PS: When typing this message I found another bug compared to MS Windows.
When making screenshots (Alt/Shift + Print Screen) - it makes perfect picture
even when you actually have the second monitor white all the time (so the
screenshot is not how it is).
I made an actual photo (and deleted some parts of the background not related
to the monitors/computer). You can see a white screen, but the screenshot shows
a "perfect world" with a perfect picture which is not how it is on the screen.
Windows, on the contrary, makes actual screenshots. And Win 10 test of this
monitor never have this white screen or any other monitor problems.
Moreover, when the monitors stops to be white for a second it depicts
different picture (more terrible image; it is disproportional, with font
heavily readable, but the screenshot functions shows an "ideal world" a user
can never see :)

I made this detailed description to help Ubuntu. I think the project
is great in concept, but poor in realization. Such bugs make it
impossible for users to use Ubuntu (who can work on just one monitor?
Who do not wish to make screenshots with what he/she actually sees on
the monitor [rather than modified images with the pictures users do
not actually see]?).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 6 19:45:32 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company TU117M [103c:87b1]
Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if
00 [VGA controller])
Subsystem: Hewlett-Packard Company Renoir [103c:87b1]
InstallationDate: Installed on 2023-02-04 (2 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic
root=UUID=30f188c5-d67f-4f68-ba6d-6995864ff95e ro quiet splash loglevel=3
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/18/2021
dmi.bios.release: 15.25
dmi.bios.vendor: AMI
dmi.bios.version: F.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 87B1
dmi.board.vendor: HP
dmi.board.version: 31.23
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 31.23
dmi.modalias:
dmi:bvnAMI:bvrF.25:bd08/18/2021:br15.25:efr31.23:svnHP:pnHPPavilionGamingLaptop15-ec1xxx:pvr:rvnHP:rn87B1:rvr31.23:cvnHP:ct10:cvrChassisVersion:sku1N3L2EA#ACB:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Gaming Laptop 15-ec1xxx
dmi.product.sku: 1N3L2EA#

[Kernel-packages] [Bug 2006370] Re: [nouveau] Terribly flicking and blicking HDMI-port display

2023-03-14 Thread Kai-Heng Feng

Please run `sudo ubuntu-drivers install` to install proprietary NVIDIA
driver.

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

Title:
[nouveau] Terribly flicking and blicking HDMI-port display

Status in linux package in Ubuntu:
Incomplete

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

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

lttng-modules/2.13.1-1ubuntu0.22.04.3 (amd64, arm64)
systemd/249.11-0ubuntu3.8 (arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2008050] Re: bmc virtual usb keyboard/mouse can't be detected when resting bmc

2023-03-14 Thread Zhanglei Mao

Summary for more testing results from zte: 
1. All works for 20.04.2-20.4.5 hwe-kernel(v5.8.0-41, v5.11.0-27, v5.13.0-30,  
v5.15.0-46), which we tested boot from iso.

2. It works too if we detach KVM (close browser)before reset BMC.

3. After reset BMC, to unbind "echo '1-7' | sudo tee
/sys/bus/usb/drivers/usb/unbind" virtual hub, open KVM can work too.

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

Title:
  bmc virtual usb keyboard/mouse can't be detected when resting bmc

Status in linux-hwe-5.4 package in Ubuntu:
  New

Bug description:
  In zte server, when reseting bmc or reload virtual keyboard/mouse
  driver in BMC, the keyboard/mouse on KVM will be hanged, it can resume
  working after reboot host OS which is Ubuntu 20.04 ga-kernel.

  This wouldn't happen on CentOS with kernel of 3.10.0-1160.317.x86_64,
  the keyboard/mouse of KVM keeps working when resting ibm.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-intel-iotg/5.15.0.1027.26)

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

lttng-modules/2.13.1-1ubuntu0.22.04.3 (amd64)
linux-intel-iotg/5.15.0-1027.32 (amd64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-intel-iotg

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-intel-iotg/5.15.0-1027.32)

All autopkgtests for the newly accepted linux-restricted-modules-intel-iotg 
(5.15.0-1027.32) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-intel-iotg

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently

2023-03-14 Thread Kai-Chuan Hsieh

reply #29

Would you like to try #7 and #8? it doesn't need to compile anything.

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

Title:
  Ubuntu 22.04 XPS 13 plus 9320  kernel 6.0 OEM and 5.19 breaks wifi
  frequently

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in oem-somerville-tentacool-meta package in Ubuntu:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in oem-somerville-tentacool-meta source package in Jammy:
  Confirmed
Status in linux-firmware source package in Kinetic:
  Fix Released
Status in oem-somerville-tentacool-meta source package in Kinetic:
  Invalid
Status in linux-firmware source package in Lunar:
  Fix Released
Status in oem-somerville-tentacool-meta source package in Lunar:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and
  -73 firmware are supported bug missing. On one user reported issue,
  this fixes WiFi stability on 5G band.

  [Fix]

  New upstreamed firmware revision fixes this issue.

  [Test Case]

  1. Boot hwe-5.19 kernel
  2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded
  3. Browse the web, usually takes between 1 and 5 minutes
  4. Networking will cut out

  [Where problems could occur]

  This affects only users need both backport-iwlwifi-dkms and hwe-5.19
  kernel on WiFi stability.

  [Other Info]

  While Kinetic and above have them all, only Jammy is nominated.

  == original bug report ==

  I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320).
  Recently I received some kernel updates, the 5.19 kernel used in 22.10
  and a 6.0 oem kernel. Both updates break wifi. It seems to only do so
  on newer 5.7 GHz access points.

  1. Boot latest 6.0 oem kernel
  2. Browse the web, usually takes between 1 and 5 minutes.
  3. Networking will cut out.

  Disabling networking and starting again will fix it until it happens
  again in a few minutes. This will repeat indefinitely, essentially
  making wireless useless.

  The attached dmesg log reliably shows up when it fails, showing
  iwlwifi failing and a (network?) hardware reset request.

  It witnessed this happen months ago on 22.10, which led me to using
  the Dell stock 22.04 image. But it seems even the newer OEM kernel is
  affected.

  A workaround is to select the older 5.15 kernel in grub. I find on
  this laptop, one must hit escape precisely 1 second after seeing the
  Dell logo on boot. Alternatively one could edit /etc/grub/default and
  set a longer timeout.

  Let me know if this bug report would be better to go to Dell as a
  support request instead.

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


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

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

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

systemd/249.11-0ubuntu3.8 (arm64)
lttng-modules/2.13.1-1ubuntu0.22.04.3 (arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-oracle/5.4.0-1097.106)

All autopkgtests for the newly accepted linux-restricted-modules-oracle 
(5.4.0-1097.106) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386, armhf)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-oracle

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried

2023-03-14 Thread Mauricio Faria de Oliveira

The fix/commit is applied in v5.12, thus available on Jammy
(v5.15-based).

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4ceddce55eb35d15b0f87f5dcf6f0058fd15d3a4


~/git/linux$ git describe --contains 4ceddce55eb35d15b0f87f5dcf6f0058fd15d3a4
v5.12-rc1-dontuse~7^2~13


** Also affects: parted (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: udev (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

** Also affects: systemd (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: snapd (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

** Changed in: parted (Ubuntu Jammy)
   Status: New => Invalid

** No longer affects: parted (Ubuntu Jammy)

** No longer affects: snapd (Ubuntu Jammy)

** No longer affects: udev (Ubuntu Jammy)

** No longer affects: systemd (Ubuntu 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/1856871

Title:
  i/o error if next unused loop device is queried

Status in linux package in Ubuntu:
  Fix Released
Status in parted package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  This is reproducible in Bionic and late.

  Here's an example running 'focal':

  $ lsb_release -cs
  focal

  $ uname -r
  5.3.0-24-generic

  The error is:
  blk_update_request: I/O error, dev loop2, sector 0

  and on more recent kernel:

  kernel: [18135.185709] blk_update_request: I/O error, dev loop18,
  sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0

  
  How to trigger it:
  $ sosreport -o block

  or more precisely the cmd causing the situation inside the block plugin:
  $ parted -s $(losetup -f) unit s print

  https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52

  but if I run it on the next next unused loop device, in this case
  /dev/loop3 (which is also unused), no errors.

  While I agree that sosreport shouldn't query unused loop devices,
  there is definitely something going on with the next unused loop
  device.

  What is differentiate loop2 and loop3 and any other unused ones ?

  3 things so far I have noticed:
  * loop2 is the next unused loop device (losetup -f)
  * A reboot is needed (if some loop modification (snap install, mount loop, 
...) has been made at runtime
  * I have also noticed that loop2 (or whatever the next unused one is) have 
some stat as oppose to other unused loop devices. The stat exist already right 
after the system boot for the next unused loop device.

  /sys/block/loop2/stat
  ::
  2 0 10 0 1 0 0 0 0 0 0

  2  = number of read I/Os processed
  10 = number of sectors read
  1  = number of write I/Os processed

  Explanation of each column:
  https://www.kernel.org/doc/html/latest/block/stat.html

  while /dev/loop3 doesn't

  /sys/block/loop3/stat
  ::
  0 0 0 0 0 0 0 0 0 0 0

  Which tells me that something during the boot process most likely
  acquired (on purpose or not) the next unused loop and possibly didn't
  released it well enough.

  If loop2 is generating errors, and I install a snap, the snap squashfs
  will take loop2, making loop3 the next unused loop device.

  If I query loop3 with 'parted' right after, no errors.

  If I reboot, and query loop3 again, then no I'll have an error.

  To triggers the errors it need to be after a reboot and it only impact
  the first unused loop device available (losetup -f).

  This was tested with focal/systemd whic his very close to latest
  upstream code.

  This has been test with latest v5.5 mainline kernel as well.

  For now, I don't think it's a kernel problem, I'm more thinking of a
  userspace misbehaviour dealing with loop device (or block device) at
  boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856871/+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 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently

2023-03-14 Thread Loic Martel

Reply #28

I am sorry, but this is my daily workstation (I'm Freelancer) and I
don't want to take the risk to break it for the next days (lot of work
to do! :) )... :/

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

Title:
  Ubuntu 22.04 XPS 13 plus 9320  kernel 6.0 OEM and 5.19 breaks wifi
  frequently

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in oem-somerville-tentacool-meta package in Ubuntu:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in oem-somerville-tentacool-meta source package in Jammy:
  Confirmed
Status in linux-firmware source package in Kinetic:
  Fix Released
Status in oem-somerville-tentacool-meta source package in Kinetic:
  Invalid
Status in linux-firmware source package in Lunar:
  Fix Released
Status in oem-somerville-tentacool-meta source package in Lunar:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and
  -73 firmware are supported bug missing. On one user reported issue,
  this fixes WiFi stability on 5G band.

  [Fix]

  New upstreamed firmware revision fixes this issue.

  [Test Case]

  1. Boot hwe-5.19 kernel
  2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded
  3. Browse the web, usually takes between 1 and 5 minutes
  4. Networking will cut out

  [Where problems could occur]

  This affects only users need both backport-iwlwifi-dkms and hwe-5.19
  kernel on WiFi stability.

  [Other Info]

  While Kinetic and above have them all, only Jammy is nominated.

  == original bug report ==

  I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320).
  Recently I received some kernel updates, the 5.19 kernel used in 22.10
  and a 6.0 oem kernel. Both updates break wifi. It seems to only do so
  on newer 5.7 GHz access points.

  1. Boot latest 6.0 oem kernel
  2. Browse the web, usually takes between 1 and 5 minutes.
  3. Networking will cut out.

  Disabling networking and starting again will fix it until it happens
  again in a few minutes. This will repeat indefinitely, essentially
  making wireless useless.

  The attached dmesg log reliably shows up when it fails, showing
  iwlwifi failing and a (network?) hardware reset request.

  It witnessed this happen months ago on 22.10, which led me to using
  the Dell stock 22.04 image. But it seems even the newer OEM kernel is
  affected.

  A workaround is to select the older 5.15 kernel in grub. I find on
  this laptop, one must hit escape precisely 1 second after seeing the
  Dell logo on boot. Alternatively one could edit /etc/grub/default and
  set a longer timeout.

  Let me know if this bug report would be better to go to Dell as a
  support request instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007875/+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 2006370] Re: [nouveau] Terribly flicking and blicking HDMI-port display

$ ubuntu-drivers devices
== /sys/devices/pci:00/:00:01.1/:01:00.0 ==
modalias : pci:v10DEd1F99sv103Csd87B1bc03sc00i00
vendor   : NVIDIA Corporation
model: TU117M
driver   : nvidia-driver-525-open - distro non-free recommended
driver   : nvidia-driver-510 - distro non-free
driver   : nvidia-driver-450-server - distro non-free
driver   : nvidia-driver-470 - distro non-free
driver   : nvidia-driver-515 - distro non-free
driver   : nvidia-driver-525-server - distro non-free
driver   : nvidia-driver-525 - distro non-free
driver   : nvidia-driver-515-server - distro non-free
driver   : nvidia-driver-470-server - distro non-free
driver   : nvidia-driver-515-open - distro non-free
driver   : xserver-xorg-video-nouveau - distro free builtin

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

Title:
  [nouveau] Terribly flicking and blicking HDMI-port display

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I have HP15 Gaming Pavilion bought 2-3 years ago. 
  I had Windows 10 before (not it is the second OS due to this bug [I can't use 
Ubuntu with this bug]), and Win 10 has no problems. 
  No solution [that I found over the internet] worked. 
  I have to have at least two displays. 
  My connection technology:
  PC HDMI output -> HDMI-VGA(+audio) transmitter -> LED 20' Display (external 
monitor)
  Win 10 have never had any problems with it (it has good drivers). 
  When I add any input to the second screen - it blinks and flickers so 
terrible that I can see nothing - a white screen problem. If I do nothing - it 
will turn to some picture in some time, but if I make any action at the second 
monitor - flickering and the white screen problem appears again. 
  I think these are drivers. I tested the equipment in Win 10 after I found 
this bug - and it works perfectly (so, the hardware is good). 
  It is a typical notebook and this bug is crucial. I use two monitors to type 
codes and work on PC. I can't survive with just one monitor. 
  Right now when I am typing you this message the second monitor became white 
again for quite a long time (I did nothing there). 
  I hope you will be able to fix this bug :)
  Best wishes,
  Alex,
  Prague, Czech Republic, EU

  
  PS: When typing this message I found another bug compared to MS Windows. 
  When making screenshots (Alt/Shift + Print Screen) - it makes perfect picture 
even when you actually have the second monitor white all the time (so the 
screenshot is not how it is).
  I made an actual photo (and deleted some parts of the background not related 
to the monitors/computer). You can see a white screen, but the screenshot shows 
a "perfect world" with a perfect picture which is not how it is on the screen. 
  Windows, on the contrary, makes actual screenshots. And Win 10 test of this 
monitor never have this white screen or any other monitor problems. 
  Moreover, when the monitors stops to be white for a second it depicts 
different picture (more terrible image; it is disproportional, with font 
heavily readable, but the screenshot functions shows an "ideal world" a user 
can never see :)

  I made this detailed description to help Ubuntu. I think the project
  is great in concept, but poor in realization. Such bugs make it
  impossible for users to use Ubuntu (who can work on just one monitor?
  Who do not wish to make screenshots with what he/she actually sees on
  the monitor [rather than modified images with the pictures users do
  not actually see]?).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb  6 19:45:32 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU117M [103c:87b1]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:87b1]
  InstallationDate: Installed on 2023-02-04 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=30f188c5-d67f-4f68-ba6d-6995864ff95e ro quiet splash loglevel=3 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2021
  dmi.bios.release: 15.25
  dmi

[Kernel-packages] [Bug 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently

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

** Changed in: oem-somerville-tentacool-meta (Ubuntu Jammy)
   Status: New => Confirmed

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

Title:
  Ubuntu 22.04 XPS 13 plus 9320  kernel 6.0 OEM and 5.19 breaks wifi
  frequently

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in oem-somerville-tentacool-meta package in Ubuntu:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in oem-somerville-tentacool-meta source package in Jammy:
  Confirmed
Status in linux-firmware source package in Kinetic:
  Fix Released
Status in oem-somerville-tentacool-meta source package in Kinetic:
  Invalid
Status in linux-firmware source package in Lunar:
  Fix Released
Status in oem-somerville-tentacool-meta source package in Lunar:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and
  -73 firmware are supported bug missing. On one user reported issue,
  this fixes WiFi stability on 5G band.

  [Fix]

  New upstreamed firmware revision fixes this issue.

  [Test Case]

  1. Boot hwe-5.19 kernel
  2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded
  3. Browse the web, usually takes between 1 and 5 minutes
  4. Networking will cut out

  [Where problems could occur]

  This affects only users need both backport-iwlwifi-dkms and hwe-5.19
  kernel on WiFi stability.

  [Other Info]

  While Kinetic and above have them all, only Jammy is nominated.

  == original bug report ==

  I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320).
  Recently I received some kernel updates, the 5.19 kernel used in 22.10
  and a 6.0 oem kernel. Both updates break wifi. It seems to only do so
  on newer 5.7 GHz access points.

  1. Boot latest 6.0 oem kernel
  2. Browse the web, usually takes between 1 and 5 minutes.
  3. Networking will cut out.

  Disabling networking and starting again will fix it until it happens
  again in a few minutes. This will repeat indefinitely, essentially
  making wireless useless.

  The attached dmesg log reliably shows up when it fails, showing
  iwlwifi failing and a (network?) hardware reset request.

  It witnessed this happen months ago on 22.10, which led me to using
  the Dell stock 22.04 image. But it seems even the newer OEM kernel is
  affected.

  A workaround is to select the older 5.15 kernel in grub. I find on
  this laptop, one must hit escape precisely 1 second after seeing the
  Dell logo on boot. Alternatively one could edit /etc/grub/default and
  set a longer timeout.

  Let me know if this bug report would be better to go to Dell as a
  support request instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007875/+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 2006370] Re: [nouveau] Terribly flicking and blicking HDMI-port display

My graphic version:
Version: F.25
Version:  
Version: 31.23
Version: Chassis Version
SBDS Version: 3.1
Version: AMD Ryzen 7 4800H with Radeon Graphics 
Firmware Version: Unknown
Firmware Version: Unknown
My laptop version: Product Name: HP Pavilion Gaming Laptop 15-ec1xxx [written 
on laptop: Model: 15ec-1032ur]
Family: 103C_5335KV HP Pavilion

The next modifications are not from Ubuntu commands, but from the basic info on 
site:
Motherboard HP 87B2
Video: NVIDIA GeForce GTX 1650

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

Title:
  [nouveau] Terribly flicking and blicking HDMI-port display

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I have HP15 Gaming Pavilion bought 2-3 years ago. 
  I had Windows 10 before (not it is the second OS due to this bug [I can't use 
Ubuntu with this bug]), and Win 10 has no problems. 
  No solution [that I found over the internet] worked. 
  I have to have at least two displays. 
  My connection technology:
  PC HDMI output -> HDMI-VGA(+audio) transmitter -> LED 20' Display (external 
monitor)
  Win 10 have never had any problems with it (it has good drivers). 
  When I add any input to the second screen - it blinks and flickers so 
terrible that I can see nothing - a white screen problem. If I do nothing - it 
will turn to some picture in some time, but if I make any action at the second 
monitor - flickering and the white screen problem appears again. 
  I think these are drivers. I tested the equipment in Win 10 after I found 
this bug - and it works perfectly (so, the hardware is good). 
  It is a typical notebook and this bug is crucial. I use two monitors to type 
codes and work on PC. I can't survive with just one monitor. 
  Right now when I am typing you this message the second monitor became white 
again for quite a long time (I did nothing there). 
  I hope you will be able to fix this bug :)
  Best wishes,
  Alex,
  Prague, Czech Republic, EU

  
  PS: When typing this message I found another bug compared to MS Windows. 
  When making screenshots (Alt/Shift + Print Screen) - it makes perfect picture 
even when you actually have the second monitor white all the time (so the 
screenshot is not how it is).
  I made an actual photo (and deleted some parts of the background not related 
to the monitors/computer). You can see a white screen, but the screenshot shows 
a "perfect world" with a perfect picture which is not how it is on the screen. 
  Windows, on the contrary, makes actual screenshots. And Win 10 test of this 
monitor never have this white screen or any other monitor problems. 
  Moreover, when the monitors stops to be white for a second it depicts 
different picture (more terrible image; it is disproportional, with font 
heavily readable, but the screenshot functions shows an "ideal world" a user 
can never see :)

  I made this detailed description to help Ubuntu. I think the project
  is great in concept, but poor in realization. Such bugs make it
  impossible for users to use Ubuntu (who can work on just one monitor?
  Who do not wish to make screenshots with what he/she actually sees on
  the monitor [rather than modified images with the pictures users do
  not actually see]?).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb  6 19:45:32 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU117M [103c:87b1]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:87b1]
  InstallationDate: Installed on 2023-02-04 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=30f188c5-d67f-4f68-ba6d-6995864ff95e ro quiet splash loglevel=3 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2021
  dmi.bios.release: 15.25
  dmi.bios.vendor: AMI
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 87B1
  dmi.board.vendor: HP
  dmi.board.version: 31.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi

[Kernel-packages] [Bug 2006994] Re: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep

2023-03-14 Thread isotope

And it is happening again...

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

Title:
Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on
after waking up from sleep

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on
after waking up from sleep

Scenario:

Fresh and clean Ubuntu 22.10 install on Latitude 7390, requiring
nomodeset kernel boot option to be added in GRUB at boot time when
booting from USB stick. This can be achieved by following instructions
from here: https://www.dell.com/support/kbdoc/en-uk/000123893/manual-
nomodeset-kernel-boot-line-option-for-linux-booting

Then, nomodeset needs to be permanently added to /etc/default/grub
Followed instructions from
https://askubuntu.com/questions/38780/how-do-i-set-nomodeset-after-ive-already-installed-ubuntu

If nomodeset is not added, Dell Latitude 7390 will freeze at one point
or another, either before reaching the Gnome desktop, either little
after. This is the case with both, installing Ubuntu 22.10 from Live
USB and running Ubuntu 22.10 after install the install (and having the
USB stick disconnected).

The issue after having Ubuntu 22.10 installed on Dell Latitude 7390 and
having nomodeset permanently added to GRUB for each boot is:

If by chance the system goes into sleep, after waking up, there is a
totally pitch-black screen; nothing shows up, no screen backlight
either. However, caps-lock works and I am able to log in to the system
via ssh and can see the system is up an running well. I can even issue
a request to send the system to sleep by “sudo systemctl suspend” and
then wake the the system up several times without loosing ssh access,
however, the screen will remain pitch-black.

Other tries to troubleshoot and see if the system can be brought back with a
working display (while nomodeset kernel option is being used):

1. sudo systemctl suspend -i
>>> this will result in an unusable system after waking up, again, with a
pitch-black screen; moreover, the caps-lock would not work, the keyboard
backlight won’t work, ssh won’t work; I need a hard reset to get the system
back up.

2. start the system in single user mode by inserting “single” in GRUB at boot
time;
>>> the system will be unusable after waking up, same as in try 1.

3. after a normal boot into the GNOME desktop with kernel nomodeset
option and investigating the dmesg for any acpi, no error could be
found.

Tried to read up on other possible solutions, while stumbled upon the ubuntu
wiki page below:
https://wiki.ubuntu.com/UnderstandingSuspend
Unfortunately, to not much help so far.

Other notes:
N1. All the above were done by having the latest BIOS v1.30.0
N2. This laptop came with Windows 10 Pro which works fine: goes into suspend
and wakes up fine, with working screen and display.

N3. Dell Latitude 7390 was released on 15 Feb 2018 ( source:
https://www.laptoparena.net/dell/notebook-dell-latitude-7390-n025l739013emea-black-12984
) and the user manual states it has support for Ubuntu. Therefore, other older
and major Ubuntu versions were given a try, along with a new version of Fedora:
N3.1 – Ubuntu 22.04
N3.2 – Ubuntu 18.04.6
N3.3 – Ubuntu 16.04.7
N3.4 – Fedora-Workstation-Live-x86_64-37-1.7
Each of the above will freeze at one point or another if nomodeset is not
used, except the Ubuntu 18.04.6 and Ubuntu 16.04.7 which will run well and
install well from the USB Live stick and will also run fine after the install,
until the system goes into sleep, after which, when the system is awake, the
screen is black and will have nothing displayed.

Any advice will be appreciated. Thank you!

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-31-generic 5.19.0-31.32
ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
Uname: Linux 5.19.0-31-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tuser 2832 F wireplumber
/dev/snd/seq:tuser 2829 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 11 13:37:59 2023
InstallationDate: Installed on 2023-01-15 (27 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated
Webcam_HD
Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 7390
ProcEnviron:
LANGUA

[Kernel-packages] [Bug 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently

2023-03-14 Thread Loic Martel

Reply #28

I am sorry, but this is my daily workstation (I'm Freelancer) and I
don't want to take the risk to break it for the next days (lot of work
to do! :) )... :/

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

Title:
  Ubuntu 22.04 XPS 13 plus 9320  kernel 6.0 OEM and 5.19 breaks wifi
  frequently

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in oem-somerville-tentacool-meta package in Ubuntu:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in oem-somerville-tentacool-meta source package in Jammy:
  Confirmed
Status in linux-firmware source package in Kinetic:
  Fix Released
Status in oem-somerville-tentacool-meta source package in Kinetic:
  Invalid
Status in linux-firmware source package in Lunar:
  Fix Released
Status in oem-somerville-tentacool-meta source package in Lunar:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and
  -73 firmware are supported bug missing. On one user reported issue,
  this fixes WiFi stability on 5G band.

  [Fix]

  New upstreamed firmware revision fixes this issue.

  [Test Case]

  1. Boot hwe-5.19 kernel
  2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded
  3. Browse the web, usually takes between 1 and 5 minutes
  4. Networking will cut out

  [Where problems could occur]

  This affects only users need both backport-iwlwifi-dkms and hwe-5.19
  kernel on WiFi stability.

  [Other Info]

  While Kinetic and above have them all, only Jammy is nominated.

  == original bug report ==

  I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320).
  Recently I received some kernel updates, the 5.19 kernel used in 22.10
  and a 6.0 oem kernel. Both updates break wifi. It seems to only do so
  on newer 5.7 GHz access points.

  1. Boot latest 6.0 oem kernel
  2. Browse the web, usually takes between 1 and 5 minutes.
  3. Networking will cut out.

  Disabling networking and starting again will fix it until it happens
  again in a few minutes. This will repeat indefinitely, essentially
  making wireless useless.

  The attached dmesg log reliably shows up when it fails, showing
  iwlwifi failing and a (network?) hardware reset request.

  It witnessed this happen months ago on 22.10, which led me to using
  the Dell stock 22.04 image. But it seems even the newer OEM kernel is
  affected.

  A workaround is to select the older 5.15 kernel in grub. I find on
  this laptop, one must hit escape precisely 1 second after seeing the
  Dell logo on boot. Alternatively one could edit /etc/grub/default and
  set a longer timeout.

  Let me know if this bug report would be better to go to Dell as a
  support request instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007875/+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 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

2023-03-14 Thread Andrew Reis

I've had this issue within AWS using:
linux-aws: 5.15.0-1031
linux-image-5.15.0-1031-aws

Problem goes away with linux-image-5.15.0-1030-aws

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

Title:
  NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating on the kernel 
  5.4.0-144.161 at Ubuntu 18 and 
  5.15.0-67.74 at Ubuntu 20, 
  we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our 
NFS servers.

  All clients are extremely slow when it comes to access to the NFS
  resources.

  Restart and use older kernel, fixed the problem.
  Ubuntu 18 5.4.0-139-generic
  Ubuntu 20 5.15.0-60-Generic
  I don't have a NFS problem with this kernel.

  Problem came with the last releas on March 3rd, 2023
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:00 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic 
root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto 
elevator=noop
  ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-67-generic N/A
   linux-backports-modules-5.15.0-67-generic  N/A
   linux-firmware 1.187.36
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.15.0-67-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:03 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic 
root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto 
elevator=noop
  ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-43-generic N/A
   linux-backports-modules-5.0.0-43-generic  N/A
   linux-firmware1.173.21
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 5.0.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/12/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNon

[Kernel-packages] [Bug 2006370] Re: [nouveau] Terribly flicking and blicking HDMI-port display

I am sorry for some delay in reply.
I have to use Windows machine due to this bug, and so I was not often in 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/2006370

Title:
[nouveau] Terribly flicking and blicking HDMI-port display

Status in linux package in Ubuntu:
Incomplete

[Kernel-packages] [Bug 2006370] Re: [nouveau] Terribly flicking and blicking HDMI-port display