[Kernel-packages] [Bug 2086460] Re: Deivce drivers aren't loaded, no wifi, no HDMI monitor

[Philip Cox]

It sounds like you have resolved this.  I will close this ticket.

** Changed in: linux-signed-aws (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

** Changed in: linux-signed-aws (Ubuntu)
   Status: New => Invalid

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

Title:
  Deivce drivers aren't loaded, no wifi, no HDMI monitor

Status in linux-signed-aws package in Ubuntu:
  Invalid

Bug description:
  Reverting to the previous kernel restored functionality.
  UEFI Safe mode is OFF

  xrandr -q says:
  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 4096 x 4096
  None-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 0mm x 0mm
 1920x1080 60.00*+

  (no HDMI device, no alternative resolutions, "None" is strange)

  nmcli dev says:
  DEVICE TYPE  STATE   CONNECTION 
  enp0s31f6  ethernet  connected   Wired connection 1 
  lo loopback  connected (externally)  lo

  (no wifi device)

  I'm happy to provide further information.  Just let me know what you
  need.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-1017-aws 6.8.0-1017.18
  ProcVersionSignature: Ubuntu 6.8.0-1017.18-aws 6.8.12
  Uname: Linux 6.8.0-1017-aws x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Nov  1 09:53:48 2024
  InstallationDate: Installed on 2024-09-20 (42 days ago)
  InstallationMedia: Kubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827)
  SourcePackage: linux-signed-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws/+bug/2086460/+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 2079491] Re: Fix handling of mixed VGA and non-VGA class PCI GPUs

[Philip Cox]

The fix has been applied as part of the latest stable update:

https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/noble/commit/?h=master-
next&id=e415bd51ba189f08f9d95e062d7ef655c731e83f

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

** Changed in: linux (Ubuntu Noble)
   Status: New => Fix Committed

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

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

Title:
  Fix handling of mixed VGA and non-VGA class PCI GPUs

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

Bug description:
  This patch needs to be applied to avoid a segfault when VGA and non-VGA PCI 
class GPUs are mixed in a system and the non-VGA GPU is the primary:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b49420d6a1aeb399e5b107fc6eb8584d0860fbd7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2079491/+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 2076217] Re: booting an 24.10 or 24.04 ec2 instance with SEV-SNP enabled hangs sometimes

[Philip Cox]

I have a bit of an update on the sev-snp delay in booting.  I am still trying 
to put everything together, and I will finalise everything on Monday after I  
finish going through all of the logs I generated today.  


I traced through apic/x2apic call stack and I've been digging through the 
kernel code, and I suspect I know the issue.   

I think it comes down to a mixture of SNP-SEV support not being fully
available in the kernel, and in the hypervisor with how it handles the
APIC (the interrupt controller).  Commit 1dfe571c12cf introduced the
kernel support for kvm handling of  SEV-SNP.   This was not added to the
kernel until kernel version 6.11.  I need to dig through the kvm source
to see how it handles the apix/x2apic with SNP-SEV still.

Without the support in the kernel and hypervisor, it seems that the
behaviour is somewhat undefined and relies on what is happening in the
other guest VMs on the machine.   This will explain why the pause does
not hit every time you boot, but once it does hit, it reproduces every
time.


One thing I have noticed is that when a VM f first started, it does not always  
happen.  After a several reboots it usually does happen.  Once it has happened 
once though, it happens every reboot after that.


  I noticed GCP supports SEV-SNP, so I created an instance there, and 
installed the AWS kernel.  I then installed the GCP kernel on the AWS instance. 
 The AWS instance is hitting the pause with the GCP, and the AWS kernel, while 
the GCP instance has not hit it after about 100 reboots using the AWS kernel..  

This makes me think it is the hypervisor rather than the kernel causing
the issue.

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

Title:
  booting an 24.10 or 24.04 ec2 instance with SEV-SNP enabled hangs
  sometimes

Status in cloud-images:
  New
Status in linux-aws package in Ubuntu:
  In Progress

Bug description:
  I'm trying to test an EC2 instance with SEV-SNP enabled. But the boot
  process hangs at:

  [snipped]
  [0.609079] printk: legacy console [ttyS0] enabled
  [5.405931] ACPI: Core revision 20230628
  [5.430448] clocksource: hpet: mask: 0x max_cycles: 0x, 
max_idle_ns: 30580167144 ns
  [5.473066] APIC: Switch to symmetric I/O mode setup

  
  Steps to reproduce are:

  $ AWS_DEFAULT_REGION=eu-west-1 aws ec2 run-instances --image-id
  ami-005a44922e2ffd1fa --instance-type m6a.large --cpu-options
  AmdSevSnp=enabled --key-name toabctl --tag-specifications
  'ResourceType=instance,Tags=[{Key=Name,Value=toabctl-2410-sevsnp-
  testing}]'

  The AMI ami-005a44922e2ffd1fa is ubuntu/images-testing/hvm-ssd-
  gp3/ubuntu-oracular-daily-amd64-server-20240716 and does contain
  6.8.0-1008-aws .

  Attached is the full output from the EC2 serial console.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2076217/+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 2085159] Re: [AWS] Fix interrupt mappings which are set to a bad default after certain ENI operations

[Philip Cox]

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

** Changed in: linux-aws (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Changed in: linux-aws (Ubuntu Noble)
   Status: In Progress => Fix Committed

** Changed in: linux-aws (Ubuntu Oracular)
   Status: In Progress => Fix Committed

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

Title:
  [AWS]  Fix interrupt mappings which are set to a bad default after
  certain ENI operations

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Focal:
  Fix Committed
Status in linux-aws source package in Jammy:
  Fix Committed
Status in linux-aws source package in Noble:
  Fix Committed
Status in linux-aws source package in Oracular:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  Interrupt mapping is set to a bad default after certain ENI operations

  After using ethtool to update the (rx) ring buffer settings on an ENI,
  the interrupt CPU affinity for all tx-rx queues is reset to a bad
  default - CPU 0-31 - even if the ENI is on a different CPU socket
  (NUMA node). Another operation that causes the interrupt mapping to be
  reset to CPU 0-31 is moving an interface to a network namespace.

  [Fix]

  ENA driver version 2.12.3g. They mentioned that this commit in the ENA
  code looks like it addresses the bug: https://github.com/amzn/amzn-
  drivers/commit/ed7754cdf6ca0d4fb3d76906abc17718cc3ffa23

  It's included starting in driver version 2.12.0.

  I have back ported the patch from the AWS OOT driver, as well as any
  existing prerequisites needed.

  [Test Plan]

  I have tested this, as has AWS.

  [Where problems could occur]

  As this is an Ubuntu Sauce patch, if these changes make their was into
  the stable trees, or any patches touching this area of code,  they may
  cause merge conflicts, or changes in behaviour which are unexpected.

  
  [Other]
  SF# f00396266

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2085159/+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 2085159] Re: [AWS] Fix interrupt mappings which are set to a bad default after certain ENI operations

[Philip Cox]

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

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

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

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

** Changed in: linux-aws (Ubuntu)
   Status: In Progress => New

** Changed in: linux-aws (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux-aws (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-aws (Ubuntu Noble)
   Status: New => In Progress

** Changed in: linux-aws (Ubuntu Oracular)
   Status: New => In Progress

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

Title:
  [AWS]  Fix interrupt mappings which are set to a bad default after
  certain ENI operations

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Focal:
  In Progress
Status in linux-aws source package in Jammy:
  In Progress
Status in linux-aws source package in Noble:
  In Progress
Status in linux-aws source package in Oracular:
  In Progress

Bug description:
  SRU Justification:

  [Impact]
  Interrupt mapping is set to a bad default after certain ENI operations

  After using ethtool to update the (rx) ring buffer settings on an ENI,
  the interrupt CPU affinity for all tx-rx queues is reset to a bad
  default - CPU 0-31 - even if the ENI is on a different CPU socket
  (NUMA node). Another operation that causes the interrupt mapping to be
  reset to CPU 0-31 is moving an interface to a network namespace.

  [Fix]

  ENA driver version 2.12.3g. They mentioned that this commit in the ENA
  code looks like it addresses the bug: https://github.com/amzn/amzn-
  drivers/commit/ed7754cdf6ca0d4fb3d76906abc17718cc3ffa23

  It's included starting in driver version 2.12.0.

  I have back ported the patch from the AWS OOT driver, as well as any
  existing prerequisites needed.

  [Test Plan]

  I have tested this, as has AWS.

  [Where problems could occur]

  As this is an Ubuntu Sauce patch, if these changes make their was into
  the stable trees, or any patches touching this area of code,  they may
  cause merge conflicts, or changes in behaviour which are unexpected.

  
  [Other]
  SF# f00396266

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2085159/+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 2085159] [NEW] [AWS] Fix interrupt mappings which are set to a bad default after certain ENI operations

[Philip Cox]

Public bug reported:

SRU Justification:

[Impact]
Interrupt mapping is set to a bad default after certain ENI operations

After using ethtool to update the (rx) ring buffer settings on an ENI,
the interrupt CPU affinity for all tx-rx queues is reset to a bad
default - CPU 0-31 - even if the ENI is on a different CPU socket (NUMA
node). Another operation that causes the interrupt mapping to be reset
to CPU 0-31 is moving an interface to a network namespace.

[Fix]

ENA driver version 2.12.3g. They mentioned that this commit in the ENA
code looks like it addresses the bug: https://github.com/amzn/amzn-
drivers/commit/ed7754cdf6ca0d4fb3d76906abc17718cc3ffa23

It's included starting in driver version 2.12.0.

I have back ported the patch from the AWS OOT driver, as well as any
existing prerequisites needed.

[Test Plan]

I have tested this, as has AWS.

[Where problems could occur]

As this is an Ubuntu Sauce patch, if these changes make their was into
the stable trees, or any patches touching this area of code,  they may
cause merge conflicts, or changes in behaviour which are unexpected.


[Other]
SF# f00396266

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Assignee: Philip Cox (philcox)
 Status: In Progress

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

Title:
  [AWS]  Fix interrupt mappings which are set to a bad default after
  certain ENI operations

Status in linux-aws package in Ubuntu:
  In Progress

Bug description:
  SRU Justification:

  [Impact]
  Interrupt mapping is set to a bad default after certain ENI operations

  After using ethtool to update the (rx) ring buffer settings on an ENI,
  the interrupt CPU affinity for all tx-rx queues is reset to a bad
  default - CPU 0-31 - even if the ENI is on a different CPU socket
  (NUMA node). Another operation that causes the interrupt mapping to be
  reset to CPU 0-31 is moving an interface to a network namespace.

  [Fix]

  ENA driver version 2.12.3g. They mentioned that this commit in the ENA
  code looks like it addresses the bug: https://github.com/amzn/amzn-
  drivers/commit/ed7754cdf6ca0d4fb3d76906abc17718cc3ffa23

  It's included starting in driver version 2.12.0.

  I have back ported the patch from the AWS OOT driver, as well as any
  existing prerequisites needed.

  [Test Plan]

  I have tested this, as has AWS.

  [Where problems could occur]

  As this is an Ubuntu Sauce patch, if these changes make their was into
  the stable trees, or any patches touching this area of code,  they may
  cause merge conflicts, or changes in behaviour which are unexpected.

  
  [Other]
  SF# f00396266

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2085159/+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 2080569] Re: AWS: support Out-Of-Band pstate mode for Emerald Rapids

[Philip Cox]

** Changed in: linux-aws (Ubuntu Noble)
   Status: In Progress => Fix Committed

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

Title:
  AWS: support Out-Of-Band pstate mode for Emerald Rapids

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Noble:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  In Emerald Rapids VMs, a stack trace is printed during boot on 6.8
  based kernels, but not 6.5 ones.  The stack traces look like:

  [1.206658] intel_pstate: Intel P-state driver initializing
  [1.207453] unchecked MSR access error: WRMSR to 0x199 (tried to write 
0x0800) at rIP: 0xb94c3b24 (native_write_msr+0x4/0x40)
  [1.208422] Call Trace:
  [1.208422]  
  [1.208422]  ? show_stack_regs+0x23/0x40
  [1.208422]  ? ex_handler_msr+0x10a/0x180
  [1.208422]  ? fixup_exception+0x183/0x390
  [1.208422]  ? gp_try_fixup_and_notify+0x23/0xc0
  [1.208422]  ? exc_general_protection+0x15e/0x480
  [1.208422]  ? asm_exc_general_protection+0x27/0x30
  [1.208422]  ? __pfx___wrmsr_on_cpu+0x10/0x10
  [1.208422]  ? native_write_msr+0x4/0x40
  [1.208422]  ? __wrmsr_on_cpu+0x4b/0x90
  [1.208422]  ? __pfx___rdmsr_on_cpu+0x10/0x10
  [1.208422]  ? __pfx___wrmsr_on_cpu+0x10/0x10
  [1.208422]  generic_exec_single+0x7e/0x120
  [1.208422]  smp_call_function_single+0x103/0x140
  [1.208422]  ? __pfx___wrmsr_on_cpu+0x10/0x10
  [1.208422]  wrmsrl_on_cpu+0x57/0x80
  [1.208422]  intel_pstate_set_pstate+0x3e/0x80
  [1.208422]  intel_pstate_get_cpu_pstates.constprop.0+0xd7/0x190
  [1.208422]  intel_pstate_init_cpu+0x3f/0x140
  [1.208422]  intel_cpufreq_cpu_init+0x44/0x270
  [1.208422]  ? freq_qos_add_notifier+0x45/0x80
  [1.208422]  cpufreq_online+0x444/0xb80
  [1.208422]  cpufreq_add_dev+0x99/0xd0
  [1.208422]  subsys_interface_register+0x11c/0x140
  [1.208422]  cpufreq_register_driver+0x1b5/0x330
  [1.208422]  intel_pstate_register_driver+0x48/0xd0
  [1.208422]  intel_pstate_init+0x25c/0x810
  [1.208422]  ? __pfx_intel_pstate_init+0x10/0x10
  [1.208422]  do_one_initcall+0x5b/0x310
  [1.208422]  do_initcalls+0x104/0x210
  [1.208422]  ? __pfx_kernel_init+0x10/0x10
  [1.208422]  kernel_init_freeable+0x134/0x1f0
  [1.208422]  kernel_init+0x1b/0x200
  [1.208422]  ret_from_fork+0x44/0x70
  [1.208422]  ? __pfx_kernel_init+0x10/0x10
  [1.208422]  ret_from_fork_asm+0x1b/0x30
  [1.208422]  

  [Fix]

  The reason that these traces are not found in the 6.5 kernel, but are
  in the 6.8 kernel one had the traces is that in the 6.5 kernel the CPU
  in the instance (Emerald Rapids) does not have the pstate support
  added yet.  The 6.8 kernel does have support though.  That is why they
  don't appear in the 6.5 kernel, but in the 6.8 kernel.

  In the 6.11 kernel the patch
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7e1c3f584ee78b0d0210fc424420d9529f3ca952
  was added to prevent trying to set the p-states while in OOB (Out-of-
  band) mode.  So, rather than having the VM trying to set the p-states,
  it is handled by the host OS/platform.

  
  [Test Plan]

  I have tested this.

  [Where problems could occur]
  In the 6.11 kernel tree where this change comes from, there has been some 
significant refactoring of the code.  If other changes need to be back-ported 
to the AWS 6.8 kernel, other conflicts or issues may arise.

  
  [Other]
  SF #00395865

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2080569/+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 2080414] Re: [N][AWS]Backport x86/kaslr fix impacting ML/HPC workloads

[Philip Cox]

** Changed in: linux-aws (Ubuntu Noble)
   Status: In Progress => Fix Committed

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

Title:
  [N][AWS]Backport x86/kaslr fix impacting ML/HPC workloads

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Noble:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  EC2 team discovered a Linux bug during ML/HPC workload testing on P5
  instances. The issue is described at
  https://lore.kernel.org/all/87ed6soy3z.ffs@tglx/ ("iounmap() on x86
  occasionally fails to unmap because the provided valid ioremap address
  is not below high_memory.").

  [Fix]

  This is fixed by upstream commit
  ea72ce5da22806d5713f3ffb39a6d5ae73841f93:

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

  [Test Plan]

  AWS tested

  [Where problems could occur]

  If there was code that made incorrect assumptions on how memory was
  laid out and used, it might break the functionality, but seeing as
  this is fixing an error, the chances of that should be fairly low.

  
  [Other Info]
  SF #00392654

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2080414/+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 2081943] Re: Application time out monitor does not work correctly

[Philip Cox]

I'm sorry you didn't agree with my analysis of the situation.

If you look at the dmesg file, or the syslog file, the minidlna is
having issues as it is throwing segmentation faults.

 Sep 21 01:54:38 Laptop2 kernel: minidlnad[93836]: segfault at 20 ip 
5c8984058dd2 sp 7ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] 
likely on CPU 4 (core 2, socket 0)
Sep 21 02:14:39 Laptop2 kernel: minidlnad[95522]: segfault at 20 ip 
5c8984058dd2 sp 7ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] 
likely on CPU 4 (core 2, socket 0)
Sep 21 08:15:16 Laptop2 kernel: minidlnad[108956]: segfault at 20 ip 
5c8984058dd2 sp 7ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] 
likely on CPU 1 (core 0, socket 0)
Sep 21 20:46:20 Laptop2 kernel: vivictpp[145335]: segfault at 7ecb98ea9d6d ip 
61b04f6fb869 sp 7ecc7a9ff980 error 6 in vivictpp[61b04e53d000+155c000] 
likely on CPU 0 (core 0, socket 0)
Sep 22 08:16:42 Laptop2 kernel: minidlnad[176849]: segfault at 20 ip 
5c8984058dd2 sp 7ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] 
likely on CPU 6 (core 3, socket 0)
Sep 22 14:44:27 Laptop2 kernel: minidlnad[201339]: segfault at 20 ip 
5c8984058dd2 sp 7ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] 
likely on CPU 0 (core 0, socket 0)
Sep 22 14:44:27 Laptop2 kernel: minidlnad[201353]: segfault at 20 ip 
5c8984058dd2 sp 7ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] 
likely on CPU 1 (core 0, socket 0)
Sep 22 15:52:06 Laptop2 kernel: minidlnad[204933]: segfault at 20 ip 
5c8984058dd2 sp 7ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] 
likely on CPU 3 (core 1, socket 0)
Sep 22 15:52:06 Laptop2 kernel: minidlnad[204935]: segfault at 20 ip 
5c8984058dd2 sp 7ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] 
likely on CPU 0 (core 0, socket 0)
Sep 25 01:16:23 Laptop2 kernel: minidlnad[347458]: segfault at 20 ip 
5c8984058dd2 sp 7ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] 
likely on CPU 7 (core 3, socket 0)
Sep 25 01:26:37 Laptop2 kernel: minidlnad[348092]: segfault at 20 ip 
5c8984058dd2 sp 7ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] 
likely on CPU 1 (core 0, socket 0)


I also know that there are reported memory leaks with minidlnad which I suspect 
was leading to the reduced performance. Also, when a major upgrade is done, as 
happens when moving from 22.04 to 24.04, even though the application you are 
running remains "unchanged", a lot of the underlying infrastructure changes, 
which can cause the application to fail in new/different ways.  

The upgrade to 24.04 changed many of the shared libraries, and the
kernel, so even though minidlnad is the same version, it doesn't mean
that because it used to be error-free that it still is.

Either way, the prompt  and timeout addition that you are asking about
is not a kernel issue.  I was just trying to help point you to a
possible root cause.

This issue is probably better to be opened against gnome-desktop
(https://bugs.launchpad.net/ubuntu/+source/gnome-desktop) or gnome-shell
(https://bugs.launchpad.net/ubuntu/+source/gnome-shell).

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

Title:
  Application time out monitor does not work correctly

Status in linux package in Ubuntu:
  Opinion

Bug description:
  Ubuntu 24.04.01

  System resources near by 100% in use. Never had a problem in this case
  with Ubuntu 22.04.03.

  E,g.: firefox open with 10Tabs, visible in the panel. Get the
  application in foreground,open a new Tab, e.g.: with youtube as
  address, got immediately the message Box with two Buttons "Wait for
  response" "Kill the process" of the respective application, in this
  case firefox.

  I did check wait during the youtube page will appear, get again the
  message Box, again check "wait", going to fill out the youtube "search
  txt box" and will be 15 times interrupted by the message box and have
  to check the "wait" button.

  Obviously the application firefox works as expected, but the
  application time out monitor does not recognize it (same with
  nautilus).

  After a call of the resources monitor application, I could switch off
  the senseless time out monitor message box with two Buttons "Wait for
  response" "Kill the process"

  A workaround would help : How to switch off this senseless monitor or
  to set the time out to 1h ?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-45-generic 6.8.0-45.45
  ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
  Uname: Linux 6.8.0-45-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:richard2036 F pipewire
   /dev/snd/controlC0:  richard2041 F wireplumber
   /dev/snd/controlC1:  richard2041 F wireplumber
  CRDA:

[Kernel-packages] [Bug 2081943] Re: Application time out monitor does not work correctly

[Philip Cox]

Hello, thank you for taking the time to open this bug report.

This sounds like a memory leak which is causing the system to slow down
and thrash to swap until it becomes unresponsive.  The application
"minidlnad" you are running is having some issues, and might be the
source of the leak.

If you reboot your system, it should help (temporarily), but updating
this application might help as well.

Otherwise, this isn't a kernel issue.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

Title:
  Application time out monitor does not work correctly

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 24.04.01

  System resources near by 100% in use. Never had a problem in this case
  with Ubuntu 22.04.03.

  E,g.: firefox open with 10Tabs, visible in the panel. Get the
  application in foreground,open a new Tab, e.g.: with youtube as
  address, got immediately the message Box with two Buttons "Wait for
  response" "Kill the process" of the respective application, in this
  case firefox.

  I did check wait during the youtube page will appear, get again the
  message Box, again check "wait", going to fill out the youtube "search
  txt box" and will be 15 times interrupted by the message box and have
  to check the "wait" button.

  Obviously the application firefox works as expected, but the
  application time out monitor does not recognize it (same with
  nautilus).

  After a call of the resources monitor application, I could switch off
  the senseless time out monitor message box with two Buttons "Wait for
  response" "Kill the process"

  A workaround would help : How to switch off this senseless monitor or
  to set the time out to 1h ?

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-45-generic 6.8.0-45.45
  ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
  Uname: Linux 6.8.0-45-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:richard2036 F pipewire
   /dev/snd/controlC0:  richard2041 F wireplumber
   /dev/snd/controlC1:  richard2041 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 25 07:26:51 2024
  InstallationDate: Installed on 2024-01-24 (245 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X515DA_M515DA
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic 
root=UUID=fd8b1656-bd1b-411b-b6bd-7cbf3bc18cdb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-45-generic N/A
   linux-backports-modules-6.8.0-45-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to noble on 2024-08-31 (25 days ago)
  dmi.bios.date: 10/19/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X515DA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X515DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX515DA.302:bd10/19/2020:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515DA_M515DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUSLaptop
  dmi.product.name: VivoBook_ASUSLaptop X515DA_M515DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081943/+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 2081963] Re: Acer Nitro 5 does not resume from suspend

[Philip Cox]

Hello, thank you for taking the time to open this bug.

Right now there is not much to go on in the provided logs, other than
there is an error with amdgpu.

Sep 25 12:32:26 Nitro-5 kernel: amdgpu :01:00.0:
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring comp_1.0.1 test
failed (-110)


Can you try suspending your laptop, and when you reboot it, run the follow 
command: 
  journalctl -b -1 -r

and paste the results?  I tmight provide more information.  Thank you.

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

Title:
  Acer Nitro 5 does not resume from suspend

Status in linux package in Ubuntu:
  New

Bug description:
  Resuming from suspend results in a black screen and keyboard lights
  turn on. System does not respond to any commands, including CTRL-
  ALT-F4.

  Need to reboot to recover.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-45-generic 6.8.0-45.45
  ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
  Uname: Linux 6.8.0-45-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:lasse  2361 F pipewire
   /dev/snd/controlC0:  lasse  2365 F wireplumber
   /dev/snd/controlC1:  lasse  2365 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 25 12:32:08 2024
  InstallationDate: Installed on 2024-08-14 (42 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: Acer Nitro AN515-43
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic 
root=UUID=2a8f106e-d087-45a9-8985-125718d940f0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-45-generic N/A
   linux-backports-modules-6.8.0-45-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2020
  dmi.bios.release: 1.12
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Octavia_PKS
  dmi.board.vendor: PK
  dmi.board.version: V1.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.12
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.12:bd11/05/2020:br1.12:efr1.7:svnAcer:pnNitroAN515-43:pvrV1.12:rvnPK:rnOctavia_PKS:rvrV1.12:cvnAcer:ct10:cvrV1.12:sku:
  dmi.product.family: Nitro 5
  dmi.product.name: Nitro AN515-43
  dmi.product.sku: 
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081963/+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 2081935] Re: Fan control stuck at high speed after upgrade to Ubuntu 24, thermal zone 6 fails to read sensor

[Philip Cox]

Hello, thank you for taking the time to open this bug report.

From what I can tell, this looks like it is this issue that was found
upstream: https://bugzilla.kernel.org/show_bug.cgi?id=201761

I will look into this a bit more and update the ticket when I have more
info.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

** Bug watch added: Linux Kernel Bug Tracker #201761
   https://bugzilla.kernel.org/show_bug.cgi?id=201761

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

Title:
  Fan control stuck at high speed after upgrade to Ubuntu 24, thermal
  zone 6 fails to read sensor

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 22 (kernel 5.x.x) to Ubuntu 24 (kernel
  6.8.x), I have encountered an issue with fan control on my Acer
  Predator PH315-54. The fans get stuck at high speed, even when the
  system temperatures are relatively low (30-40°C for both CPU and GPU).
  This problem did not occur on Ubuntu 22, where fan control worked
  properly.

  The issue seems related to the thermal_zone6 sensor, which
  consistently fails to provide a valid temperature reading in both
  dmesg and thermald logs.

  This is accompanied by the following error in dmesg:
  thermal thermal_zone6: failed to read out thermal zone (-61)

  In the thermald logs, I also observe errors related to sensor id 16:
  sensor id 16 : No temp sysfs for reading raw temp

  I have attempted multiple troubleshooting steps, including restarting
  and stopping thermald, checking BIOS settings, and reinstalling NVIDIA
  drivers, but the fan remains stuck at high speed. The issue persists
  regardless of system load, and the laptop remains cool to the touch.

  System Information:

  Model: Acer Predator PH315-54
  BIOS Version: V1.11
  Kernel Version: 6.x.x (Ubuntu 24)
  Thermal Sensors Detected:
  acpitz
  INT3400 Thermal
  SEN2
  SEN3
  TCPU
  x86_pkg_temp
  iwlwifi_1

  Steps to Reproduce:

  Boot into Ubuntu 24.
  Allow the system to idle or perform light system activities.
  Observe that the fan stays at high speed, regardless of system 
temperature.

  Expected Behavior:

  The fans should adjust dynamically according to system temperatures, slowing 
down when the system is idle or under light load.
  Actual Behavior:

  The fan remains at high speed continuously, even when the system is
  cool (30-40°C for CPU and GPU), and thermal_zone6 fails to read
  temperature data.

  Troubleshooting Steps Taken:

  Restarted Thermald: Restarting thermald does not fix the issue.
  Stopped Thermald: Disabling thermald temporarily reduces the issue, but 
the fan still runs at high speed under BIOS control.
  Reinstalled NVIDIA Drivers: The problem persists regardless of NVIDIA 
driver reinstallation.
  Checked Kernel Logs: The dmesg logs consistently show the thermal_zone6 
failure.
  Checked Sensors: Other sensors are reporting valid temperature data 
(e.g., CPU and GPU), but thermal_zone6 is not functional.
  BIOS Settings: Checked BIOS/UEFI for fan control options but found none. 
The BIOS was updated to the latest version (V1.11), but the issue persists.

  Additional Information:

  The issue appears to be tied to the kernel update (6.x.x) in Ubuntu 24. 
The fan control worked properly on Ubuntu 22 (kernel 5.x.x), suggesting a 
possible regression or missing support for hardware sensors in the newer kernel.
  The issue could be related to BIOS/ACPI fan management or a conflict with 
thermald in the newer kernel.

  I believe this may be a regression in the thermal management drivers,
  and I am willing to provide any additional logs or information
  required to help resolve it.

  I have also noticed a bunch of ACPI logs in 'dmesg' that i attached
  with this. This might be related or not i'm not sure.

  Regards!

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-45-generic 6.8.0-45.45
  ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
  Uname: Linux 6.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:alexgmenard   4277 F pipewire
   /dev/snd/controlC0:  alexgmenard   4282 F wireplumber
   /dev/snd/controlC1:  alexgmenard   4282 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 24 23:42:14 2024
  InstallationDate: Installed on 2022-08-19 (768 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Predator PH315-54
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic 

[Kernel-packages] [Bug 2081862] Re: new resiase upgrade crashed

[Philip Cox]

Hello, thank you for opening this bug report.

Can you please run the command "apport-collect 2081862" to collect the
information about your system so it is included in the bug report?  I
changed the package it was opened against, so this time more information
will be collected.  Thank you.

** Package changed: linux-signed-hwe-6.8 (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

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

Title:
  new resiase upgrade crashed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ошибка при обновлении

  При обновлении возникла проблема. Обычно это бывает вызвано проблемами
  в сети. Проверьте сетевые подключения и повторите попытку.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.8.0-45-generic 6.8.0-45.45~22.04.1
  ProcVersionSignature: Ubuntu 6.8.0-45.45~22.04.1-generic 6.8.12
  Uname: Linux 6.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 24 19:24:36 2024
  InstallationDate: Installed on 2023-10-04 (355 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.8
  UpgradeStatus: Upgraded to jammy on 2024-09-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081862/+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 2081821] Re: kernel 6.8.0-45

[Philip Cox]

This is likely related to the out-of-tree version of amdgpu you have
installed.  You can try to uninstall it, which should resolve the issue.
The other thing you may try is logging in via Xorg rather than wayland.

If removing the out of tree amdgpu doesn't resolve this, please re-open
this ticket, and run "apport-collect 2081821" to include the updated
logs and machine info.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

Title:
  kernel 6.8.0-45

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I can't log into the desktop using this core version.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-41-generic 6.8.0-41.41
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 24 19:03:29 2024
  InstallationDate: Installed on 2024-08-29 (26 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 03f0:2a4a HP, Inc HP USB Slim Keyboard - Skylab
   Bus 001 Device 003: ID 0461:4e84 Primax Electronics, Ltd USB Optical Mouse
   Bus 001 Device 004: ID 0bda:0169 Realtek Semiconductor Corp. Mass Storage 
Device
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: ASUSTeK COMPUTER INC. Pro E500 G7_WS750T
  ProcEnviron:
   LANG=zh_TW.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/zsh
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-generic 
root=UUID=0de158f2-58bf-4ac9-bbaf-06b2a4db3844 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-41-generic N/A
   linux-backports-modules-6.8.0-41-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2022
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0406
  dmi.board.asset.tag: Default string
  dmi.board.name: W580/SYS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0406:bd05/09/2022:br4.6:svnASUSTeKCOMPUTERINC.:pnProE500G7_WS750T:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnW580/SYS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: Server
  dmi.product.name: Pro E500 G7_WS750T
  dmi.product.sku: SKU
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081821/+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 2081693] Re: package linux-image-6.8.0-41-generic 6.8.0-41.41 failed to install/upgrade: installed linux-image-6.8.0-41-generic package pre-removal script subprocess returned er

[Philip Cox]

Hello, thank you for taking the time to open this bug report.

This seems to be working as designed, but perhaps not as you intended.
You are executing the command "apt-get purge linux-
image-6.8.0-41-generic", which is trying to purge the current running
kernel from your system.

If you boot in to another kernel, you will then be able to purge the
6.8.0-41-generic kernel without this prompt.

You can answer the prompt to purge the kernel, and on your next reboot
you will be booted into a previous kernel if one exists, otherwise your
system will be unusable.  This is why that warning is there.

If you are absolutely sure this is something you want to do, and you
want to avoid the prompt, you can use the command:

 sudo DEBIAN_FRONTEND=noninteractive apt-get purge linux-
image-6.8.0-41-generic

but this is not recomended.

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

Title:
  package linux-image-6.8.0-41-generic 6.8.0-41.41 failed to
  install/upgrade: installed linux-image-6.8.0-41-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Invalid

Bug description:
  System program problem detected

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-41-generic 6.8.0-41.41
  ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
  Uname: Linux 6.8.0-45-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  AptOrdering:
   linux-image-6.8.0-41-generic:amd64: Purge
   NULL: ConfigurePending
   NULL: PurgePending
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:mattakushi   2597 F pipewire
   /dev/snd/controlC0:  mattakushi   2606 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep 17 19:23:16 2024
  ErrorMessage: installed linux-image-6.8.0-41-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-04-25 (151 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  IwConfig:
   lono wireless extensions.
   
   ens33 no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 001 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 001 Device 004: ID 0e0f:0008 VMware, Inc. Virtual Bluetooth Adapter
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic 
root=UUID=10cb5289-1e93-4cb2-b33c-4c7807a4b29b ro 
debian-installer/custom-installation=/custom find_preseed=/preseed.cfg auto 
preseed/file=/floppy/preseed.cfg automatic-ubiquity noprompt priority=critical 
locale=en_US console-setup/modelcode=evdev
  Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.12-1ubuntu7
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-6.8.0-41-generic 6.8.0-41.41 failed to 
install/upgrade: installed linux-image-6.8.0-41-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to noble on 2024-06-19 (96 days ago)
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081693/+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 2081693] Re: package linux-image-6.8.0-41-generic 6.8.0-41.41 failed to install/upgrade: installed linux-image-6.8.0-41-generic package pre-removal script subprocess returned er

[Philip Cox]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

Title:
  package linux-image-6.8.0-41-generic 6.8.0-41.41 failed to
  install/upgrade: installed linux-image-6.8.0-41-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Invalid

Bug description:
  System program problem detected

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-41-generic 6.8.0-41.41
  ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
  Uname: Linux 6.8.0-45-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  AptOrdering:
   linux-image-6.8.0-41-generic:amd64: Purge
   NULL: ConfigurePending
   NULL: PurgePending
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:mattakushi   2597 F pipewire
   /dev/snd/controlC0:  mattakushi   2606 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep 17 19:23:16 2024
  ErrorMessage: installed linux-image-6.8.0-41-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-04-25 (151 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  IwConfig:
   lono wireless extensions.
   
   ens33 no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 001 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 001 Device 004: ID 0e0f:0008 VMware, Inc. Virtual Bluetooth Adapter
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic 
root=UUID=10cb5289-1e93-4cb2-b33c-4c7807a4b29b ro 
debian-installer/custom-installation=/custom find_preseed=/preseed.cfg auto 
preseed/file=/floppy/preseed.cfg automatic-ubiquity noprompt priority=critical 
locale=en_US console-setup/modelcode=evdev
  Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.12-1ubuntu7
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-6.8.0-41-generic 6.8.0-41.41 failed to 
install/upgrade: installed linux-image-6.8.0-41-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to noble on 2024-06-19 (96 days ago)
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081693/+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 2080949] Re: lubuntu oracular 6.11 kernel; 1 display 'cannot display' & unusable on LIVE

[Philip Cox]

Hi Chris, thank you for taking the time to open this bug report.

How are the displays connected?

I think this might be a duplicate of:
https://bugs.launchpad.net/bugs/2079491


** Changed in: linux (Ubuntu Oracular)
 Assignee: (unassigned) => Philip Cox (philcox)

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

Title:
  lubuntu oracular 6.11 kernel; 1 display 'cannot display' & unusable on
  LIVE

Status in linux package in Ubuntu:
  New
Status in linux source package in Oracular:
  New

Bug description:
  Lubuntu oracular live; first daily using 6.11 kernel on this box which
  I think is the key difference.

  On boot (this is second boot of this ISO) I get on one display a
  message

  1: Auto Detect (Digital Input)
  Cannot Display This Video Model
  Optimum resolution 1280x1024 60Hz

  and display was not usable.
  The other display works...

  ** Expected results

  I can use both displays; like I did earlier today OR do if I boot
  installed systems (Ubuntu noble, oracular [6.8], jammy, Debian
  testing)

  ** Actual results

  I'm limited to one display only; second shows a message & my
  LXQt.Monitor.Settings won't let me use the display..

  ** Other thoughts

  - booting this ISO in live mode & using `lshw -C video`, and comparing
  with installed systems I don't see any differences; I can save &
  append the results if helpful (I didn't save them & was relying on my
  bad.memory.. so not conclusive)

  - I have no issues on NOBLE, JAMMY installs; and hadn't noticed any on
  ORACULAR install either; but installed system was still on 6.8
  kernel...

  I booted the INSTALLED ORACULAR; applied `apt update; apt full-
  upgrade`, when done rebooted and IT HAD THE SAME ISSUE as this live
  system

  This is the first time I've experienced this.

  This video card is OLD!!  and I'm suspicious issue is this real old
  video car AND newer kernel; not Ubuntu specific issue; but bug report
  allows tracking into future (subsequent ISOs etc)

  Users with old hardware like this can still use Ubuntu 24.04 LTS and
  use the GA kernel stack??..

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: linux-image-6.11.0-7-generic 6.11.0-7.7
  ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7
  Uname: Linux 6.11.0-7-generic x86_64
  ApportVersion: 2.30.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:lubuntu1857 F pipewire
   /dev/snd/controlC1:  lubuntu1860 F wireplumber
   /dev/snd/controlC0:  lubuntu1860 F wireplumber
  CasperMD5CheckResult: pass
  CasperVersion: 1.502
  CurrentDesktop: LXQt
  Date: Tue Sep 17 11:15:18 2024
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Lubuntu 24.10 "Oracular Oriole" - Daily amd64 (20240916)
  MachineType: Dell Inc. OptiPlex 780
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.11.0-7-generic N/A
   linux-backports-modules-6.11.0-7-generic  N/A
   linux-firmware20240913.gita34e7a5f-0ubuntu2
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: yes
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2010
  dmi.bios.release: 3.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0200DY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd02/13/2010:br3.0:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0200DY:rvrA00:cvnDellInc.:ct3:cvr:sku:
  dmi.product.name: OptiPlex 780
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080949/+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 2080926] Re: issues after sleeping

[Philip Cox]

Hi Daniel, thank you for taking the time to open this bug report.

I've read over everything provided, and I do not see evidence of a crash
or hang.

The next time this happens, on the next boot, can you please run the
command "journalctl -b -1 -r" and post the results? It might contain the
info as to what happened.  Thank you.

Also, has this happened before?  I see you are running kernel version
6.8.0-44.  If this happened in the past, was it the same kernel version,
or is this a new thing?  Thank you.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

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

Title:
  issues after sleeping

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I left my laptop on last night because I wanted to continue some work
  today. I closed the laptop and went to bed.

  When I woke up,it was frozen on the password screen and I could not
  input anything.The shut down and restart options were also gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-44-generic 6.8.0-44.44
  ProcVersionSignature: Ubuntu 6.8.0-44.44-generic 6.8.12
  Uname: Linux 6.8.0-44-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:qd91   2779 F pipewire
   /dev/snd/controlC0:  qd91   2783 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 17 08:03:00 2024
  InstallationDate: Installed on 2024-02-08 (221 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Dell Inc. Latitude 5420
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-44-generic 
root=UUID=02738a08-52ac-4d19-88c9-cacd3b303bbb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-44-generic N/A
   linux-backports-modules-6.8.0-44-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to noble on 2024-05-22 (118 days ago)
  dmi.bios.date: 11/10/2023
  dmi.bios.release: 1.33
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.33.0
  dmi.board.name: 0772C9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd11/10/2023:br1.33:svnDellInc.:pnLatitude5420:pvr:rvnDellInc.:rn0772C9:rvrA00:cvnDellInc.:ct10:cvr:sku0A20:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5420
  dmi.product.sku: 0A20
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080926/+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 2081094] Re: Error with touchpad

[Philip Cox]

Hi @vpeixoto, this looks similiar to a couple other touchpad issues you
looked at.  When you can, can you take a look at this please?

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Vinicius Peixoto (vpeixoto)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Error with touchpad

Status in linux package in Ubuntu:
  New

Bug description:
  My touchpad doesn't work after upgrade ubuntu 22.04 to 24.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-40-generic 6.8.0-40.40
  ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:libert 2097 F pipewire
   /dev/snd/controlC0:  libert 2101 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 18 19:36:46 2024
  InstallationDate: Installed on 2023-05-26 (482 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: HP HP Pavilion Laptop 15-cs1xxx
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-40-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-6.8.0-40-generic N/A
   linux-backports-modules-6.8.0-40-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to noble on 2024-09-18 (0 days ago)
  dmi.bios.date: 03/06/2019
  dmi.bios.release: 15.15
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.15
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84C0
  dmi.board.vendor: HP
  dmi.board.version: 15.27
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 15.27
  dmi.modalias: 
dmi:bvnInsyde:bvrF.15:bd03/06/2019:br15.15:efr15.27:svnHP:pnHPPavilionLaptop15-cs1xxx:pvrType1ProductConfigId:rvnHP:rn84C0:rvr15.27:cvnHP:ct10:cvrChassisVersion:sku6EH46UAR#ABA:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cs1xxx
  dmi.product.sku: 6EH46UAR#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.init.d.apport: 2024-07-22T15:59:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081094/+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 2081037] Re: LG Gram screen brightness hot keys and battery charge limit regression

[Philip Cox]

Hello, thank you for taking the time to open this bug report.

Can you please run the command "apport-collect 2081037" to include the
logs and system information so we can look into this please?

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

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

Title:
  LG Gram screen brightness hot keys and battery charge limit regression

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm running Xubuntu 24.04 with all packages up to date on an LG Gram
  14ZD90Q. It's been upgraded in place since 23.04. When I first
  installed it, Xubuntu supported the Fn+F2/Fn+F3 screen brightness hot
  keys out of the box. They stopped working a couple of weeks ago. It's
  hard to pin down an exact cause, but I did install a kernel update
  around the same time. Some other Fn+FX hot keys still work (volume
  controls and keyboard backlighting). The remaining Fn+FX hot keys
  don't work, but I'm not sure whether that's a regression since I
  wasn't using them before noticing this bug.

  In addition, the battery charge limit threshold is no longer working.
  Per the "Battery care limit" instructions at
  https://docs.kernel.org/admin-guide/laptops/lg-laptop.html I had set
  the charge limit to 80%. Now it no longer has any effect.

  ```sh
  root@gram:~# cat /sys/class/power_supply/CMB0/charge_control_end_threshold 
  0
  root@gram:~# echo 80 > 
/sys/class/power_supply/CMB0/charge_control_end_threshold 
  root@gram:~# cat /sys/class/power_supply/CMB0/charge_control_end_threshold 
  0
  root@gram:~# echo 100 > 
/sys/class/power_supply/CMB0/charge_control_end_threshold 
  root@gram:~# cat /sys/class/power_supply/CMB0/charge_control_end_threshold 
  0
  root@gram:~# echo 50 > 
/sys/class/power_supply/CMB0/charge_control_end_threshold 
  bash: echo: write error: Invalid argument
  ```

  Both of the supported values 80 and 100 are accepted, but don't take
  effect. An invalid value throws an error as previously.

  This may be related to upstream bug
  https://bugzilla.kernel.org/show_bug.cgi?id=204913.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081037/+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 2080943] Re: bug 2080773 Lenovo thinkpad X1 yoga requires reset after shutdown

[Philip Cox]

Thank you for taking the time to open this bug.

Nothing is standing out in any of the logs as to what might be causing
this.

After this has happened, on the next boot, can you please run the command:
journalctl -b -1 -r
and include the output?  Thank you.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

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

Title:
  bug 2080773 Lenovo thinkpad X1 yoga requires reset after shutdown

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since updating from 22.04 LTS to 24.04 LTS after shutdown the laptop does not 
turn on again, the button is like dead. No LEDs light up. Furthermore, after 
sleep mode no resuming is possible.
  In both cases pressing the reset button in the back of the laptop with a 
needle or pressing the power button for 10 seconds allow a clean boot 
afterwards.
  Verification: This also happens when booting a 24.04 live usb stick, however 
it works cleanly with a 22.04 live usb stick.

  I am happy to provide more information if needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-44-generic 6.8.0-44.44
  ProcVersionSignature: Ubuntu 6.8.0-44.44-generic 6.8.12
  Uname: Linux 6.8.0-44-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:hermann1924 F pipewire
   /dev/snd/controlC0:  hermann1927 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue Sep 17 12:02:31 2024
  InstallationDate: Installed on 2022-07-03 (807 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 20FRS05C00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-44-generic 
root=UUID=c550bb3f-9a3b-4463-b2a6-bfe32a4d572e 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-6.8.0-44-generic N/A
   linux-backports-modules-6.8.0-44-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to noble on 2024-09-04 (13 days ago)
  dmi.bios.date: 05/31/2022
  dmi.bios.release: 1.53
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET79W (1.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS05C00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET79W(1.53):bd05/31/2022:br1.53:efr1.9:svnLENOVO:pn20FRS05C00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FRS05C00:rvrNotDefined:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20FR_BU_Think_FM_ThinkPadX1Carbon4th:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FRS05C00
  dmi.product.sku: LENOVO_MT_20FR_BU_Think_FM_ThinkPad X1 Carbon 4th
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080943/+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 2080851] Re: package linux-headers-6.8.0-44-generic 6.8.0-44.44 failed to install/upgrade: installed linux-headers-6.8.0-44-generic package post-installation script subprocess r

[Philip Cox]

Hello, thank you for taking the time to open this bug report.

It looks like the failure is being caused because you have multiple
nvidia dkms packages installed.

If you have installed nvidia dkms packages yourself, please try removing
them, and then using the Ubuntu provided/tested nvidia dkms package.
That should resolve the issue you have hit.

If that does not solve the problem, please re-open this ticket, and let
me know.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

Title:
  package linux-headers-6.8.0-44-generic 6.8.0-44.44 failed to
  install/upgrade: installed linux-headers-6.8.0-44-generic package
  post-installation script subprocess returned error exit status 11

Status in linux package in Ubuntu:
  Invalid

Bug description:
  When install packages

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: linux-headers-6.8.0-44-generic 6.8.0-44.44
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:pprados2619 F pipewire
   /dev/snd/controlC0:  pprados2624 F wireplumber
   /dev/snd/controlC1:  pprados2619 F pipewire
pprados2624 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Mon Sep 16 14:33:22 2024
  ErrorMessage: installed linux-headers-6.8.0-44-generic package 
post-installation script subprocess returned error exit status 11
  InstallationDate: Installed on 2024-06-06 (102 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: HP HP ZBook 15 G6
  ProcFB: 0 simpledrmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-generic 
root=UUID=308acfb4-3abd-47c9-b37a-5833696e8d04 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.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-6.8.0-44-generic 6.8.0-44.44 failed to 
install/upgrade: installed linux-headers-6.8.0-44-generic package 
post-installation script subprocess returned error exit status 11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2024
  dmi.bios.release: 28.0
  dmi.bios.vendor: HP
  dmi.bios.version: R92 Ver. 01.28.00
  dmi.board.name: 860F
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 65.37.00
  dmi.chassis.asset.tag: 5CD9420F98
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 101.55
  dmi.modalias: 
dmi:bvnHP:bvrR92Ver.01.28.00:bd04/12/2024:br28.0:efr101.55:svnHP:pnHPZBook15G6:pvrSBKPF:rvnHP:rn860F:rvrKBCVersion65.37.00:cvnHP:ct10:cvr:sku6CJ09AV:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook 15 G6
  dmi.product.sku: 6CJ09AV
  dmi.product.version: SBKPF
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080851/+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 2080638] Re: [QCA9377] Bluetoth turning off every reboot and i need to reinstall e restart the modules everytime

[Philip Cox]

Hi Jorge , thank you for taking the time to open this bug report!

I've gone over the kernel logs, and nothing in the kernel logs indicate
a kernel issue.

I see the bluetooth device set up, and functioning, and then later
systemd is called to stop and restart the device, which also doesn't git
any issue.  This sounds like a config issue, or some option that is set
in the bluetooth stack.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

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

Title:
  [QCA9377] Bluetoth turning off every reboot and i need to reinstall e
  restart the modules everytime

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

Bug description:
  Hi! Bluetooth turn off at every reboot. What i need to do at every
  restart is:

  sudo modprobe -r btusb btbcm btintel btmtk btrtl

  sudo modprobe -r bluetooth

  sudo apt-get install --reinstall bluez bluez-tools

  sudo modprobe btusb

  sudo systemctl restart bluetooth

  
  And it start to work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: bluetooth 5.72-0ubuntu5
  ProcVersionSignature: Ubuntu 6.8.0-44.44-generic 6.8.12
  Uname: Linux 6.8.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 13 09:15:12 2024
  InstallationDate: Installed on 2024-06-27 (78 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512FB_X512FB
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-44-generic 
root=UUID=c58a91e9-450e-44c5-8fdc-9a17d4d7ea7d ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X512FB.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X512FB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX512FB.309:bd01/29/2021:br5.13:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512FB_X512FB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512FB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X512FB_X512FB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:63:A1:25:1C:12  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING 
RX bytes:4083 acl:35 sco:0 events:191 errors:0
TX bytes:6512 acl:37 sco:0 commands:116 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2080638/+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 2080489] Re: Network Manager stops functioning on Ubuntu 24.04

[Philip Cox]

Thank you Luís for taking the time to open this ticket, and respond with
the additional logs. I am from the from the kernel team, and I have
looked over the dmesg.log that you have provided.


I don't see any networking issues in the kernel log relating to the kernel, but 
I do see that some Virtual Box modules have been loaded which are out of tree, 
and unsupported by us.

I see that the "VBoxNetFlt" among other Virtual box drivers have been
loaded.  This one is the Virtual Box "Network Filter Driver".  I think
there is a good chance that the newer kernel version you are now running
is not playing nicely with the VirtualBox drivers.  Can you please un-
install them, and see if the problem still exists?  I do not see any
other networking related problems in the kernel log.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

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

Title:
  Network Manager stops functioning on Ubuntu 24.04

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 24.04 about a month ago on a Asus Vivobook. Soon
  after the NetworkManager started misbehaving, with all connections to
  the internet becoming idle now and then. When this event happens the
  only way to restore internet access is to reboot the system. If
  initially these events were occasional, they now take place 3 or 4
  times per day, often after signing in from the lock screen.

  So far I was not able to verify whether NetworkManager is actually
  crashing, the Settings programme reports "NetworkManager not running"
  (see attached image). However, in the command line `systemctl` reports
  an active service:

  ```
  $ systemctl status NetworkManager
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled>
   Active: active (running) since Sun 2024-08-27 18:21:44 WEST; 2h 18min a>
     Docs: man:NetworkManager(8)
     Main PID: 1149 (NetworkManager)
    Tasks: 4 (limit: 18646)
   Memory: 12.2M (peak: 28.6M)
  CPU: 836ms
   CGroup: /system.slice/NetworkManager.service
   └─1149 /usr/sbin/NetworkManager --no-daemon

  ago 27 19:34:08 Symbolic NetworkManager[1149]:   [1724006048.8961] man>
  ago 27 19:34:08 Symbolic NetworkManager[1149]:   [1724006048.8965] dev>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1482] dev>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1484] dev>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1488] dhc>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1488] dhc>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1489] dhc>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.2049] dev>
  ago 27 20:33:50 Symbolic NetworkManager[1149]:   [1724009630.5340] man>
  ago 27 20:33:50 Symbolic NetworkManager[1149]:   [1724009630.5344] dev>
  ```

  But if I try to restart the service, the command line just hangs up:

  ```
  $ ping 1.1.1.1
  ping: connect: Network is unreachable

  $ sudo systemctl restart NetworkManager

  ```

  Also from `ifconfig` there is no response:

  ```
  $ ifconfig -a

  ```

  Please let me know if there is further useful information I can
  report.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080489/+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 2080860] Re: Kernel 6.8.0-40 causes frequent screen flickering in Ubuntu 22.04

[Philip Cox]

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

Thank you for taking the time to open this bug report.  This seems to be
a duplicate of https://bugs.launchpad.net/bugs/2062951 which is waiting
for the fix to be released.  If the fix doesn't resolve this, please re-
open this ticket, and let me know.  Thanks.

** Package changed: linux-signed-hwe-6.8 (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

** This bug has been marked a duplicate of bug 2062951
   Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 
6.8

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

Title:
  Kernel 6.8.0-40 causes frequent screen flickering in Ubuntu 22.04

Status in linux package in Ubuntu:
  New

Bug description:
  Kernel 6.8.0-40 causes frequent screen flickering in Ubuntu 22.04 to
  the point of making it unusable. Screen flickering goes away when the
  kernel is rolled back to 6.5.0-45.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3
  ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Mon Sep 16 10:23:17 2024
  InstallationDate: Installed on 2023-07-16 (427 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:nilesh 2629 F pipewire
   /dev/snd/controlC0:  nilesh 2631 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-07-16 (427 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  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 5986:0711 Acer, Inc EasyCamera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80SA
  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 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-40-generic 
root=UUID=bb20bde2-de66-4eea-bd8a-be94bba37fdc ro quiet splash loglevel=3 
vt.handoff=7
  ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-40-generic N/A
   linux-backports-modules-6.8.0-40-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.31
  Tags:  wayland-session jammy
  Uname: Linux 6.8.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip kvm libvirt lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/26/2016
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0VCN22WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo ideapad F
  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 ideapad FLEX 4-1470
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvr0VCN22WW(V1.06):bd09/26/2016:br1.22:efr1.22:svnLENOVO:pn80SA:pvrLenovoideapadFLEX4-1470:rvnLENOVO:rnLenovoideapadF:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1470:skuLENOVO_MT_80SA_BU_idea_FM_LenovoideapadFLEX4-1470:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80SA
  dmi.product.sku: LENOVO_MT_80SA_BU_idea_FM_Lenovo ideapad FLEX 4-1470
  dmi.product.version: Lenovo ideapad FLEX 4-1470
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080860/+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 2080563] Re: Backport "x86/kaslr: Expose and use the end of the physical memory address space"

[Philip Cox]

** Changed in: linux-gcp (Ubuntu)
 Assignee: (unassigned) => Magali Lemes do Sacramento (magalilemes)

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

Title:
  Backport "x86/kaslr: Expose and use the end of the physical memory
  address space"

Status in linux-gcp package in Ubuntu:
  New

Bug description:
  [Impact]
  Request from Google to backport "x86/kaslr: Expose and use the end of the
  physical memory address space" to address intermittent CUDA hangs.

  [Fix]
  ea72ce5da22806d5713f3ffb39a6d5ae73841f93 ("x86/kaslr: Expose and use the end 
of the physical memory address space")

  [Test]

  
  [Where problems could occur]
  The fix directly affects memory management in x86 systems, specifically when 
KASLR
  is enabled.

  [Other info]
  #SF 00395854

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2080563/+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 2080443] Re: Create 64K page size GCP kernel for ARM

[Philip Cox]

** Changed in: linux-gcp (Ubuntu)
 Assignee: (unassigned) => Ian Whitfield (ijwhitfield)

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

Title:
  Create 64K page size GCP kernel for ARM

Status in linux-gcp package in Ubuntu:
  New

Bug description:
  [Impact]

  * 64k page size flavor was requested by Google

  [Fix]

  * Add flavour and configs for 64k flavour

  [Test Case]

  * Compile tested
  * Boot tested

  [Where things could go wrong]

  * Low chance of regression as no logic is changed
  * Should be verified by checking built packages

  [Other Info]

  * SF #00384132

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2080443/+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 2080569] [NEW] AWS: support Out-Of-Band pstate mode for Emerald Rapids

[Philip Cox]

Public bug reported:

SRU Justification:

[Impact]

In Emerald Rapids VMs, a stack trace is printed during boot on 6.8 based
kernels, but not 6.5 ones.  The stack traces look like:

[1.206658] intel_pstate: Intel P-state driver initializing
[1.207453] unchecked MSR access error: WRMSR to 0x199 (tried to write 
0x0800) at rIP: 0xb94c3b24 (native_write_msr+0x4/0x40)
[1.208422] Call Trace:
[1.208422]  
[1.208422]  ? show_stack_regs+0x23/0x40
[1.208422]  ? ex_handler_msr+0x10a/0x180
[1.208422]  ? fixup_exception+0x183/0x390
[1.208422]  ? gp_try_fixup_and_notify+0x23/0xc0
[1.208422]  ? exc_general_protection+0x15e/0x480
[1.208422]  ? asm_exc_general_protection+0x27/0x30
[1.208422]  ? __pfx___wrmsr_on_cpu+0x10/0x10
[1.208422]  ? native_write_msr+0x4/0x40
[1.208422]  ? __wrmsr_on_cpu+0x4b/0x90
[1.208422]  ? __pfx___rdmsr_on_cpu+0x10/0x10
[1.208422]  ? __pfx___wrmsr_on_cpu+0x10/0x10
[1.208422]  generic_exec_single+0x7e/0x120
[1.208422]  smp_call_function_single+0x103/0x140
[1.208422]  ? __pfx___wrmsr_on_cpu+0x10/0x10
[1.208422]  wrmsrl_on_cpu+0x57/0x80
[1.208422]  intel_pstate_set_pstate+0x3e/0x80
[1.208422]  intel_pstate_get_cpu_pstates.constprop.0+0xd7/0x190
[1.208422]  intel_pstate_init_cpu+0x3f/0x140
[1.208422]  intel_cpufreq_cpu_init+0x44/0x270
[1.208422]  ? freq_qos_add_notifier+0x45/0x80
[1.208422]  cpufreq_online+0x444/0xb80
[1.208422]  cpufreq_add_dev+0x99/0xd0
[1.208422]  subsys_interface_register+0x11c/0x140
[1.208422]  cpufreq_register_driver+0x1b5/0x330
[1.208422]  intel_pstate_register_driver+0x48/0xd0
[1.208422]  intel_pstate_init+0x25c/0x810
[1.208422]  ? __pfx_intel_pstate_init+0x10/0x10
[1.208422]  do_one_initcall+0x5b/0x310
[1.208422]  do_initcalls+0x104/0x210
[1.208422]  ? __pfx_kernel_init+0x10/0x10
[1.208422]  kernel_init_freeable+0x134/0x1f0
[1.208422]  kernel_init+0x1b/0x200
[1.208422]  ret_from_fork+0x44/0x70
[1.208422]  ? __pfx_kernel_init+0x10/0x10
[1.208422]  ret_from_fork_asm+0x1b/0x30
[1.208422]  

[Fix]

The reason that these traces are not found in the 6.5 kernel, but are in
the 6.8 kernel one had the traces is that in the 6.5 kernel the CPU in
the instance (Emerald Rapids) does not have the pstate support added
yet.  The 6.8 kernel does have support though.  That is why they don't
appear in the 6.5 kernel, but in the 6.8 kernel.

In the 6.11 kernel the patch
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7e1c3f584ee78b0d0210fc424420d9529f3ca952
was added to prevent trying to set the p-states while in OOB (Out-of-
band) mode.  So, rather than having the VM trying to set the p-states,
it is handled by the host OS/platform.


[Test Plan]

I have tested this.

[Where problems could occur]
In the 6.11 kernel tree where this change comes from, there has been some 
significant refactoring of the code.  If other changes need to be back-ported 
to the AWS 6.8 kernel, other conflicts or issues may arise.


[Other]
SF #00395865

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Assignee: Philip Cox (philcox)
 Status: Fix Released

** Affects: linux-aws (Ubuntu Noble)
 Importance: High
 Assignee: Philip Cox (philcox)
 Status: In Progress

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

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

** Changed in: linux-aws (Ubuntu Noble)
 Assignee: (unassigned) => Philip Cox (philcox)

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

** Changed in: linux-aws (Ubuntu Noble)
   Status: Confirmed => Triaged

** Changed in: linux-aws (Ubuntu Noble)
   Status: Triaged => In Progress

** Changed in: linux-aws (Ubuntu Noble)
   Importance: Undecided => High

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

Title:
  AWS: support Out-Of-Band pstate mode for Emerald Rapids

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Noble:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

  In Emerald Rapids VMs, a stack trace is printed during boot on 6.8
  based kernels, but not 6.5 ones.  The stack traces look like:

  [1.206658] intel_pstate: Intel P-state driver initializing
  [1.207453] unchecked MSR access error: WRMSR to 0x199 (tried to write 
0x0800) at rIP: 0xb94c3b24 (native_write_msr+0x4/0x40)
  [1.208422] Call Trace:
  [1.208422]  
  [1.208422]  ? show_stack_regs+0x23/0x40
  [1.208422]  ? ex_handler_msr+0x10a/0x180
  [1.208422]  ? fixup_exception+0x183/0x390
  [1.208422]  ? gp_try_fixup_and_notify+0x23/0xc0
  [1.208422]  ? exc_general_protection+0x15

[Kernel-packages] [Bug 2076986] Re: Lenovo Touchpad not working or detected in 'Lenovo Legion 9 16IRX9' following Ubuntu 22.04 installation.

[Philip Cox]

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

Hi Cara, and Davide,

I was talking to another member of the kernel team, and he mentioned he
was working on an issue that seemed very similar to the issue you both
have hit.

After looking into it more deeply, we are sure that they are the same
issue.

He has made more progress on the issue, and has reproduced it.  I will
be marking this ticket as a duplicate of
https://bugs.launchpad.net/bugs/2080355 and @vpeixoto will continue the
investigation.

** This bug has been marked a duplicate of bug 2080355
   Kernel trouble, with some trace, 6.8.0-44-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/2076986

Title:
  Lenovo Touchpad not working or detected in 'Lenovo Legion 9 16IRX9'
  following Ubuntu 22.04 installation.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Legion 9 touchpad on my laptop is unresponsive after
  installing Ubuntu 22.04. How might I get it working again? A lot of
  solutions suggested to downgrade the kernel but the posts I found were
  from 2+ years ago.

  Below is the output from 'cat /proc/bus/input/devices'. Note that the
  Logitech mouse is a (functional) wired mouse I was using at the time.

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
  U: Uniq=
  H: Handlers=kbd event0
  B: PROP=0
  B: EV=3
  B: KEY=8000 10 0

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
  U: Uniq=
  H: Handlers=event1
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2
  B: PROP=0
  B: EV=3
  B: KEY=8000 10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=046d Product=c050 Version=0110
  N: Name="Logitech USB-PS/2 Optical Mouse"
  P: Phys=usb-:00:14.0-4/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:046D:C050.0003/input/input4
  U: Uniq=
  H: Handlers=mouse0 event4
  B: PROP=0
  B: EV=17
  B: KEY=ff 0 0 0 0
  B: REL=1943
  B: MSC=10

  I: Bus=0003 Vendor=048d Product=c990 Version=0110
  N: Name="ITE Tech. Inc. ITE Device(8258) Keyboard"
  P: Phys=usb-:00:14.0-6/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:048D:C990.0004/input/input5
  U: Uniq=
  H: Handlers=sysrq kbd event5 leds
  B: PROP=0
  B: EV=12001f
  B: KEY=33eff 0 0 48317aff32d bfd6 1 130c730b17c007 
ffbf7bfad9415fff febeffdfffef fffe
  B: REL=1040
  B: ABS=1
  B: MSC=10
  B: LED=1f

  I: Bus=0003 Vendor=048d Product=c990 Version=0110
  N: Name="ITE Tech. Inc. ITE Device(8258)"
  P: Phys=usb-:00:14.0-6/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:048D:C990.0004/input/input6
  U: Uniq=
  H: Handlers=event6
  B: PROP=0
  B: EV=9
  B: ABS=100

  I: Bus=0003 Vendor=048d Product=c990 Version=0110
  N: Name="ITE Tech. Inc. ITE Device(8258) Wireless Radio Control"
  P: Phys=usb-:00:14.0-6/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:048D:C990.0004/input/input7
  U: Uniq=
  H: Handlers=rfkill kbd event7
  B: PROP=0
  B: EV=13
  B: KEY=80 0 0 0
  B: MSC=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input8
  U: Uniq=
  H: Handlers=event8
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input9
  U: Uniq=
  H: Handlers=event9
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=8"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input10
  U: Uniq=
  H: Handlers=event10
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=9"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input11
  U: Uniq=
  H: Handlers=event11
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus=0019 Vendor=0

[Kernel-packages] [Bug 2079985] Re: Lenovo Legion 9 16IRX9 - Touchpad is missing on Ubuntu 22.04+

[Philip Cox]

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

** This bug is no longer a duplicate of bug 2076986
   Lenovo Touchpad not working or detected in 'Lenovo Legion 9 16IRX9' 
following Ubuntu 22.04 installation.
** This bug has been marked a duplicate of bug 2080355
   Kernel trouble, with some trace, 6.8.0-44-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/2079985

Title:
  Lenovo Legion 9 16IRX9 - Touchpad is missing on Ubuntu 22.04+

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brand new Lenovo Legion 9 16IRX9. It doesn't seem to detect any touchpad. 
  I also tested PopOS 24.04 liveUSB and it doesn't work.
  In Windows 11 it works.

  user@lenovo-Legion-9-16IRX9:~$ neofetch 
  .-/+oooo+/-.   user@droneracing-Legion-9-16IRX9 
  `:+ss+:`   
--- 
-+ssyy+- OS: Ubuntu 22.04.4 LTS x86_64 
  .ossdMMMNyo.   Host: 83G0 Legion 9 16IRX9 
 /ssshdmmNNmmyNhss/  Kernel: 6.8.0-40-generic 
+shmydMMMNy+ Uptime: 27 mins 
   /hNMMMyhhhmNMMMNh/Packages: 1859 (dpkg), 9 (snap) 
  .dMMMNhsshNMMMd.   Shell: bash 5.1.16 
  +hhhyNMMNyyNMMMysss+   Resolution: 3200x2000 
  ossyNMMMNyMMhsshmmmhssso   DE: GNOME 42.9 
  ossyNMMMNyMMhsshmmmhssso   WM: Mutter 
  +hhhyNMMNyyNMMMysss+   WM Theme: Adwaita 
  .dMMMNhsshNMMMd.   Theme: Yaru [GTK2/3] 
   /hNMMMyhhhdNMMMNh/Icons: Yaru [GTK2/3] 
+sdmydy+ Terminal: gnome-terminal 
 /ssshdmmyNhss/  CPU: Intel i9-14900HX (32) @ 
5.600GHz 
  .ossdMMMNyo.   GPU: Intel Device a788 
-+syyy+- GPU: NVIDIA 01:00.0 NVIDIA 
Corporation Device 2757 
  `:+ss+:`   Memory: 2943MiB / 64004MiB 

  user@lenovo-Legion-9-16IRX9:~$ xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ PixArt Lenovo USB Optical Mouse id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8258) Keyboardid=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8258) Keyboardid=14   [slave  
keyboard (3)]
  ∼ ITE Tech. Inc. ITE Device(8258) Wireless Radio Control  id=12   
[floating slave]


  user@lenovo-Legion-9-16IRX9:~$ sudo acpidump | grep -C3 -i elan
 79490: 50 44 53 0A 02 70 0C 40 42 0F 00 53 50 45 44 A4  pds@b..sped.
 794A0: 00 08 5F 48 49 44 0D 58 58 58 58 30 30 30 30 00  .._HID..
 794B0: 08 5F 53 55 42 0D 58 58 58 58 30 30 30 30 00 A0  ._SUB...
 794C0: 25 93 54 50 54 59 01 70 0D 45 4C 41 4E 30 36 46  %.TPTY.p.ELAN06F
 794D0: 41 00 5F 48 49 44 70 0D 45 4C 41 4E 30 30 30 31  A._HIDp.ELAN0001
 794E0: 00 5F 53 55 42 A1 28 A0 26 93 54 50 54 59 0A 02  ._SUB.(.&.TPTY..
 794F0: 70 0D 53 59 4E 41 32 42 41 36 00 5F 48 49 44 70  p.SYNA2BA6._HIDp
 79500: 0D 53 59 4E 41 30 30 30 31 00 5F 53 55 42 08 5F  .SYNA0001._SUB._

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3
  ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  9 16:37:04 2024
  InstallationDate: Installed on 2024-09-09 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: linux-signed-hwe-6.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  droneracing   1363 F pulseaudio
   /dev/snd/controlC0:  droneracing   1363 F..

[Kernel-packages] [Bug 2080355] Re: Kernel trouble, with some trace, 6.8.0-44-generic

[Philip Cox]

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Kernel trouble, with some trace, 6.8.0-44-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since the release upgrade 22.04 to 24.04.1, I have a bunch a problems; 
starting with the kernel at boot, later on with udev. 
  Here is the dmesg for the usual cold start:

  ```
  9.487625] Console: switching to colour frame buffer device 160x45
  [9.551017] intel-vbtn INT33D6:00: Registering Intel Virtual Switches 
input-dev after receiving a switch event
  [9.551112] input: Intel Virtual Switches as 
/devices/pci:00/:00:1f.0/PNP0C09:00/INT33D6:00/input/input36
  [9.551161] intel-vbtn INT33D6:00: Registering Intel Virtual Switches 
input-dev after receiving a switch event
  [9.552011] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:1f.0/PNP0C09:00/INT33D6:00/input/input36'
  [9.552017] CPU: 2 PID: 206 Comm: kworker/2:4 Not tainted 6.8.0-44-generic 
#44-Ubuntu
  [9.552022] Hardware name: LENOVO 20CHS10P02/20CHS10P02, BIOS N17ETB6W 
(2.16 ) 09/02/2021
  [9.552025] Workqueue: kacpi_notify acpi_os_execute_deferred
  [9.552034] Call Trace:
  [9.552037]  
  [9.552040]  dump_stack_lvl+0x76/0xa0
  [9.552047]  dump_stack+0x10/0x20
  [9.552051]  sysfs_warn_dup+0x8a/0xb0
  [9.552057]  sysfs_create_dir_ns+0xe0/0x100
  [9.552063]  kobject_add_internal+0xa8/0x2f0
  [9.552067]  kobject_add+0x93/0x100
  [9.552071]  ? get_device_parent+0xd0/0x210
  [9.552076]  device_add+0xe0/0x740
  [9.552079]  input_register_device+0xe8/0x370
  [9.552087]  notify_handler+0x12e/0x1a0 [intel_vbtn]
  [9.552095]  acpi_ev_notify_dispatch+0x59/0xa0
  [9.552101]  acpi_os_execute_deferred+0x1a/0x40
  [9.552105]  process_one_work+0x16f/0x350
  [9.552112]  worker_thread+0x306/0x440
  [9.552117]  ? _raw_spin_lock_irqsave+0xe/0x20
  [9.552122]  ? __pfx_worker_thread+0x10/0x10
  [9.552127]  kthread+0xf2/0x120
  [9.552131]  ? __pfx_kthread+0x10/0x10
  [9.552135]  ret_from_fork+0x47/0x70
  [9.552139]  ? __pfx_kthread+0x10/0x10
  [9.552143]  ret_from_fork_asm+0x1b/0x30
  [9.552149]  
  [9.552151] kobject: kobject_add_internal failed for input36 with -EEXIST, 
don't try to register things with the same name in the same directory.
  [9.615562] BUG: kernel NULL pointer dereference, address: 0018
  [9.615634] #PF: supervisor read access in kernel mode
  [9.615681] #PF: error_code(0x) - not-present page
  [9.615727] PGD 0 P4D 0 
  [9.615753] Oops:  [#1] PREEMPT SMP PTI
  [9.615793] CPU: 2 PID: 204 Comm: kworker/2:3 Not tainted 6.8.0-44-generic 
#44-Ubuntu
  [9.615863] Hardware name: LENOVO 20CHS10P02/20CHS10P02, BIOS N17ETB6W 
(2.16 ) 09/02/2021
  [9.615934] Workqueue: kacpi_notify acpi_os_execute_deferred
  [9.615992] RIP: 0010:klist_add_tail+0x2a/0x80
  [9.616039] Code: 55 48 89 e5 41 55 4c 8d 6f 08 41 54 49 89 fc 53 48 89 f3 
48 89 37 83 e6 01 4c 89 6f 08 4c 89 6f 10 c7 47 18 01 00 00 00 75 4d <48> 8b 43 
18 48 85 c0 74 08 4c 89 e7 e8 05 39 0c 00 48 89 df e8 4d
  [9.616200] RSP: 0018:be9c00513c98 EFLAGS: 00010246
  [9.616249] RAX: 992c95e69700 RBX:  RCX: 

  [9.616307] RDX:  RSI:  RDI: 
992c95e69728
  [9.616368] RBP: be9c00513cb0 R08:  R09: 

  [9.616422] R10:  R11:  R12: 
992c95e69728
  [9.616488] R13: 992c95e69730 R14:  R15: 
992c99fe2890
  [9.616551] FS:  () GS:992da5b0() 
knlGS:
  [9.616627] CS:  0010 DS:  ES:  CR0: 80050033
  [9.616681] CR2: 0018 CR3: 00010c34e006 CR4: 
003706f0
  [9.616747] DR0:  DR1:  DR2: 

  [9.616810] DR3:  DR6: fffe0ff0 DR7: 
0400
  [9.616876] Call Trace:
  [9.616902]  
  [9.616924]  ? show_regs+0x6d/0x80
  [9.616960]  ? __die+0x24/0x80
  [9.616992]  ? page_fault_oops+0x99/0x1b0
  [9.618392]  ? do_user_addr_fault+0x2e2/0x670
  [9.619819]  ? exc_page_fault+0x83/0x1b0
  [9.621268]  ? asm_exc_page_fault+0x27/0x30
  [9.622752]  ? klist_add_tail+0x2a/0x80
  [9.624234]  device_add+0x590/0x740
  [9.625492]  cdev_device_add+0x4e/0xc0
  [9.626728]  ? cdev_init+0x56/0x70
  [9.628295]  evdev_connect+0x1a9/0x210
  [9.629892]  input_attach_handler.isra.0+0x84/0xc0
  [9.631508]  input_register_device+0x231/0x370
  [9.632591]  notify_handler+0x12e/0x1a0 [intel_vbtn]
  [9.634220]  acpi_ev_notify_dispatch+0x59/0xa0
  [9.6359

[Kernel-packages] [Bug 2080341] Re: package linux-headers-generic 6.8.0-44.44 failed to install/upgrade: problèmes de dépendances - laissé non configuré

[Philip Cox]

Hello Jean-Marc, thank you for opening this bug report.

After looking through the logs, it seems that the issue you are hitting
is the out-of-tree driver rtl8821ce you have installed is failing to
build.

If you remove this dkms driver/package, the issue should be resolved.

Also, the rtl8821ce driver should no longer be needed as the device is
supported in the kernel without any additional packages required.  It
looks like the support for the device landed in the kernel in version
5.9.  This is why your original install of 20.04/Focal needed it, as it
was a 5.4 based kernel.  The Noble/24.04 kernel is a 6.8 based kernel,
so it should support the device without needing this additional out of
tree driver.

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

Title:
  package linux-headers-generic 6.8.0-44.44 failed to install/upgrade:
  problèmes de dépendances - laissé non configuré

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Kubuntu 22.04 to 24.04

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: linux-headers-generic 6.8.0-44.44
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  AptOrdering:
   libunbound8:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:jean-marc   1729 F pipewire
   /dev/snd/controlC0:  jean-marc   1733 F wireplumber
  CasperMD5CheckResult: unknown
  Date: Wed Sep 11 09:39:36 2024
  ErrorMessage: problèmes de dépendances - laissé non configuré
  InstallationDate: Installed on 2022-06-25 (809 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  MachineType: Hewlett-Packard HP ProBook 4540s
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-generic 
root=UUID=6265d3a1-c9be-4610-b129-1e89e575c66b 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.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.12-1ubuntu7
  SourcePackage: linux
  Title: package linux-headers-generic 6.8.0-44.44 failed to install/upgrade: 
problèmes de dépendances - laissé non configuré
  UpgradeStatus: Upgraded to noble on 2024-09-05 (5 days ago)
  dmi.bios.date: 04/11/2019
  dmi.bios.release: 15.104
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.68
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 88.33
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.68:bd04/11/2019:br15.104:efr88.33:svnHewlett-Packard:pnHPProBook4540s:pvrA1019D1103:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.21:cvnHewlett-Packard:ct10:cvr:skuC5E25EA#ABF:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 4540s
  dmi.product.sku: C5E25EA#ABF
  dmi.product.version: A1019D1103
  dmi.sys.vendor: Hewlett-Packard
  mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080341/+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 2080341] Re: package linux-headers-generic 6.8.0-44.44 failed to install/upgrade: problèmes de dépendances - laissé non configuré

[Philip Cox]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

Title:
  package linux-headers-generic 6.8.0-44.44 failed to install/upgrade:
  problèmes de dépendances - laissé non configuré

Status in linux package in Ubuntu:
  New

Bug description:
  Kubuntu 22.04 to 24.04

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: linux-headers-generic 6.8.0-44.44
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  AptOrdering:
   libunbound8:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:jean-marc   1729 F pipewire
   /dev/snd/controlC0:  jean-marc   1733 F wireplumber
  CasperMD5CheckResult: unknown
  Date: Wed Sep 11 09:39:36 2024
  ErrorMessage: problèmes de dépendances - laissé non configuré
  InstallationDate: Installed on 2022-06-25 (809 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  MachineType: Hewlett-Packard HP ProBook 4540s
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-generic 
root=UUID=6265d3a1-c9be-4610-b129-1e89e575c66b 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.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.12-1ubuntu7
  SourcePackage: linux
  Title: package linux-headers-generic 6.8.0-44.44 failed to install/upgrade: 
problèmes de dépendances - laissé non configuré
  UpgradeStatus: Upgraded to noble on 2024-09-05 (5 days ago)
  dmi.bios.date: 04/11/2019
  dmi.bios.release: 15.104
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.68
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 88.33
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.68:bd04/11/2019:br15.104:efr88.33:svnHewlett-Packard:pnHPProBook4540s:pvrA1019D1103:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.21:cvnHewlett-Packard:ct10:cvr:skuC5E25EA#ABF:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 4540s
  dmi.product.sku: C5E25EA#ABF
  dmi.product.version: A1019D1103
  dmi.sys.vendor: Hewlett-Packard
  mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080341/+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 2079859] Re: Lenovo V130-15IKB kernel 6.8 not booting from nvme

[Philip Cox]

Hi Paul, I fixed the package that this bug was opened against, so the
apport-collect should now work.  Can you please try running it now?

** Package changed: linux-hwe-6.8 (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/2079859

Title:
  Lenovo V130-15IKB kernel 6.8 not booting from nvme

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to 6.8.0-40, my Lenovo V130-15IKB fails to boot with a
  "nvme failed with error -12" message in dmesg.

  Booting on older 6.5.0-45 goes flawlessly.

  Tryed installing in-proposal 6.8.44 getting the same error as 6.8.40

  Is there a driver problem on 6.8.x, will it be addressed, or should I
  stick to 6.5?

  Thank you very much,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2079859/+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 2080318] Re: BlueField Jammy: call trace RIP: 0010:mlx5_tc_ct_del_ft_cb.part.0+0x17b/0x1c0

[Philip Cox]

** Changed in: linux-bluefield (Ubuntu)
 Assignee: (unassigned) => Bartlomiej Zolnierkiewicz (bzolnier)

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

Title:
  BlueField Jammy: call trace RIP:
  0010:mlx5_tc_ct_del_ft_cb.part.0+0x17b/0x1c0

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  * Intro

  Got call trace RIP below, internal bug ID: 4059202
   [  747.269287] WARNING: CPU: 3 PID: 8360 at 
include/net/netfilter/nf_flow_table.h:261 
mlx5_tc_ct_del_ft_cb.part.0+0x17b/0x1c0 [mlx5_core]

  * Solution
  Need to backport 
  "sched: act_ct: take care of padding in struct zones_ht_key"

  * Full call trace

  3] mlx5_core :08:00.1: mlx5_wait_for_pages:919:(pid 8360): Skipping wait 
for vf pages stage
   [  744.780536] mlx5_core :08:00.1: E-Switch: cleanup
   [  747.086729] mlx5_core :08:00.0: E-Switch: Unload vfs: mode(OFFLOADS), 
nvfs(2), necvfs(0), active vports(2)
   [  747.268720] [ cut here ]
   [  747.269287] WARNING: CPU: 3 PID: 8360 at 
include/net/netfilter/nf_flow_table.h:261 
mlx5_tc_ct_del_ft_cb.part.0+0x17b/0x1c0 [mlx5_core]
   [  747.270709] Modules linked in: rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) 
ib_ipoib(OE) ib_cm(OE) ib_umad(OE) ib_uverbs(OE) fwctl(OE) mlx5_core(OE-) 
mlxfw(OE) auxiliary(OE) mlxdevm(OE) ib_core(OE) memtrack(OE) mlx_compat(OE) 
psample(E) ptp(E) pps_core(E) act_gact(E) act_mirred(E) cls_flower(E) act_ct(E) 
nf_flow_table(E) sch_ingress(E) openvswitch(E) nsh(E) nf_conncount(E) nfsv3(E) 
nfs_acl(E) xt_conntrack(E) xt_MASQUERADE(E) nf_conntrack_netlink(E) 
nfnetlink(E) xt_addrtype(E) iptable_filter(E) iptable_nat(E) nf_nat(E) 
br_netfilter(E) bridge(E) rpcsec_gss_krb5(E) stp(E) llc(E) auth_rpcgss(E) 
nfsv4(E) dns_resolver(E) nfs(E) lockd(E) grace(E) fscache(E) netfs(E) 
overlay(E) rfkill(E) sunrpc(E) kvm_intel(E) iTCO_wdt(E) kvm(E) 
iTCO_vendor_support(E) irqbypass(E) i2c_i801(E) virtio_net(E) pcspkr(E) 
lpc_ich(E) net_failover(E) i2c_smbus(E) mfd_core(E) failover(E) sch_fq_codel(E) 
drm(E) i2c_core(E) ip_tables(E) crc32_pclmul(E) crc32c_intel(E) 
ghash_clmulni_intel(E) sha256_ssse3(E) sha1_ssse3(E)
   [  747.270734]  serio_raw(E) fuse(E) [last unloaded: mlx5_fwctl]
   [  747.280452] CPU: 3 PID: 8360 Comm: modprobe Tainted: G   OE 
5.15.0-1052.39.ga4f8915-bluefield #1
   [  747.281539] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 
rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014
   [  747.282751] RIP: 0010:mlx5_tc_ct_del_ft_cb.part.0+0x17b/0x1c0 [mlx5_core]
   [  747.283557] Code: ff 8b 75 0c 49 8b bd 10 02 00 00 e8 5f d5 fd ff 48 83 
fd 10 77 1b 48 83 c4 28 48 89 ef 5b 5d 41 5c 41 5d 41 5e e9 c5 39 54 e0 <0f> 0b 
e9 14 ff ff ff 48 c7 c7 c0 17 e6 a0 e8 f2 c0 46 ff 85 c0 75
   [  747.285551] RSP: 0018:ffa00141f798 EFLAGS: 00010246
   [  747.286148] RAX:  RBX: ff1100013dc7d040 RCX: 
ff1100013dc7d148
   [  747.286933] RDX: ff1100013dc7ca00 RSI: a0dace30 RDI: 
ff1100013dc7d148
   [  747.287713] RBP: ff1100013dc7ca00 R08:  R09: 
ff110001048dc8a0
   [  747.288498] R10: ff1100011604d9b0 R11: 0001 R12: 
ff1100011f4169f0
   [  747.289279] R13: ff1100011f416800 R14: ff1100013dc7d158 R15: 
ff110001078a
   [  747.290060] FS:  7f51138e0740() GS:ff1100085f6c() 
knlGS:
   [  747.290962] CS:  0010 DS:  ES:  CR0: 80050033
   [  747.291611] CR2: 56383bead180 CR3: 000101a7a006 CR4: 
00771ee0
   [  747.292395] DR0:  DR1:  DR2: 

   [  747.293186] DR3:  DR6: fffe07f0 DR7: 
0400
   [  747.293966] PKRU: 5554
   [  747.294308] Call Trace:
   [  747.294630]  
   [  747.294916]  ? __warn+0x7d/0xc0
   [  747.295305]  ? mlx5_tc_ct_del_ft_cb.part.0+0x17b/0x1c0 [mlx5_core]
   [  747.296043]  ? report_bug+0xd0/0x100
   [  747.296479]  ? handle_bug+0x35/0x80
   [  747.296901]  ? exc_invalid_op+0x14/0x70
   [  747.297358]  ? asm_exc_invalid_op+0x16/0x20
   [  747.297853]  ? mlx5_tc_ct_block_flow_offload_add+0xa70/0xa70 [mlx5_core]
   [  747.298640]  ? mlx5_tc_ct_del_ft_cb.part.0+0x17b/0x1c0 [mlx5_core]
   [  747.299371]  ? mlx5_tc_ct_del_ft_cb.part.0+0x4c/0x1c0 [mlx5_core]
   [  747.300092]  ? mapping_remove+0x108/0x130 [mlx5_core]
   [  747.300718]  mlx5_tc_ct_delete_flow+0x7a/0xa0 [mlx5_core]
   [  747.301379]  mlx5_free_flow_attr_actions+0xea/0x2a0 [mlx5_core]
   [  747.302089]  mlx5e_tc_del_fdb_flow+0x199/0x400 [mlx5_core]
   [  747.302754]  mlx5e_flow_put+0x25/0x90 [mlx5_core]
   [  747.303338]  mlx5e_delete_flower+0x1fe/0x280 [mlx5_core]
   [  747.303983]  tc_setup_cb_reoffload+0x20/0x80
   [  747.304487]  fl_reoffload+0x25b/0x310 [cls_flower]
   [  747.305096]  ? mlx5e_rep_setup_ft_cb+0x150/0x150 [mlx5_core]
   [  747.305781]  ? mlx5e_rep_setup_ft_cb+0x150/0x150 [mlx5_core]
   [ 

[Kernel-packages] [Bug 2080413] Re: package linux-generic 6.8.0-44.44 failed to install/upgrade: priklausomybių problemos - paliekamas nekonfigūruotas

[Philip Cox]

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

** This bug has been marked a duplicate of bug 2080412
   package linux-headers-generic 6.8.0-44.44 failed to install/upgrade: 
priklausomybių problemos - paliekamas nekonfigūruotas

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

Title:
  package linux-generic 6.8.0-44.44 failed to install/upgrade:
  priklausomybių problemos - paliekamas nekonfigūruotas

Status in linux package in Ubuntu:
  New

Bug description:
  Attaching...

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: linux-generic 6.8.0-44.44
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  povilas1707 F pulseaudio
   /dev/snd/controlC1:  povilas1707 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Wed Sep 11 20:08:46 2024
  ErrorMessage: priklausomybių problemos - paliekamas nekonfigūruotas
  InstallationDate: Installed on 2024-09-09 (2 days ago)
  InstallationMedia: Ubuntu-Unity 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827)
  MachineType: LENOVO 20EY000XUK
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-41-generic 
root=UUID=92cc5d6f-191a-4776-aa58-29cb7a99ceee ro quiet 
cryptdevice=UUID=010f9314-56dd-41b8-a919-33af7db7c5c7:luks-010f9314-56dd-41b8-a919-33af7db7c5c7
 root=/dev/mapper/luks-010f9314-56dd-41b8-a919-33af7db7c5c7 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.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.12-1ubuntu7
  SourcePackage: linux
  Title: package linux-generic 6.8.0-44.44 failed to install/upgrade: 
priklausomybių problemos - paliekamas nekonfigūruotas
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2018
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R01ET42W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EY000XUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrR01ET42W(1.22):bd04/25/2018:br1.22:efr1.22:svnLENOVO:pn20EY000XUK:pvrThinkPadE565:rvnLENOVO:rn20EY000XUK:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20EY_BU_Think_FM_ThinkPadE565:
  dmi.product.family: ThinkPad E565
  dmi.product.name: 20EY000XUK
  dmi.product.sku: LENOVO_MT_20EY_BU_Think_FM_ThinkPad E565
  dmi.product.version: ThinkPad E565
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080413/+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 2080405] Re: package linux-image-6.8.0-44-generic 6.8.0-44.44 failed to install/upgrade: triggers looping, abandoned

[Philip Cox]

Hello, thank you for opening this bug report.

Unfortunately, the out of tree amdgpu driver you are trying to use is
the cause of this issue.   If you uninstall the  package, and retry the
installation, it should work.

You may also be able to update the amdgpu driver to see if that fixes
it, but it still isn't an Ubuntu supported driver.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

Title:
  package linux-image-6.8.0-44-generic 6.8.0-44.44 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Invalid

Bug description:
  error when upgrading to ubuntu 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-44-generic 6.8.0-44.44
  ProcVersionSignature: Ubuntu 5.15.0-119.129-generic 5.15.160
  Uname: Linux 5.15.0-119-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nash   2514 F pulseaudio
   /dev/snd/controlC0:  nash   2514 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Wed Sep 11 11:06:44 2024
  ErrorMessage: triggers looping, abandoned
  HibernationDevice: RESUME=UUID=41b51a45-1c0e-4d8b-8bcc-146df09b5e2a
  InstallationDate: Installed on 2017-10-22 (2516 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 80M8
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-119-generic 
root=UUID=12703e1c-0d6e-4ada-b9b3-1311ca7dd458 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.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-6.8.0-44-generic 6.8.0-44.44 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to noble on 2024-09-11 (0 days ago)
  dmi.bios.date: 02/18/2016
  dmi.bios.release: 1.64
  dmi.bios.vendor: Lenovo
  dmi.bios.version: C3CN64WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo G51-35
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G51-35
  dmi.ec.firmware.release: 1.64
  dmi.modalias: 
dmi:bvnLenovo:bvrC3CN64WW:bd02/18/2016:br1.64:efr1.64:svnLENOVO:pn80M8:pvrLenovoG51-35:rvnLENOVO:rnLenovoG51-35:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoG51-35:skuLENOVO_MT_80M8_BU_idea_FM_LenovoG51-35:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80M8
  dmi.product.sku: LENOVO_MT_80M8_BU_idea_FM_Lenovo G51-35
  dmi.product.version: Lenovo G51-35
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.init.d.apport: 2024-07-22T09:59:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080405/+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 2080412] Re: package linux-headers-generic 6.8.0-44.44 failed to install/upgrade: priklausomybių problemos - paliekamas nekonfigūruotas

[Philip Cox]

Hello, Povilas, thank you for taking the time to open this bug report.

The issue is being caused by the out-of-tree amdgpu driver you have
installed on your system.  If you remove it, and then retry the
install/upgrade it should fix the problem.


** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

Title:
  package linux-headers-generic 6.8.0-44.44 failed to install/upgrade:
  priklausomybių problemos - paliekamas nekonfigūruotas

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Unavailable...

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: linux-headers-generic 6.8.0-44.44
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  povilas1707 F pulseaudio
   /dev/snd/controlC1:  povilas1707 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Wed Sep 11 20:08:46 2024
  ErrorMessage: priklausomybių problemos - paliekamas nekonfigūruotas
  InstallationDate: Installed on 2024-09-09 (2 days ago)
  InstallationMedia: Ubuntu-Unity 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827)
  MachineType: LENOVO 20EY000XUK
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-41-generic 
root=UUID=92cc5d6f-191a-4776-aa58-29cb7a99ceee ro quiet 
cryptdevice=UUID=010f9314-56dd-41b8-a919-33af7db7c5c7:luks-010f9314-56dd-41b8-a919-33af7db7c5c7
 root=/dev/mapper/luks-010f9314-56dd-41b8-a919-33af7db7c5c7 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.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.12-1ubuntu7
  SourcePackage: linux
  Title: package linux-headers-generic 6.8.0-44.44 failed to install/upgrade: 
priklausomybių problemos - paliekamas nekonfigūruotas
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2018
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R01ET42W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EY000XUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrR01ET42W(1.22):bd04/25/2018:br1.22:efr1.22:svnLENOVO:pn20EY000XUK:pvrThinkPadE565:rvnLENOVO:rn20EY000XUK:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20EY_BU_Think_FM_ThinkPadE565:
  dmi.product.family: ThinkPad E565
  dmi.product.name: 20EY000XUK
  dmi.product.sku: LENOVO_MT_20EY_BU_Think_FM_ThinkPad E565
  dmi.product.version: ThinkPad E565
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080412/+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 2080219] Re: Ubuntu 24.04 stuck

[Philip Cox]

Hello Rinad, thank you for taking the time to open this bug report.

Unfortunately there is not enough info for us to go on, to look into
this issue yet.

Can you please run "apport-collect 2080219" to include the logs and
other data that we meed to look into this please?

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

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

Title:
  Ubuntu 24.04 stuck

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Regularly Ubuntu 22.04 has stuck and does not show panel buttons images 
(restart, shutdown etc)
  If you try to restart computer it runs slow shutdown process and stuck with 
repeating:
  ```
  09:39:23 kernel: Call Trace:
  09:39:23 kernel: DR3:  DR6: fffe0ff0 DR7: 
0400
  09:39:23 kernel: DR0:  DR1:  DR2: 

  09:39:23 kernel: CR2: 00c00026b010 CR3: 000b6743c005 CR4: 
003706f0
  09:39:23 kernel: CS:  0010 DS:  ES:  CR0: 80050033
  09:39:23 kernel: FS:  () GS:8fa70c30() 
knlGS:
  09:39:23 kernel: R13: d818ff680300 R14:  R15: 
8f9bc0e0f000
  09:39:23 kernel: R10:  R11:  R12: 
001d
  09:39:23 kernel: RBP: b81901e23d88 R08:  R09: 
001e8480
  09:39:23 kernel: RDX:  RSI: 001d RDI: 
8f9bc56ab000
  09:39:23 kernel: RAX: 8f9bc56ab000 RBX: 001d RCX: 
8f9bccd2
  09:39:23 kernel: RSP: 0018:b81901e23d20 EFLAGS: 0087
  09:39:23 kernel: Code: e4 4c 03 2c c5 e0 7c b3 9b 49 8b 87 00 06 00 00 49 89 
c7 48 89 f8 e9 a9 00 00 00 48 83 fb 36 0f 83 bf 0a 00 00 49 8b 54 dd 18 <48> 83 
fb 35 0f 83 58 0b 00 00 4f 8b 84 e5 70 02 00 00 4c 39 c2 74
  09:39:23 kernel: RIP: 0010:mem_cgroup_css_rstat_flush+0x6d/0xc00
  09:39:23 kernel: Workqueue: events_unbound flush_memcg_stats_dwork
  09:39:23 kernel: Hardware name: LENOVO 20N3S5EF0H/20N3S5EF0H, BIOS N2IETA5W 
(1.83 ) 06/20/2024
  09:39:23 kernel: CPU: 2 PID: 12242 Comm: kworker/u16:4 Tainted: GW  
OE  6.8.0-41-generic #41-Ubuntu
  09:39:23 kernel: NMI backtrace for cpu 2
  09:39:23 kernel: Sending NMI from CPU 1 to CPUs 2:
  09:39:23 kernel: rcu: blocking rcu_node structures (internal RCU debug):
  09:36:22 kernel: NMI backtrace for cpu 4 skipped: idling at 
intel_idle+0x72/0xe0
  09:36:22 kernel: Sending NMI from CPU 1 to CPUs 4:
  09:36:22 kernel: NMI backtrace for cpu 2 skipped: idling at 
intel_idle+0x72/0xe0
  09:36:22 kernel: Sending NMI from CPU 1 to CPUs 2:
  09:36:22 kernel: rcu: blocking rcu_node structures (internal RCU debug):
  09:33:22 kernel: NMI backtrace for cpu 4 skipped: idling at 
intel_idle+0x72/0xe0
  09:33:22 kernel: Sending NMI from CPU 1 to CPUs 4:
  09:33:22 kernel:  

  ```

  And also I have found messages like this:
  ```
  сен 10 05:27:52 rinad-ThinkPad-T490 systemd[1]: Stopping 
NetworkManager.service - Network Manager...
  сен 10 05:29:22 rinad-ThinkPad-T490 systemd[1]: NetworkManager.service: State 
'stop-sigterm' timed out. Killing.
  сен 10 05:29:22 rinad-ThinkPad-T490 systemd[1]: NetworkManager.service: 
Killing process 1163 (NetworkManager) with signal SIGKILL.
  сен 10 05:30:52 rinad-ThinkPad-T490 systemd[1]: NetworkManager.service: 
Processes still around after SIGKILL. Ignoring.
  сен 10 05:32:22 rinad-ThinkPad-T490 systemd[1]: NetworkManager.service: State 
'final-sigterm' timed out. Killing.
  сен 10 05:32:22 rinad-ThinkPad-T490 systemd[1]: NetworkManager.service: 
Killing process 1163 (NetworkManager) with signal SIGKILL.
  сен 10 05:33:52 rinad-ThinkPad-T490 systemd[1]: NetworkManager.service: 
Processes still around after final SIGKILL. Entering failed mode.
  сен 10 05:33:52 rinad-ThinkPad-T490 systemd[1]: NetworkManager.service: 
Failed with result 'timeout'.
  сен 10 05:33:52 rinad-ThinkPad-T490 systemd[1]: NetworkManager.service: Unit 
process 1163 (NetworkManager) remains running after unit stopped.
  сен 10 05:33:52 rinad-ThinkPad-T490 systemd[1]: Stopped 
NetworkManager.service - Network Manager.
  сен 10 05:33:52 rinad-ThinkPad-T490 systemd[1]: NetworkManager.service: 
Consumed 3.842s CPU time, 30.4M memory peak, 0B memory swap peak.
  ```

  and this:
  ```
  01:37:30 gnome-shell: clutter_text_get_editable: assertion 'CLUTTER_IS_TEXT 
(self)' failed
  01:37:29 systemd-logind: Power key pressed short.
  01:37:27 dbus-daemon: [system] Failed to activate service 
'org.freedesktop.PackageKit': timed out (service_start_timeout=25000ms)
  01:37:25 ModemManager:  [base-manager] couldn't create modem for device 
'/sys/devices/pci:00/:00:16.3': 

[Kernel-packages] [Bug 2080182] Re: System hangs after GDM login with 6.8.0 kernel

[Philip Cox]

Hello Radon, thank you for taking the time to open this bug report.

I've read through much of the logs you have provided, and the only thing
that stands out is the segfaults that are happening in the end of the
dmesg file and syslog file.

1)
[  321.304482] zsh[5354]: segfault at 10 ip 6010da089caa sp 
7ffdc1981c00 error 4 in zsh[6010da011000+b9000] likely on CPU 1 (core 0, 
socket 0)

[  321.304508] Code: f6 74 08 85 f6 0f 84 9d 01 00 00 45 31 ed 89 c2 81 e2 ff 
ff bf ff 89 53 10 a9 00 00 00 01 75 0d 48 8b 43 20 44 89 e6 48 89 df  50 10 
48 83 7b 30 00 74 1a 48 8b 7b 08 e8 03 8a f8 ff 48 8b 7b
-

2)
[  378.452809] w[6224]: segfault at 4c ip 56fa7fe66e73 sp 7ffe52a049d0 
error 4 in w[56fa7fe66000+3000] likely on CPU 3 (core 2, socket 0)


[  378.452827] Code: 01 40 0f 84 8f 00 00 00 80 fb 20 0f 84 86 00 00 00 0f be 
fb 49 83 c4 01 e8 3a f6 ff ff 4c 39 65 c8 0f 84 88 00 00 00 45 89 ee <41> 0f b6 
1c 24 84 db 75 ac 45 85 f6 75 6f 4c 8b 2d 58 41 00 00 bf
-

3)
[  978.984338] w[7121]: segfault at 4c ip 5a0e7b31be73 sp 7ffe88ce6f10 
error 4 in w[5a0e7b31b000+3000] likely on CPU 0 (core 0, socket 0)

[  978.984357] Code: 01 40 0f 84 8f 00 00 00 80 fb 20 0f 84 86 00 00 00 0f be 
fb 49 83 c4 01 e8 3a f6 ff ff 4c 39 65 c8 0f 84 88 00 00 00 45 89 ee <41> 0f b6 
1c 24 84 db 75 ac 45 85 f6 75 6f 4c 8b 2d 58 41 00 00 bf


These are very strange.  Having segfaults in zsh, and w should not be
happening.  The "error 4" means it is trying to read a user-mode page
which cannot be found.

Looking at these 3 segfaults:

1) zsh is trying to access the memory address 0x10  and is causing a user page 
fault.
2) w is trying to access the memory address 0x4c and is causing a user page 
fault.
3) w is again trying to access memory at 0x4c and is causing a user page fault.


Memory addresses 0x10 and 0x4c aren't valid addresses, and this is causing the 
error.

This is usually caused by a failing/faulty disk, or memory.


Everything may have been fine when you where running 22.04, but during the 
upgrade to 24.04 something was corrupted either by faulty memory, or a faulty 
drive.

This means that you will likely hit these same errors repeatability
because corrupted versions have been written to disk.  This can be seen
by the "w" command having the same "Code" and trapping on the same 0x4c
address.

You should download a copy of memtest86 and try running it on your
system, and see if your ram is alright.  You should also boot off of a
live USB and check the SMART data of your HDD and make sure it is fine.
Perhaps copy your data off to another drive if possible.  You can also
run fsck to try to check the disk.

If the memory and disk check out fine, please let me know and I can
continue to help with this.

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

Title:
  System hangs after GDM login with 6.8.0 kernel

Status in linux package in Ubuntu:
  New

Bug description:
  I recently upgraded a working system from Ubuntu 22.04 to 24.04. After
  the upgrade, the system has acquired an eagerness to become completely
  nonresponsive about a minute after logging in to a graphical session.
  Logging in via console/SSH does not trigger hangs as quickly but they
  still occur within a few hours typically. When logging in to a
  graphical session, I notice immediately that performance and
  responsiveness is heavily degraded, and within moments, the entire
  system locks up. Any existing SSH sessions immediately stop
  responding, and the display freezes on whatever it was previously
  displaying. No keyboard or mouse input has any observable effect on
  the system, and it must be powered off manually.

  The system does not reboot automatically nor does it power off. I
  configured linux-crashdump and triggered a kernel panic to verify that
  dump files can be written successfully. However, they are not written
  on this hang, implying that it is not a kernel crash.

  The new Linux kernel version is 6.8.0-41, while the old kernel
  6.5.0-45 is still installed. When booting into the older kernel
  version (no other changes), these symptoms do not occur and function
  is as it was before the 24.04 upgrade.

  Seeing LP#2073358, I tested linux-oem-6.8/6.8.0-1011.11 but this has
  the same behavior as 6.8.0-41-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-41-generic 6.8.0-41.41
  ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-45-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raxod502   1884 F wireplumber
   /dev/snd/seq:raxod502   1880 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Mon Sep  9 17:51:02 2024
  InstallationDate: Installed on 2022-10-28 (683 days ago)
  InstallationMedia: Ub

[Kernel-packages] [Bug 2080182] Re: System hangs after GDM login with 6.8.0 kernel

[Philip Cox]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

Title:
  System hangs after GDM login with 6.8.0 kernel

Status in linux package in Ubuntu:
  New

Bug description:
  I recently upgraded a working system from Ubuntu 22.04 to 24.04. After
  the upgrade, the system has acquired an eagerness to become completely
  nonresponsive about a minute after logging in to a graphical session.
  Logging in via console/SSH does not trigger hangs as quickly but they
  still occur within a few hours typically. When logging in to a
  graphical session, I notice immediately that performance and
  responsiveness is heavily degraded, and within moments, the entire
  system locks up. Any existing SSH sessions immediately stop
  responding, and the display freezes on whatever it was previously
  displaying. No keyboard or mouse input has any observable effect on
  the system, and it must be powered off manually.

  The system does not reboot automatically nor does it power off. I
  configured linux-crashdump and triggered a kernel panic to verify that
  dump files can be written successfully. However, they are not written
  on this hang, implying that it is not a kernel crash.

  The new Linux kernel version is 6.8.0-41, while the old kernel
  6.5.0-45 is still installed. When booting into the older kernel
  version (no other changes), these symptoms do not occur and function
  is as it was before the 24.04 upgrade.

  Seeing LP#2073358, I tested linux-oem-6.8/6.8.0-1011.11 but this has
  the same behavior as 6.8.0-41-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-41-generic 6.8.0-41.41
  ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-45-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raxod502   1884 F wireplumber
   /dev/snd/seq:raxod502   1880 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Mon Sep  9 17:51:02 2024
  InstallationDate: Installed on 2022-10-28 (683 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 3626AL3
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash 
crashkernel=2G-4G:1024M,4G-32G:1024M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-45-generic N/A
   linux-backports-modules-6.5.0-45-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to noble on 2024-09-03 (7 days ago)
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626AL3
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: 20124051
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626AL3:pvrThinkPadX201:rvnLENOVO:rn3626AL3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626AL3
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.init.d.apport: 2024-07-22T07:59:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080182/+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 2080414] [NEW] [N][AWS]Backport x86/kaslr fix impacting ML/HPC workloads

[Philip Cox]

Public bug reported:

SRU Justification:

[Impact]

EC2 team discovered a Linux bug during ML/HPC workload testing on P5
instances. The issue is described at
https://lore.kernel.org/all/87ed6soy3z.ffs@tglx/ ("iounmap() on x86
occasionally fails to unmap because the provided valid ioremap address
is not below high_memory.").

[Fix]

This is fixed by upstream commit
ea72ce5da22806d5713f3ffb39a6d5ae73841f93:

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

[Test Plan]

AWS tested

[Where problems could occur]

If there was code that made incorrect assumptions on how memory was laid
out and used, it might break the functionality, but seeing as this is
fixing an error, the chances of that should be fairly low.


[Other Info]
SF #00392654

** Affects: linux-aws (Ubuntu)
 Importance: High
 Status: Fix Released

** Affects: linux-aws (Ubuntu Noble)
 Importance: Undecided
 Assignee: Philip Cox (philcox)
 Status: In Progress

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

** Changed in: linux-aws (Ubuntu)
   Status: New => In Progress

** Changed in: linux-aws (Ubuntu)
   Status: In Progress => New

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

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

** Changed in: linux-aws (Ubuntu)
     Assignee: Philip Cox (philcox) => (unassigned)

** Changed in: linux-aws (Ubuntu Noble)
 Assignee: (unassigned) => Philip Cox (philcox)

** Changed in: linux-aws (Ubuntu Noble)
   Status: New => In Progress

** Description changed:

  SRU Justification:
  
  [Impact]
  
  EC2 team discovered a Linux bug during ML/HPC workload testing on P5
  instances. The issue is described at
  https://lore.kernel.org/all/87ed6soy3z.ffs@tglx/ ("iounmap() on x86
  occasionally fails to unmap because the provided valid ioremap address
  is not below high_memory.").
  
- 
  [Fix]
  
  This is fixed by upstream commit
  ea72ce5da22806d5713f3ffb39a6d5ae73841f93:
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ea72ce5da22806d5713f3ffb39a6d5ae73841f93
- 
  
  [Test Plan]
  
  AWS tested
  
  [Where problems could occur]
  
  If there was code that made incorrect assumptions on how memory was laid
  out and used, it might break the functionality, but seeing as this is
  fixing an error, the chances of that should be fairly low.
+ 
+ 
+ [Other Info]
+ SF #00392654

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

Title:
  [N][AWS]Backport x86/kaslr fix impacting ML/HPC workloads

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Noble:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

  EC2 team discovered a Linux bug during ML/HPC workload testing on P5
  instances. The issue is described at
  https://lore.kernel.org/all/87ed6soy3z.ffs@tglx/ ("iounmap() on x86
  occasionally fails to unmap because the provided valid ioremap address
  is not below high_memory.").

  [Fix]

  This is fixed by upstream commit
  ea72ce5da22806d5713f3ffb39a6d5ae73841f93:

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

  [Test Plan]

  AWS tested

  [Where problems could occur]

  If there was code that made incorrect assumptions on how memory was
  laid out and used, it might break the functionality, but seeing as
  this is fixing an error, the chances of that should be fairly low.

  
  [Other Info]
  SF #00392654

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2080414/+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 2076217] Re: booting an 24.10 or 24.04 ec2 instance with SEV-SNP enabled hangs sometimes

[Philip Cox]

The pause is happening in the code that inits the APIC.

Its after the APIC is set up when it is beginning to init the x2APIC.

It is timing related, and when I add  a lot of print statements to the
code, the problem goes away.  So, its been fun trying to narrow it down.
I have it narrowed down somewhat now.  I tested with the oracular:linux
6.11 kernel, and it still has the pause.  I tested the jammy:aws-6.5
kernel, and it seems to run fine.

Rather than debugging the  6.8 kernel, which is very time consuming, I
will do the following in parallel:

1) I will try to do a bisect between the 6.5 and 6.8 kernels to find the 
regression point
2) I will examine the commits between 6.5 and 6.8 that touched the APIC code, 
and see if any stand out to be the root cause.

One of these should get the answer.

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

** Changed in: linux-aws (Ubuntu)
   Status: New => In Progress

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

Title:
  booting an 24.10 or 24.04 ec2 instance with SEV-SNP enabled hangs
  sometimes

Status in cloud-images:
  New
Status in linux-aws package in Ubuntu:
  In Progress

Bug description:
  I'm trying to test an EC2 instance with SEV-SNP enabled. But the boot
  process hangs at:

  [snipped]
  [0.609079] printk: legacy console [ttyS0] enabled
  [5.405931] ACPI: Core revision 20230628
  [5.430448] clocksource: hpet: mask: 0x max_cycles: 0x, 
max_idle_ns: 30580167144 ns
  [5.473066] APIC: Switch to symmetric I/O mode setup

  
  Steps to reproduce are:

  $ AWS_DEFAULT_REGION=eu-west-1 aws ec2 run-instances --image-id
  ami-005a44922e2ffd1fa --instance-type m6a.large --cpu-options
  AmdSevSnp=enabled --key-name toabctl --tag-specifications
  'ResourceType=instance,Tags=[{Key=Name,Value=toabctl-2410-sevsnp-
  testing}]'

  The AMI ami-005a44922e2ffd1fa is ubuntu/images-testing/hvm-ssd-
  gp3/ubuntu-oracular-daily-amd64-server-20240716 and does contain
  6.8.0-1008-aws .

  Attached is the full output from the EC2 serial console.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2076217/+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 2077145] Re: GDS force mitigation re-enabled in 6.10 (and 6.11) causing crashes

[Philip Cox]

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

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

Title:
  GDS force mitigation re-enabled in 6.10 (and 6.11) causing crashes

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  The (supposedly unintended) re-enabling of GDS force migration in the
  Ubuntu 6.10 kernels causes the AVX instruction to be disabled on older
  CPUs which have no available microcode update. This causes various
  programs to crash due to the unconditional use of AVX in libgnutls.so,
  libxul.so, etc.

  Typically "traps" of "invalid opcode" will be seen in dmesg output
  along with the initial notice:

  [0.121833] GDS: Microcode update needed! Disabling AVX as mitigation.
  [0.121835] GDS: Mitigation: AVX disabled, no microcode

  When GDS force mitigation appeared in the kernel, with default "y", it
  created a lot of issues like these and Ubuntu quickly patched all
  their kernels, this from the 6.2.0-28.29_6.2.0-31.31 diff:

  ==

  ```
  diff -u linux-6.2.0/debian.master/changelog 
linux-6.2.0/debian.master/changelog
  --- linux-6.2.0/debian.master/changelog
  +++ linux-6.2.0/debian.master/changelog
  @@ -1,3 +1,13 @@
  +linux (6.2.0-31.31) lunar; urgency=medium
  +
  +  * lunar/linux: 6.2.0-31.31 -proposed tracker (LP: #2031146)
  +
  +  * libgnutls report "trap invalid opcode" when trying to install packages 
over
  +https (LP: #2031093)
  +- [Config]: disable CONFIG_GDS_FORCE_MITIGATION
  +
  + -- Thadeu Lima de Souza Cascardo   Mon, 14 Aug 2023 
08:29:52 -0300
  +
   linux (6.2.0-28.29) lunar; urgency=medium

     * lunar/linux: 6.2.0-28.29 -proposed tracker (LP: #2030547)
  diff -u linux-6.2.0/debian.master/config/annotations 
linux-6.2.0/debian.master/config/annotations
  --- linux-6.2.0/debian.master/config/annotations
  +++ linux-6.2.0/debian.master/config/annotations
  @@ -4992,7 +4992,7 @@
   CONFIG_GCC_VERSION  policy<{'amd64': '120200', 
'arm64': '120200', 'armhf': '120200', 'ppc64el': '120200', 'riscv64': '120200', 
's390x': '120200'}>
   CONFIG_GCOV_KERNEL  policy<{'amd64': 'n', 
'arm64': 'n', 'armhf': 'n', 'ppc64el': 'n', 'riscv64': 'n', 's390x': 'n'}>
   CONFIG_GDB_SCRIPTS  policy<{'amd64': 'y', 
'arm64': 'y', 'armhf': 'y', 'ppc64el': 'y', 'riscv64': 'y', 's390x': 'y'}>
  -CONFIG_GDS_FORCE_MITIGATION policy<{'amd64': 'y'}>
  +CONFIG_GDS_FORCE_MITIGATION policy<{'amd64': 'n'}>
   CONFIG_GEMINI_ETHERNET  policy<{'arm64': 'm', 
'armhf': 'm', 'ppc64el': 'm', 'riscv64': 'm'}>
   CONFIG_GENERIC_ADC_BATTERY  policy<{'amd64': 'm', 
'arm64': 'm', 'armhf': 'm', 'ppc64el': 'm', 'riscv64': 'm'}>
   CONFIG_GENERIC_ADC_THERMAL  policy<{'amd64': 'm', 
'arm64': 'm', 'armhf': 'm', 'ppc64el': 'm', 'riscv64': 'm'}>
  ```

  ==

  In upstream 6.9 the option was renamed from
  CONFIG_GDS_FORCE_MITIGATION to CONFIG_MITIGATION_GDS_FORCE, but when
  Ubuntu jumped from 6.8 to 6.10, this customization was lost, seen in
  the 6.8.0-31.31_6.10.0-15.15 diff:

  ==

   ```
   CONFIG_GDB_SCRIPTS  policy<{'amd64': 'y', 
'arm64': 'y', 'armhf': 'y', 'ppc64el': 'y', 'riscv64': 'y', 's390x': 'y'}>
  -CONFIG_GDS_FORCE_MITIGATION policy<{'amd64': 'n'}>
   CONFIG_GEMINI_ETHERNET  policy<{'arm64': 'm', 
'armhf': 'm', 'ppc64el': 'm', 'riscv64': 'm'}>
  ...
   CONFIG_MITIGATE_SPECTRE_BRANCH_HISTORY  policy<{'arm64': 'y'}>
  +CONFIG_MITIGATION_CALL_DEPTH_TRACKING   policy<{'amd64': 'y'}>
  +CONFIG_MITIGATION_GDS_FORCE policy<{'amd64': 'y'}>
  +CONFIG_MITIGATION_IBPB_ENTRYpolicy<{'amd64': 'y'}>
  +CONFIG_MITIGATION_IBRS_ENTRYpolicy<{'amd64': 'y'}>
  ```

  ==

  I am sure this was an oversight, and that the old option was simply
  dropped because it didn't exist any longer, without thinking of it
  being renamed (among a lot of other renames).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077145/+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 2080181] Re: suspend fails because lockd refuses to freeze

[Philip Cox]

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

Hello Jason, thank you for taking the time to open this bug report.

This is a known issue, and a fix for the failing to suspend on machines
with an NFS share has been submitted and should be released soon.  The
other bug tracking this is:

https://bugs.launchpad.net/bugs/2076576

** Changed in: linux-signed-hwe-5.15 (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

** This bug has been marked a duplicate of bug 2076576
   5.15.0-118: NFS causes suspend to fail

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

Title:
  suspend fails because lockd refuses to freeze

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

Bug description:
  Up to 5.15.0-117-generic (package 5.15.0-117.127), I could reliably
  suspend and restart my computer.  Now with package 5.15.0-119.129, I
  cannot suspend.

  I get this error:

  Sep  8 21:26:35 trotzdem kernel: [ 2365.487773] Freezing user space processes 
... (elapsed 0.003 seconds) done.
  Sep  8 21:26:35 trotzdem kernel: [ 2365.491406] OOM killer disabled.
  Sep  8 21:26:35 trotzdem kernel: [ 2365.491408] Freezing remaining freezable 
tasks ... 
  Sep  8 21:26:35 trotzdem kernel: [ 2385.497718] Freezing of tasks failed 
after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0):
  Sep  8 21:26:35 trotzdem kernel: [ 2385.497884] task:lockd   state:I 
stack:0 pid: 1677 ppid: 2 flags:0x4000
  Sep  8 21:26:35 trotzdem kernel: [ 2385.497893] Call Trace:
  Sep  8 21:26:35 trotzdem kernel: [ 2385.497898]  
  Sep  8 21:26:35 trotzdem kernel: [ 2385.497904]  __schedule+0x24e/0x590
  Sep  8 21:26:35 trotzdem kernel: [ 2385.497916]  schedule+0x69/0x110
  Sep  8 21:26:35 trotzdem kernel: [ 2385.497922]  schedule_timeout+0x105/0x140
  Sep  8 21:26:35 trotzdem kernel: [ 2385.497931]  svc_get_next_xprt+0xf1/0x190 
[sunrpc]
  Sep  8 21:26:35 trotzdem kernel: [ 2385.498041]  svc_recv+0x1a9/0x330 [sunrpc]
  Sep  8 21:26:35 trotzdem kernel: [ 2385.498142]  lockd+0xa9/0x1c0 [lockd]
  Sep  8 21:26:35 trotzdem kernel: [ 2385.498162]  ? set_grace_period+0xa0/0xa0 
[lockd]
  Sep  8 21:26:35 trotzdem kernel: [ 2385.498179]  kthread+0x12a/0x150
  Sep  8 21:26:35 trotzdem kernel: [ 2385.498188]  ? 
set_kthread_struct+0x50/0x50
  Sep  8 21:26:35 trotzdem kernel: [ 2385.498196]  ret_from_fork+0x22/0x30
  Sep  8 21:26:35 trotzdem kernel: [ 2385.498206]  
  Sep  8 21:26:35 trotzdem kernel: [ 2385.498450] 
  Sep  8 21:26:35 trotzdem kernel: [ 2385.498452] Restarting kernel threads ... 
  Sep  8 21:26:35 trotzdem kernel: [ 2385.498661] usb 2-1: USB disconnect, 
device number 5
  Sep  8 21:26:35 trotzdem kernel: [ 2385.498756] done.
  Sep  8 21:26:35 trotzdem kernel: [ 2385.498761] OOM killer enabled.

  It is consistently lockd which produces this error.  As far as I know,
  lockd is related to NFS.  This computer is an NFS client.

  I believe the issue started in version 5.15.0-118.128.  I will re-test
  to confirm, then update this report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2080181/+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 2077575] Re: standby broken on ThinkPad 260 Yoga with 6.8

[Philip Cox]

Thank you for providing the updated info.  We will continue the
investigation of this bug.

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/2077575

Title:
  standby broken on ThinkPad 260 Yoga with 6.8

Status in linux package in Ubuntu:
  New

Bug description:
  I'm on Ubuntu 22.04 with HWE, so I recently got the upgrade from 6.5
  to 6.8 and since then, standby doesn't work anymore. The screen goes
  black, the keyboard backlight goes off and the status LED goes from on
  to fading, but the fan and the LEDs on the keyboard stay on.

  The laptop also doesn't wake up anymore.

  The logs end here:

  Aug 21 20:57:20 systemd[1]: Starting System Suspend...
  Aug 21 20:57:20 wpa_supplicant[1259]: wlp4s0: CTRL-EVENT-DSCP-POLICY clear_all
  Aug 21 20:57:20 wpa_supplicant[1259]: wlp4s0: CTRL-EVENT-DSCP-POLICY clear_all
  Aug 21 20:57:20 wpa_supplicant[1259]: nl80211: deinit ifname=wlp4s0 
disabled_11b_rates=0
  Aug 21 20:57:20 systemd[1]: grub-common.service: Deactivated successfully.
  Aug 21 20:57:20 systemd[1]: Finished Record successful boot for GRUB.
  Aug 21 20:57:20 systemd-sleep[2204]: Entering sleep state 'suspend'...
  Aug 21 20:57:20 kernel: PM: suspend entry (deep)

  whereas they continue on 6.5:

  Aug 21 21:03:03 wpa_supplicant[1213]: wlp4s0: CTRL-EVENT-DSCP-POLICY clear_all
  Aug 21 21:03:03 wpa_supplicant[1213]: wlp4s0: CTRL-EVENT-DSCP-POLICY clear_all
  Aug 21 21:03:03 wpa_supplicant[1213]: nl80211: deinit ifname=wlp4s0 
disabled_11b_rates=0
  Aug 21 21:03:03 systemd-sleep[2158]: Entering sleep state 'suspend'...
  Aug 21 21:03:03 kernel: PM: suspend entry (deep)
  Aug 21 21:03:04 kernel: Filesystems sync: 0.392 seconds
  Aug 21 21:03:15 kernel: Freezing user space processes
  Aug 21 21:03:15 kernel: Freezing user space processes completed (elapsed 
0.001 seconds)
  Aug 21 21:03:15 kernel: OOM killer disabled.
  Aug 21 21:03:15 kernel: Freezing remaining freezable tasks
  Aug 21 21:03:15 kernel: Freezing remaining freezable tasks completed (elapsed 
0.001 seconds)
  Aug 21 21:03:15 kernel: printk: Suspending console(s) (use no_console_suspend 
to debug)
  Aug 21 21:03:15 kernel: e1000e: EEE TX LPI TIMER: 0011
  Aug 21 21:03:15 kernel: ACPI: EC: interrupt blocked
  Aug 21 21:03:15 kernel: ACPI: PM: Preparing to enter system sleep state S3
  Aug 21 21:03:15 kernel: ACPI: EC: event blocked
  Aug 21 21:03:15 kernel: ACPI: EC: EC stopped
  Aug 21 21:03:15 kernel: ACPI: PM: Saving platform NVS memory
  Aug 21 21:03:15 kernel: Disabling non-boot CPUs ...
  Aug 21 21:03:15 kernel: smpboot: CPU 1 is now offline
  Aug 21 21:03:15 kernel: smpboot: CPU 2 is now offline
  Aug 21 21:03:15 kernel: smpboot: CPU 3 is now offline
  Aug 21 21:03:15 kernel: ACPI: PM: Low-level resume complete
  Aug 21 21:03:15 kernel: ACPI: EC: EC started
  Aug 21 21:03:15 kernel: ACPI: PM: Restoring platform NVS memory
  Aug 21 21:03:15 kernel: Enabling non-boot CPUs ...
  Aug 21 21:03:15 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
  Aug 21 21:03:15 kernel: CPU1 is up
  Aug 21 21:03:15 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
  Aug 21 21:03:15 kernel: CPU2 is up
  Aug 21 21:03:15 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
  Aug 21 21:03:15 kernel: CPU3 is up
  Aug 21 21:03:15 kernel: ACPI: PM: Waking up from system sleep state S3
  Aug 21 21:03:15 kernel: ACPI: EC: interrupt unblocked
  Aug 21 21:03:15 kernel: ACPI: EC: event unblocked
  Aug 21 21:03:15 kernel: i915 :00:02.0: [drm] [ENCODER:94:DDI A/PHY A] is 
disabled/in DSI mode with an ungated>
  Aug 21 21:03:15 kernel: i915 :00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is 
disabled/in DSI mode with an ungate>
  Aug 21 21:03:15 kernel: i915 :00:02.0: [drm] [ENCODER:117:DDI C/PHY C] is 
disabled/in DSI mode with an ungate>
  Aug 21 21:03:15 kernel: nvme nvme0: Shutdown timeout set to 8 seconds
  Aug 21 21:03:15 kernel: nvme nvme0: 4/0/0 default/read/poll queues
  Aug 21 21:03:15 kernel: thinkpad_acpi: Unknown/reserved multi mode value 
0x for type 4, please report this to ibm-acpi-de...@lists.sourceforge.net
  Aug 21 21:03:15 kernel: usb 1-8: reset high-speed USB device number 3 using 
xhci_hcd
  Aug 21 21:03:15 kernel: usb 1-9: reset full-speed USB device number 4 using 
xhci_hcd
  Aug 21 21:03:15 kernel: OOM killer enabled.
  Aug 21 21:03:15 kernel: Restarting tasks ... done.
  Aug 21 21:03:15 kernel: random: crng reseeded on system resumption
  Aug 21 21:03:15 kernel: kauditd_printk_skb: 14405 callbacks suppressed
  Aug 21 21:03:15 systemd-resolved[708]: Clock change detected. Flushing caches.
  Aug 21 21:03:15 systemd-sleep[2158]: System returned from sleep state.
  Aug 21 21:03:15 kernel: PM: suspend exit
  Aug 21 21:03:15 systemd[1]: systemd-suspend.service: Deactivated successfully.
  Aug 21 21:03:15 systemd[1]: Finished System Suspend.
  Aug 21 21:03:15

[Kernel-packages] [Bug 2077260] Re: freeze after updating to newest kernel on log in sreen or just after log in (6.8.0-45 ?). Had to use Grub to restero to 6.5.0-45

[Philip Cox]

Thank you for updating the info as requested.  We will  continue to
investigate this issue.

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/2077260

Title:
  freeze after updating to newest kernel on log in sreen or just after
  log in (6.8.0-45 ?). Had to use Grub to restero to 6.5.0-45

Status in linux package in Ubuntu:
  New

Bug description:
  freeze after updating to newest kernel on log in sreen or just after
  log in (6.8.0-45 ?). Had to use Grub to rester to 6.5.0-45

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-45-generic 6.5.0-45.45~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 18 15:53:56 2024
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michal 2670 F wireplumber
   /dev/snd/seq:michal 2665 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  MachineType: Hewlett-Packard HP G62 Notebook PC
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-45-generic 
root=UUID=62689215-60a8-4e0a-8e4e-fb3115fd7b88 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-45-generic N/A
   linux-backports-modules-6.5.0-45-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.2
  Tags: noble wayland-session
  Uname: Linux 6.5.0-45-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: 10/29/2010
  dmi.bios.release: 15.37
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.37
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1439
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 60.3F
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 60.63
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.37:bd10/29/2010:br15.37:efr60.63:svnHewlett-Packard:pnHPG62NotebookPC:pvr059411252710001020100:rvnHewlett-Packard:rn1439:rvr60.3F:cvnHewlett-Packard:ct10:cvrChassisVersion:skuLD667EA#AKD:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP G62 Notebook PC
  dmi.product.sku: LD667EA#AKD
  dmi.product.version: 059411252710001020100
  dmi.sys.vendor: Hewlett-Packard
  mtime.conffile..etc.init.d.apport: 2024-07-22T14:59:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077260/+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 2079246] Re: System hanging at startup after seeing the line "Listening on Load/save RF Kill Switch Status" in console

[Philip Cox]

Thank you for updating this ticket.  We will continue with investigating
this issue.

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/2079246

Title:
  System hanging at startup after seeing the line "Listening on
  Load/save RF Kill Switch Status" in console

Status in linux package in Ubuntu:
  New

Bug description:
  Hi, the system just hangs. When choosing not to use quiet & splash
  options on boot, I can see the last line before complete freeze, which
  starts with "Listening on Load/save RF Kill Switch Status". After
  that, a hard reboot is needed.

  I can boot on previous kernel without problem (linux-
  image-6.5.0-45-generic).

  After booting with previous kernel, all I can see in dmesg, near the end, is :
  [   20.115597] nouveau :01:00.0: Direct firmware load for 
nouveau/nv98_fuc084 failed with error -2
  [   20.115640] nouveau :01:00.0: Direct firmware load for 
nouveau/nv98_fuc084d failed with error -2
  [   20.115643] nouveau :01:00.0: msvld: unable to load firmware data
  [   20.115646] nouveau :01:00.0: msvld: init failed, -19

  I'm not skilled enough to say whether it's relevant or not.

  My computer is an old HP 6200 MT with Intel Core i7-2600 and a Nvidia
  Geforce 8400GS additional graphic card. If I can help furthermore by
  providing any additional information, I will do it.

  I found two topis on the web where similar issues are reported :
  
https://www.reddit.com/r/archlinux/comments/1dusm7g/os_booting_stuck_at_ok_started_load_save_rf_kill/
  
https://askubuntu.com/questions/1524855/kubuntu-22-04-problem-with-kernel-6-8-0-after-update-from-kernel-6-5-0-45-to-6

  Thx !
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christele   1894 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-09-23 (350 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Hewlett-Packard HP Compaq 6200 Pro MT PC
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-45-generic 
root=UUID=caebb7ef-3a0b-4a41-8dbb-d64e6eae70a6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-45-generic N/A
   linux-backports-modules-6.5.0-45-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.31
  RfKill:
   
  Tags:  jammy
  Uname: Linux 6.5.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/04/2016
  dmi.bios.release: 2.29
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.29
  dmi.board.asset.tag: CZC2214XXD
  dmi.board.name: 1497
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC2214XXD
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.29:bd04/04/2016:br2.29:svnHewlett-Packard:pnHPCompaq6200ProMTPC:pvr:rvnHewlett-Packard:rn1497:rvr:cvnHewlett-Packard:ct6:cvr:skuXL504AV:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq 6200 Pro MT PC
  dmi.product.sku: XL504AV
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2079246/+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 2076986] Re: Lenovo Touchpad not working or detected in 'Lenovo Legion 9 16IRX9' following Ubuntu 22.04 installation.

[Philip Cox]

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Lenovo Touchpad not working or detected in 'Lenovo Legion 9 16IRX9'
  following Ubuntu 22.04 installation.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Legion 9 touchpad on my laptop is unresponsive after
  installing Ubuntu 22.04. How might I get it working again? A lot of
  solutions suggested to downgrade the kernel but the posts I found were
  from 2+ years ago.

  Below is the output from 'cat /proc/bus/input/devices'. Note that the
  Logitech mouse is a (functional) wired mouse I was using at the time.

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
  U: Uniq=
  H: Handlers=kbd event0
  B: PROP=0
  B: EV=3
  B: KEY=8000 10 0

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
  U: Uniq=
  H: Handlers=event1
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2
  B: PROP=0
  B: EV=3
  B: KEY=8000 10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=046d Product=c050 Version=0110
  N: Name="Logitech USB-PS/2 Optical Mouse"
  P: Phys=usb-:00:14.0-4/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:046D:C050.0003/input/input4
  U: Uniq=
  H: Handlers=mouse0 event4
  B: PROP=0
  B: EV=17
  B: KEY=ff 0 0 0 0
  B: REL=1943
  B: MSC=10

  I: Bus=0003 Vendor=048d Product=c990 Version=0110
  N: Name="ITE Tech. Inc. ITE Device(8258) Keyboard"
  P: Phys=usb-:00:14.0-6/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:048D:C990.0004/input/input5
  U: Uniq=
  H: Handlers=sysrq kbd event5 leds
  B: PROP=0
  B: EV=12001f
  B: KEY=33eff 0 0 48317aff32d bfd6 1 130c730b17c007 
ffbf7bfad9415fff febeffdfffef fffe
  B: REL=1040
  B: ABS=1
  B: MSC=10
  B: LED=1f

  I: Bus=0003 Vendor=048d Product=c990 Version=0110
  N: Name="ITE Tech. Inc. ITE Device(8258)"
  P: Phys=usb-:00:14.0-6/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:048D:C990.0004/input/input6
  U: Uniq=
  H: Handlers=event6
  B: PROP=0
  B: EV=9
  B: ABS=100

  I: Bus=0003 Vendor=048d Product=c990 Version=0110
  N: Name="ITE Tech. Inc. ITE Device(8258) Wireless Radio Control"
  P: Phys=usb-:00:14.0-6/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:048D:C990.0004/input/input7
  U: Uniq=
  H: Handlers=rfkill kbd event7
  B: PROP=0
  B: EV=13
  B: KEY=80 0 0 0
  B: MSC=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input8
  U: Uniq=
  H: Handlers=event8
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input9
  U: Uniq=
  H: Handlers=event9
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=8"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input10
  U: Uniq=
  H: Handlers=event10
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=9"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input11
  U: Uniq=
  H: Handlers=event11
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:03/LNXVIDEO:00/input/input12
  U: Uniq=
  H: Handlers=kbd event12
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input13
  U: Uniq=
  H: Handlers=kbd event13
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus= Vendor= Product= Version

[Kernel-packages] [Bug 2076986] Re: Lenovo Touchpad not working or detected in 'Lenovo Legion 9 16IRX9' following Ubuntu 22.04 installation.

[Philip Cox]

Hi Cara and Davide, I am the same person handling both of these tickets,
so I will merge them.

So, from my understanding, the trackpad does not work in 22.04 when
using kernel linux-image-6.8.0-40-generic.

When booting a live USB install image, the trackpad doesn't work either.
The install image is likely using 6.8.0-31.

After Davide did a complete install, and update (i assume), everything
worked.  The newest 6.8 kernel available in -updates is 6.8.0-41.   This
kernel will be available for both Jammy installs (22.04) and Noble
installs (24.04).

It sounded like  in Comment #21
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2079985/comments/21
that it worked after installing and updating.

Could you please both update your systems and see if that resolves this?

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

Title:
  Lenovo Touchpad not working or detected in 'Lenovo Legion 9 16IRX9'
  following Ubuntu 22.04 installation.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Legion 9 touchpad on my laptop is unresponsive after
  installing Ubuntu 22.04. How might I get it working again? A lot of
  solutions suggested to downgrade the kernel but the posts I found were
  from 2+ years ago.

  Below is the output from 'cat /proc/bus/input/devices'. Note that the
  Logitech mouse is a (functional) wired mouse I was using at the time.

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
  U: Uniq=
  H: Handlers=kbd event0
  B: PROP=0
  B: EV=3
  B: KEY=8000 10 0

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
  U: Uniq=
  H: Handlers=event1
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2
  B: PROP=0
  B: EV=3
  B: KEY=8000 10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=046d Product=c050 Version=0110
  N: Name="Logitech USB-PS/2 Optical Mouse"
  P: Phys=usb-:00:14.0-4/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:046D:C050.0003/input/input4
  U: Uniq=
  H: Handlers=mouse0 event4
  B: PROP=0
  B: EV=17
  B: KEY=ff 0 0 0 0
  B: REL=1943
  B: MSC=10

  I: Bus=0003 Vendor=048d Product=c990 Version=0110
  N: Name="ITE Tech. Inc. ITE Device(8258) Keyboard"
  P: Phys=usb-:00:14.0-6/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:048D:C990.0004/input/input5
  U: Uniq=
  H: Handlers=sysrq kbd event5 leds
  B: PROP=0
  B: EV=12001f
  B: KEY=33eff 0 0 48317aff32d bfd6 1 130c730b17c007 
ffbf7bfad9415fff febeffdfffef fffe
  B: REL=1040
  B: ABS=1
  B: MSC=10
  B: LED=1f

  I: Bus=0003 Vendor=048d Product=c990 Version=0110
  N: Name="ITE Tech. Inc. ITE Device(8258)"
  P: Phys=usb-:00:14.0-6/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:048D:C990.0004/input/input6
  U: Uniq=
  H: Handlers=event6
  B: PROP=0
  B: EV=9
  B: ABS=100

  I: Bus=0003 Vendor=048d Product=c990 Version=0110
  N: Name="ITE Tech. Inc. ITE Device(8258) Wireless Radio Control"
  P: Phys=usb-:00:14.0-6/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:048D:C990.0004/input/input7
  U: Uniq=
  H: Handlers=rfkill kbd event7
  B: PROP=0
  B: EV=13
  B: KEY=80 0 0 0
  B: MSC=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input8
  U: Uniq=
  H: Handlers=event8
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input9
  U: Uniq=
  H: Handlers=event9
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=8"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input10
  U: Uniq=
  H: Handlers=event10
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=9"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01

[Kernel-packages] [Bug 2079985] Re: Lenovo Legion 9 16IRX9 - Touchpad is missing on Ubuntu 22.04+

[Philip Cox]

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

** This bug has been marked a duplicate of bug 2076986
   Lenovo Touchpad not working or detected in 'Lenovo Legion 9 16IRX9' 
following Ubuntu 22.04 installation.

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

Title:
  Lenovo Legion 9 16IRX9 - Touchpad is missing on Ubuntu 22.04+

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brand new Lenovo Legion 9 16IRX9. It doesn't seem to detect any touchpad. 
  I also tested PopOS 24.04 liveUSB and it doesn't work.
  In Windows 11 it works.

  user@lenovo-Legion-9-16IRX9:~$ neofetch 
  .-/+oooo+/-.   user@droneracing-Legion-9-16IRX9 
  `:+ss+:`   
--- 
-+ssyy+- OS: Ubuntu 22.04.4 LTS x86_64 
  .ossdMMMNyo.   Host: 83G0 Legion 9 16IRX9 
 /ssshdmmNNmmyNhss/  Kernel: 6.8.0-40-generic 
+shmydMMMNy+ Uptime: 27 mins 
   /hNMMMyhhhmNMMMNh/Packages: 1859 (dpkg), 9 (snap) 
  .dMMMNhsshNMMMd.   Shell: bash 5.1.16 
  +hhhyNMMNyyNMMMysss+   Resolution: 3200x2000 
  ossyNMMMNyMMhsshmmmhssso   DE: GNOME 42.9 
  ossyNMMMNyMMhsshmmmhssso   WM: Mutter 
  +hhhyNMMNyyNMMMysss+   WM Theme: Adwaita 
  .dMMMNhsshNMMMd.   Theme: Yaru [GTK2/3] 
   /hNMMMyhhhdNMMMNh/Icons: Yaru [GTK2/3] 
+sdmydy+ Terminal: gnome-terminal 
 /ssshdmmyNhss/  CPU: Intel i9-14900HX (32) @ 
5.600GHz 
  .ossdMMMNyo.   GPU: Intel Device a788 
-+syyy+- GPU: NVIDIA 01:00.0 NVIDIA 
Corporation Device 2757 
  `:+ss+:`   Memory: 2943MiB / 64004MiB 

  user@lenovo-Legion-9-16IRX9:~$ xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ PixArt Lenovo USB Optical Mouse id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8258) Keyboardid=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8258) Keyboardid=14   [slave  
keyboard (3)]
  ∼ ITE Tech. Inc. ITE Device(8258) Wireless Radio Control  id=12   
[floating slave]


  user@lenovo-Legion-9-16IRX9:~$ sudo acpidump | grep -C3 -i elan
 79490: 50 44 53 0A 02 70 0C 40 42 0F 00 53 50 45 44 A4  pds@b..sped.
 794A0: 00 08 5F 48 49 44 0D 58 58 58 58 30 30 30 30 00  .._HID..
 794B0: 08 5F 53 55 42 0D 58 58 58 58 30 30 30 30 00 A0  ._SUB...
 794C0: 25 93 54 50 54 59 01 70 0D 45 4C 41 4E 30 36 46  %.TPTY.p.ELAN06F
 794D0: 41 00 5F 48 49 44 70 0D 45 4C 41 4E 30 30 30 31  A._HIDp.ELAN0001
 794E0: 00 5F 53 55 42 A1 28 A0 26 93 54 50 54 59 0A 02  ._SUB.(.&.TPTY..
 794F0: 70 0D 53 59 4E 41 32 42 41 36 00 5F 48 49 44 70  p.SYNA2BA6._HIDp
 79500: 0D 53 59 4E 41 30 30 30 31 00 5F 53 55 42 08 5F  .SYNA0001._SUB._

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3
  ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  9 16:37:04 2024
  InstallationDate: Installed on 2024-09-09 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: linux-signed-hwe-6.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  droneracing   1363 F pulseaudio
   /dev/snd/controlC0:  droneracing   1363 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ub

[Kernel-packages] [Bug 2079985] Re: Lenovo Legion 9 16IRX9 - Touchpad is missing on Ubuntu 22.04+

[Philip Cox]

Hello Davide,

Thank you for taking the time to look into this.

I would like to clarify the issue here.

When you use the Ubuntu 22.04 live USB install media, the touchpad does
not work.  After you install though, the touchpad now works.

Also, the battery indicator appears after installing too, but not
before.

Can you please confirm that this is what the issue is?  Thank you.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Lenovo Legion 9 16IRX9 - Touchpad is missing on Ubuntu 22.04+

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brand new Lenovo Legion 9 16IRX9. It doesn't seem to detect any touchpad. 
  I also tested PopOS 24.04 liveUSB and it doesn't work.
  In Windows 11 it works.

  user@lenovo-Legion-9-16IRX9:~$ neofetch 
  .-/+oooo+/-.   user@droneracing-Legion-9-16IRX9 
  `:+ss+:`   
--- 
-+ssyy+- OS: Ubuntu 22.04.4 LTS x86_64 
  .ossdMMMNyo.   Host: 83G0 Legion 9 16IRX9 
 /ssshdmmNNmmyNhss/  Kernel: 6.8.0-40-generic 
+shmydMMMNy+ Uptime: 27 mins 
   /hNMMMyhhhmNMMMNh/Packages: 1859 (dpkg), 9 (snap) 
  .dMMMNhsshNMMMd.   Shell: bash 5.1.16 
  +hhhyNMMNyyNMMMysss+   Resolution: 3200x2000 
  ossyNMMMNyMMhsshmmmhssso   DE: GNOME 42.9 
  ossyNMMMNyMMhsshmmmhssso   WM: Mutter 
  +hhhyNMMNyyNMMMysss+   WM Theme: Adwaita 
  .dMMMNhsshNMMMd.   Theme: Yaru [GTK2/3] 
   /hNMMMyhhhdNMMMNh/Icons: Yaru [GTK2/3] 
+sdmydy+ Terminal: gnome-terminal 
 /ssshdmmyNhss/  CPU: Intel i9-14900HX (32) @ 
5.600GHz 
  .ossdMMMNyo.   GPU: Intel Device a788 
-+syyy+- GPU: NVIDIA 01:00.0 NVIDIA 
Corporation Device 2757 
  `:+ss+:`   Memory: 2943MiB / 64004MiB 

  user@lenovo-Legion-9-16IRX9:~$ xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ PixArt Lenovo USB Optical Mouse id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8258) Keyboardid=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8258) Keyboardid=14   [slave  
keyboard (3)]
  ∼ ITE Tech. Inc. ITE Device(8258) Wireless Radio Control  id=12   
[floating slave]


  user@lenovo-Legion-9-16IRX9:~$ sudo acpidump | grep -C3 -i elan
 79490: 50 44 53 0A 02 70 0C 40 42 0F 00 53 50 45 44 A4  pds@b..sped.
 794A0: 00 08 5F 48 49 44 0D 58 58 58 58 30 30 30 30 00  .._HID..
 794B0: 08 5F 53 55 42 0D 58 58 58 58 30 30 30 30 00 A0  ._SUB...
 794C0: 25 93 54 50 54 59 01 70 0D 45 4C 41 4E 30 36 46  %.TPTY.p.ELAN06F
 794D0: 41 00 5F 48 49 44 70 0D 45 4C 41 4E 30 30 30 31  A._HIDp.ELAN0001
 794E0: 00 5F 53 55 42 A1 28 A0 26 93 54 50 54 59 0A 02  ._SUB.(.&.TPTY..
 794F0: 70 0D 53 59 4E 41 32 42 41 36 00 5F 48 49 44 70  p.SYNA2BA6._HIDp
 79500: 0D 53 59 4E 41 30 30 30 31 00 5F 53 55 42 08 5F  .SYNA0001._SUB._

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3
  ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  9 16:37:04 2024
  InstallationDate: Installed on 2024-09-09 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: linux-signed-hwe-6.8
  UpgradeStatus: No upgrade lo

[Kernel-packages] [Bug 2080095] Re: Initializing bluetooth using socket.c userland functions broken after upgrade from 6.5 to 6.8 (and mainline 6.9, 6.10)

[Philip Cox]

Hi Julio.

Thank you for taking the time to open this bug report.

It isn't totally clear to me what you are asking for us to look at here.
I took a quick look and don't see any aobvious issues that could cause
the issues you are seeing.  IF you could provide more detail as to what
you would like us to look at, or in to, I can dig deeper.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

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

Title:
  Initializing bluetooth using socket.c userland functions broken after
  upgrade from 6.5 to 6.8 (and mainline 6.9, 6.10)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My company uses pybleno to initialize bluetooth LE devices on our IOT devices 
as GATT servers.
  This has worked fine from 4.x kernels on Ubuntu 18.04 up to 6.5.0 on Ubuntu 
22.04 for us. The Python code interfaces
  with the socket.c userland functions AFAICT.

  After upgrading from 6.5 to 6.8 kernel on Ubuntu 22.04, the kernel is
  now returning

  "[Errno 22] Invalid Argument" from the socket.c setsockopt function.

  I have outline as best I can what I checked in the downstream pybleno
  ticket here: https://github.com/Adam-Langley/pybleno/issues/63

  I could use some input on whether on not any of the recent socket.c changes 
between 6.5 to 6.8 changes could have caused this and if
  this is a regression or whether not the Python calls to these socket.c 
functions which have worked since 4.x need to be rewritten as a result 
  of an expected interface change on the kernel side.

  This problem exists for us as well when we tested with mainline 6.9
  and 6.10 kernels last week and our only current solution is
  downgrading to 6.5 .

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3
  ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  9 17:09:08 2024
  InstallationDate: Installed on 2023-01-03 (614 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.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.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080095/+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 2080095] Re: Initializing bluetooth using socket.c userland functions broken after upgrade from 6.5 to 6.8 (and mainline 6.9, 6.10)

[Philip Cox]

** Package changed: linux-signed-hwe-6.8 (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/2080095

Title:
  Initializing bluetooth using socket.c userland functions broken after
  upgrade from 6.5 to 6.8 (and mainline 6.9, 6.10)

Status in linux package in Ubuntu:
  New

Bug description:
  My company uses pybleno to initialize bluetooth LE devices on our IOT devices 
as GATT servers.
  This has worked fine from 4.x kernels on Ubuntu 18.04 up to 6.5.0 on Ubuntu 
22.04 for us. The Python code interfaces
  with the socket.c userland functions AFAICT.

  After upgrading from 6.5 to 6.8 kernel on Ubuntu 22.04, the kernel is
  now returning

  "[Errno 22] Invalid Argument" from the socket.c setsockopt function.

  I have outline as best I can what I checked in the downstream pybleno
  ticket here: https://github.com/Adam-Langley/pybleno/issues/63

  I could use some input on whether on not any of the recent socket.c changes 
between 6.5 to 6.8 changes could have caused this and if
  this is a regression or whether not the Python calls to these socket.c 
functions which have worked since 4.x need to be rewritten as a result 
  of an expected interface change on the kernel side.

  This problem exists for us as well when we tested with mainline 6.9
  and 6.10 kernels last week and our only current solution is
  downgrading to 6.5 .

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3
  ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  9 17:09:08 2024
  InstallationDate: Installed on 2023-01-03 (614 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.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.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080095/+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 2079859] Re: Lenovo V130-15IKB kernel 6.8 not booting from nvme

[Philip Cox]

** Changed in: linux-hwe-6.8 (Ubuntu)
 Assignee: (unassigned) => Vinicius Peixoto (vpeixoto)

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

Title:
  Lenovo V130-15IKB kernel 6.8 not booting from nvme

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

Bug description:
  After updating to 6.8.0-40, my Lenovo V130-15IKB fails to boot with a
  "nvme failed with error -12" message in dmesg.

  Booting on older 6.5.0-45 goes flawlessly.

  Tryed installing in-proposal 6.8.44 getting the same error as 6.8.40

  Is there a driver problem on 6.8.x, will it be addressed, or should I
  stick to 6.5?

  Thank you very much,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.8/+bug/2079859/+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 2079847] Re: Multiple bwrap processes opened by Nautilus jams up to infinity and this raise up cpu power guzzle over 60 W.

[Philip Cox]

Hello, thank you for taking the time to open this bug report.

Can you please share where you say the comment from Feb 28 saying that
it was fixed?  I would like to see what was said, by who, and about
what.

You are also running a very old  6.8 Ubuntu kernel, and you have not
provided any relevant or useful information.

Please take the following steps:
1) Update Ubuntu and its kernel to the latest available.
2) re-test if the bug exists
and if it still does
3) run the command "apport-collect 2079847"

---

After all of that is provided, I can take a look at the issue and see
what might be causing this.  IT also seems like it is not a kernel
issue, but an issue  somewhere in userspace, or perhaps the nautalis
package.  We need the requested info to determine that.


** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

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

Title:
  Multiple bwrap processes opened by Nautilus jams up to infinity and
  this raise up cpu power guzzle over 60 W.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Nautilus starts multiple process named bwrap which continues to
  infinity and adds cpu wattages many tens of wats, usually over 60 Wats
  in my two-processor 88-thread pc.

  So you must understand i so pist off for that this even rais up my
  electricity bill couse my computers is online 24/7.

  
  Someone is sayed on Feb 28
  "The issue can probably be closed now...our kernel maintainer says the same 
as smcv (fix was in 6.8rc6). Don't think bubblewrap can do anything about it."


  I have:

  Linux xeon-e5-2696-v4 6.8.0-11-generic #11-Ubuntu SMP PREEMPT_DYNAMIC
  Wed Feb 14 00:29:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  ... and still problem !

  When you like to do something about that?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2079847/+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 2079782] Re: LinuxMint22 shutdown issues: 2-minute delay, black screen, and kernel warnings

[Philip Cox]

Hello, thank you for taking the time to open the bug report about this
issue.

Unfortunately, this is running on Mint, not Ubuntu, and you have the
out-of-tree virtualbox drivers installed.  These are two things we can
not provide support for.

I will close this ticket for now, but if you reproduce this on Ubuntu
directly, without the out-of-tree drivers, please re-open this ticket,
and we can look into it.  Also, please run the command "apport-collect
2079782" to include all the relevant logs and data.

Perhaps this issue can be resolved by the resolution to the following
bug that dealt with VirtualBox on the 6.8 kernel...
https://bugs.launchpad.net/bugs/2073267

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

Title:
  LinuxMint22 shutdown issues: 2-minute delay, black screen, and kernel
  warnings

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  Since I installed LinuxMint22 (with kernel 6.8.0-41), the PC
  (NUC12WSHi5) shutdown process has become very long and unusual.

  Initially, the screen turns off and then turns back on with a black display.
  After 2 minutes of black screen, the following message appears (and then the 
PC shuts down).

  
  Additionally, when I enter the following command in the LinuxMint22 terminal:
  sudo dmesg | egrep 'fail|error|warn'

  I get these messages:
  [0.00] x86/split lock detection: #AC: crashing the kernel on kernel 
split_locks and warning on user-space split_locks
  [4.165952] Serial bus multi instantiate pseudo device driver INT3515:00: 
error -ENXIO: IRQ index 1 not found
  [4.165962] Serial bus multi instantiate pseudo device driver INT3515:00: 
error -ENXIO: Error requesting irq at index 1
  [   10.086509] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel

  These issues seem to be related to the shutdown process and possibly
  to driver or kernel module problems.

  
  I remain at your disposal.

  Thank you

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2079782/+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 2078725] Re: 24.04.1 LTS useless as a stratum 1 ntp server

[Philip Cox]

Hi Jim, thank you for the update on this!

I will mark this bug closed for now, but please re-open it if it turns
out that it is not with the NTP package, but likely the kernel.

Also, feel free to update the bug with the results of the NTP groups
analysis, or provide a link to it so I/others can follow if needed.

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

Title:
  24.04.1 LTS useless as a stratum 1 ntp server

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I have a machine with a serial attached precision reference clock with
  a pps accuracy of +/- 1 nanosecond that I have been using as a stratum
  1 ntp server for years.

  Upon upgrading from 22.04.4 LTS to 24.04.1 LTS ntp went insane.

  ntpq -p shows:

  xNMEA(0) .PPS.0 l   12   16  377   0. -96.8229
  0.5427

  Previously that 'x', which means the source is being rejected, was
  'o', which means the source has pps, and the offset, which now shows
  as -96 milliseconds was under 1 millisecond.

  From syslog:

  ntpd[10299]: REFCLOCK: refclock_params: kernel PLL (hardpps, RFC 1589) not 
implemented
  ntpd[10299]: REFCLOCK: NMEA(0) set PPSAPI params fails

  It appears that the ppsapi has not been implemented in 24.04.1 LTS which 
makes it useless as a stratum 1 ntp server.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k6.8.0-41-lowlatency.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', 
'/dev/snd/seq', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D3p', 
'/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/controlC0', '/dev/snd/by-path'] 
failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2022-07-05 (791 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Lsusb-t:
   /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 480M
   |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
   /:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 5000M
  MachineType: Default string Default string
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-lowlatency 
root=UUID=4046c392-c5b7-474e-8533-ac02ad623d3f ro
  ProcVersionSignature: Ubuntu 6.8.0-41.41.1-lowlatency 6.8.12
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-41-lowlatency N/A
   linux-backports-modules-6.8.0-41-lowlatency  N/A
   linux-firmware   20240318.git3b128b60-0ubuntu2.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: noble
  Uname: Linux 6.8.0-41-lowlatency x86_64
  UpgradeStatus: Upgraded to noble on 2024-09-01 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/11/2021
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.6.5
  dmi.board.asset.tag: Default string
  dmi.board.name: PB_1900A
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd11/11/2021:br5.6:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnPB_1900A:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Default string
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-07-05T15:09:42.972150
  mtime.conffile..etc.init.d.apport: 2024-07-22T07:59:07

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


-- 
Mailing list: https://launchpad.n

[Kernel-packages] [Bug 2079246] Re: System hanging at startup after seeing the line "Listening on Load/save RF Kill Switch Status" in console

[Philip Cox]

Hi Alan, thank you for opening this bug report.

Does your system boot fine if you do not remove the quiet and splash
options?

If you are able to boot can you please run the command "apport-collect
2079246" to include relevant information that will help us look at this
issue?

If you are not able to boot, can you boot to the latest working kernel,
and run it there?

Also, what is the kernel version you are having this failure with?

The firmware messages look like they would be the cause of the issue,
but we need more information to confirm that.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

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

Title:
  System hanging at startup after seeing the line "Listening on
  Load/save RF Kill Switch Status" in console

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi, the system just hangs. When choosing not to use quiet & splash
  options on boot, I can see the last line before complete freeze, which
  starts with "Listening on Load/save RF Kill Switch Status". After
  that, a hard reboot is needed.

  I can boot on previous kernel without problem (linux-
  image-6.5.0-45-generic).

  After booting with previous kernel, all I can see in dmesg, near the end, is :
  [   20.115597] nouveau :01:00.0: Direct firmware load for 
nouveau/nv98_fuc084 failed with error -2
  [   20.115640] nouveau :01:00.0: Direct firmware load for 
nouveau/nv98_fuc084d failed with error -2
  [   20.115643] nouveau :01:00.0: msvld: unable to load firmware data
  [   20.115646] nouveau :01:00.0: msvld: init failed, -19

  I'm not skilled enough to say whether it's relevant or not.

  My computer is an old HP 6200 MT with Intel Core i7-2600 and a Nvidia
  Geforce 8400GS additional graphic card. If I can help furthermore by
  providing any additional information, I will do it.

  I found two topis on the web where similar issues are reported :
  
https://www.reddit.com/r/archlinux/comments/1dusm7g/os_booting_stuck_at_ok_started_load_save_rf_kill/
  
https://askubuntu.com/questions/1524855/kubuntu-22-04-problem-with-kernel-6-8-0-after-update-from-kernel-6-5-0-45-to-6

  Thx !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2079246/+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 2079246] Re: System hanging at startup after seeing the line "Listening on Load/save RF Kill Switch Status" in console

[Philip Cox]

** Package changed: linux-meta-hwe-6.8 (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/2079246

Title:
  System hanging at startup after seeing the line "Listening on
  Load/save RF Kill Switch Status" in console

Status in linux package in Ubuntu:
  New

Bug description:
  Hi, the system just hangs. When choosing not to use quiet & splash
  options on boot, I can see the last line before complete freeze, which
  starts with "Listening on Load/save RF Kill Switch Status". After
  that, a hard reboot is needed.

  I can boot on previous kernel without problem (linux-
  image-6.5.0-45-generic).

  After booting with previous kernel, all I can see in dmesg, near the end, is :
  [   20.115597] nouveau :01:00.0: Direct firmware load for 
nouveau/nv98_fuc084 failed with error -2
  [   20.115640] nouveau :01:00.0: Direct firmware load for 
nouveau/nv98_fuc084d failed with error -2
  [   20.115643] nouveau :01:00.0: msvld: unable to load firmware data
  [   20.115646] nouveau :01:00.0: msvld: init failed, -19

  I'm not skilled enough to say whether it's relevant or not.

  My computer is an old HP 6200 MT with Intel Core i7-2600 and a Nvidia
  Geforce 8400GS additional graphic card. If I can help furthermore by
  providing any additional information, I will do it.

  I found two topis on the web where similar issues are reported :
  
https://www.reddit.com/r/archlinux/comments/1dusm7g/os_booting_stuck_at_ok_started_load_save_rf_kill/
  
https://askubuntu.com/questions/1524855/kubuntu-22-04-problem-with-kernel-6-8-0-after-update-from-kernel-6-5-0-45-to-6

  Thx !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2079246/+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 2079491] Re: Fix handling of mixed VGA and non-VGA class PCI GPUs

[Philip Cox]

Hi Alex, thank you for letting us know about this.  I will make sure it
gets applied to any of a kernels that it is applicable to. It looks like
it is applicable to the 6.8 based kernels, and newer.

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

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

Title:
  Fix handling of mixed VGA and non-VGA class PCI GPUs

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This patch needs to be applied to avoid a segfault when VGA and non-VGA PCI 
class GPUs are mixed in a system and the non-VGA GPU is the primary:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b49420d6a1aeb399e5b107fc6eb8584d0860fbd7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2079491/+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 2078725] Re: 24.04.1 LTS useless as a stratum 1 ntp server

[Philip Cox]

Hi Jim, thank you for adding the extra information.

The configs for the noble (24.04) and jammy (22.04) kernels both have
the same PPS options enabled, and the  pps_ldisc module is being loaded
on your machine, which appears to be the correct driver to use.


Two things I can thin k to suggest are, 

1) try switching to the generic noble 6.8 kernel rather than the
lowlatency kernel.  Just as a test, this might provide useful
information.

2) The linux-modules-extra package contains other drivers that are not
always installed.  Some times between releases a driver will move from
the main linux-modules package to the linux-modules-extra package.  This
might resolve the issue as well.

Can you let me know if either of these resolve the issue?  It would
provide more info for me to use to look into this.

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

Title:
  24.04.1 LTS useless as a stratum 1 ntp server

Status in linux package in Ubuntu:
  New

Bug description:
  I have a machine with a serial attached precision reference clock with
  a pps accuracy of +/- 1 nanosecond that I have been using as a stratum
  1 ntp server for years.

  Upon upgrading from 22.04.4 LTS to 24.04.1 LTS ntp went insane.

  ntpq -p shows:

  xNMEA(0) .PPS.0 l   12   16  377   0. -96.8229
  0.5427

  Previously that 'x', which means the source is being rejected, was
  'o', which means the source has pps, and the offset, which now shows
  as -96 milliseconds was under 1 millisecond.

  From syslog:

  ntpd[10299]: REFCLOCK: refclock_params: kernel PLL (hardpps, RFC 1589) not 
implemented
  ntpd[10299]: REFCLOCK: NMEA(0) set PPSAPI params fails

  It appears that the ppsapi has not been implemented in 24.04.1 LTS which 
makes it useless as a stratum 1 ntp server.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k6.8.0-41-lowlatency.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', 
'/dev/snd/seq', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D3p', 
'/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/controlC0', '/dev/snd/by-path'] 
failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2022-07-05 (791 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Lsusb-t:
   /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 480M
   |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
   /:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 5000M
  MachineType: Default string Default string
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-lowlatency 
root=UUID=4046c392-c5b7-474e-8533-ac02ad623d3f ro
  ProcVersionSignature: Ubuntu 6.8.0-41.41.1-lowlatency 6.8.12
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-41-lowlatency N/A
   linux-backports-modules-6.8.0-41-lowlatency  N/A
   linux-firmware   20240318.git3b128b60-0ubuntu2.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: noble
  Uname: Linux 6.8.0-41-lowlatency x86_64
  UpgradeStatus: Upgraded to noble on 2024-09-01 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/11/2021
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.6.5
  dmi.board.asset.tag: Default string
  dmi.board.name: PB_1900A
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd11/11/2021:br5.6:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnPB_1900A:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Default string
  modified.conffile..etc.default.apport:
   # set this 

[Kernel-packages] [Bug 2078725] Re: 24.04.1 LTS useless as a stratum 1 ntp server

[Philip Cox]

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/2078725

Title:
  24.04.1 LTS useless as a stratum 1 ntp server

Status in linux package in Ubuntu:
  New

Bug description:
  I have a machine with a serial attached precision reference clock with
  a pps accuracy of +/- 1 nanosecond that I have been using as a stratum
  1 ntp server for years.

  Upon upgrading from 22.04.4 LTS to 24.04.1 LTS ntp went insane.

  ntpq -p shows:

  xNMEA(0) .PPS.0 l   12   16  377   0. -96.8229
  0.5427

  Previously that 'x', which means the source is being rejected, was
  'o', which means the source has pps, and the offset, which now shows
  as -96 milliseconds was under 1 millisecond.

  From syslog:

  ntpd[10299]: REFCLOCK: refclock_params: kernel PLL (hardpps, RFC 1589) not 
implemented
  ntpd[10299]: REFCLOCK: NMEA(0) set PPSAPI params fails

  It appears that the ppsapi has not been implemented in 24.04.1 LTS which 
makes it useless as a stratum 1 ntp server.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k6.8.0-41-lowlatency.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', 
'/dev/snd/seq', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D3p', 
'/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/controlC0', '/dev/snd/by-path'] 
failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2022-07-05 (791 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Lsusb-t:
   /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 480M
   |__ Port 002: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
   /:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 5000M
  MachineType: Default string Default string
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-lowlatency 
root=UUID=4046c392-c5b7-474e-8533-ac02ad623d3f ro
  ProcVersionSignature: Ubuntu 6.8.0-41.41.1-lowlatency 6.8.12
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-41-lowlatency N/A
   linux-backports-modules-6.8.0-41-lowlatency  N/A
   linux-firmware   20240318.git3b128b60-0ubuntu2.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: noble
  Uname: Linux 6.8.0-41-lowlatency x86_64
  UpgradeStatus: Upgraded to noble on 2024-09-01 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/11/2021
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.6.5
  dmi.board.asset.tag: Default string
  dmi.board.name: PB_1900A
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd11/11/2021:br5.6:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnPB_1900A:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Default string
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-07-05T15:09:42.972150
  mtime.conffile..etc.init.d.apport: 2024-07-22T07:59:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078725/+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 2077405] Re: External screen flashing and cannot use after laptop lid closed

[Philip Cox]

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

Hi Oliver, thank you for providing the requested information.

After reading through the logs, it really looks like this is a duplicate
of https://bugs.launchpad.net/bugs/2062951


** This bug has been marked a duplicate of bug 2062951
   Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 
6.8

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

Title:
  External screen flashing and cannot use after laptop lid closed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With Kernel 6.8.0-40 (upgraded yesterday) 
  a) the external screen connected to my Lenovo T14 ThinkPad randomly turns 
black for a few seconds and then recovers,
  b) the laptop cannot be used after the lid has been closed. The power LED is 
lit (no stand-by) but screen is blank. No reaction to any key, also cannot open 
a terminal with Ctrl-Alt-Fx. Only a hard reset is possible.

  None of these problems occur with Kernel 6.5.0-45.

  I have previously attempted to use Ubuntu 24.04 LTS but faced exactly
  the same issues, therefore I re-installed Ubuntu 22.04 LTS which was
  working stable until yesterdays kernel upgrade.

  While working with 24.04 LTS for a few weeks I also noted frequent,
  random and complete system freezes which made it unusable with that
  laptop.

  $ lsb_release -rd
  Description:  Ubuntu 22.04.4 LTS
  Release:  22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3
  ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Tue Aug 20 10:27:32 2024
  InstallationDate: Installed on 2024-08-05 (14 days ago)
  InstallationMedia: Xubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  SourcePackage: linux-signed-hwe-6.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oligri 1236 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-08-05 (27 days ago)
  InstallationMedia: Xubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: LENOVO 20S0007LMX
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-40-generic 
root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-40-generic N/A
   linux-backports-modules-6.8.0-40-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.31
  Tags:  jammy
  Uname: Linux 6.8.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/26/2020
  dmi.bios.release: 1.13
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2XET23W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20S0007LMX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2XET23W(1.13):bd08/26/2020:br1.13:efr1.7:svnLENOVO:pn20S0007LMX:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0007LMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20S0_BU_Think_FM_ThinkPadT14Gen1:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20S0007LMX
  dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077405/+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 2077260] Re: freeze after updating to newest kernel on log in sreen or just after log in (6.8.0-45 ?). Had to use Grub to restero to 6.5.0-45

[Philip Cox]

I have updated the pack  this is opened against.  The apport-collect
command should collect better information this time.  Can you please try
to run it again?

I've read through all the data and looked at the differences in kernels
but I can't see anything standing out yet.  Can you please re-run the
apport-collect to gather more info?

** Package changed: linux-signed-hwe-6.8 (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/2077260

Title:
  freeze after updating to newest kernel on log in sreen or just after
  log in (6.8.0-45 ?). Had to use Grub to restero to 6.5.0-45

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  freeze after updating to newest kernel on log in sreen or just after
  log in (6.8.0-45 ?). Had to use Grub to rester to 6.5.0-45

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-45-generic 6.5.0-45.45~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 18 15:53:56 2024
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077260/+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 2077061] Re: Ubuntu 24.04 showed CXL related complaining messages when CXL capable root port did not attach CXL device

[Philip Cox]

Thank you Kelvin for adding the information from apport-collect.  I will
go over all the data to look into this.

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

Title:
  Ubuntu 24.04 showed CXL related complaining messages when CXL capable
  root port did not attach CXL device

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 24.04 showed CXL related complaining messages (when CXL root
  port did not attach CXL device) such as below messages (refer to
  attached dmesg file):

  
  Couldn't locate the CXL.cache and CXL.mem capability array header.
  HDM decoder capability not found

  For more details, Please refer to the attached dmesg file

  How reproducible:
  100%

  Steps to reproduce

  1. Install Ubuntu 24.04 on a Lenovo server which is CXL enabled by
  Intel CPU and Lenovo UEFI, but there is no CXL device attached in this
  server.

  2. Check the dmesg.

  3. The above error messages are seen in the dmesg file.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 28 03:14 seq
   crw-rw 1 root audio 116, 33 Aug 28 03:14 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', 
'/dev/snd/seq'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-08-28 (0 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Release amd64 
(20240423)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Lenovo ThinkSystem SR650 V4,Processor board,BHS,2U,Renesas
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-41-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-41-generic N/A
   linux-backports-modules-6.8.0-41-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: noble
  Uname: Linux 6.8.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/26/2024
  dmi.bios.release: 0.60
  dmi.bios.vendor: Lenovo
  dmi.bios.version: IHE105M-0.60
  dmi.board.name: SB27B70050
  dmi.board.vendor: Lenovo
  dmi.board.version: 2
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: None
  dmi.ec.firmware.release: 0.46
  dmi.modalias: 
dmi:bvnLenovo:bvrIHE105M-0.60:bd08/26/2024:br0.60:efr0.46:svnLenovo:pnThinkSystemSR650V4,Processorboard,BHS,2U,Renesas:pvr2:rvnLenovo:rnSB27B70050:rvr2:cvnLenovo:ct23:cvrNone:sku7DGCCTO2WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkSystem SR650 V4,Processor board,BHS,2U,Renesas
  dmi.product.sku: 7DGCCTO2WW
  dmi.product.version: 2
  dmi.sys.vendor: Lenovo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077061/+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 2077061] Re: Ubuntu 24.04 showed CXL related complaining messages when CXL capable root port did not attach CXL device

[Philip Cox]

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/2077061

Title:
  Ubuntu 24.04 showed CXL related complaining messages when CXL capable
  root port did not attach CXL device

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 24.04 showed CXL related complaining messages (when CXL root
  port did not attach CXL device) such as below messages (refer to
  attached dmesg file):

  
  Couldn't locate the CXL.cache and CXL.mem capability array header.
  HDM decoder capability not found

  For more details, Please refer to the attached dmesg file

  How reproducible:
  100%

  Steps to reproduce

  1. Install Ubuntu 24.04 on a Lenovo server which is CXL enabled by
  Intel CPU and Lenovo UEFI, but there is no CXL device attached in this
  server.

  2. Check the dmesg.

  3. The above error messages are seen in the dmesg file.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 28 03:14 seq
   crw-rw 1 root audio 116, 33 Aug 28 03:14 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', 
'/dev/snd/seq'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-08-28 (0 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Release amd64 
(20240423)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Lenovo ThinkSystem SR650 V4,Processor board,BHS,2U,Renesas
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-41-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-41-generic N/A
   linux-backports-modules-6.8.0-41-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: noble
  Uname: Linux 6.8.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/26/2024
  dmi.bios.release: 0.60
  dmi.bios.vendor: Lenovo
  dmi.bios.version: IHE105M-0.60
  dmi.board.name: SB27B70050
  dmi.board.vendor: Lenovo
  dmi.board.version: 2
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: None
  dmi.ec.firmware.release: 0.46
  dmi.modalias: 
dmi:bvnLenovo:bvrIHE105M-0.60:bd08/26/2024:br0.60:efr0.46:svnLenovo:pnThinkSystemSR650V4,Processorboard,BHS,2U,Renesas:pvr2:rvnLenovo:rnSB27B70050:rvr2:cvnLenovo:ct23:cvrNone:sku7DGCCTO2WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkSystem SR650 V4,Processor board,BHS,2U,Renesas
  dmi.product.sku: 7DGCCTO2WW
  dmi.product.version: 2
  dmi.sys.vendor: Lenovo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077061/+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 2078881] Re: mlx-bootctl: support RTC battery status read and clear

[Philip Cox]

** Changed in: linux-bluefield (Ubuntu)
 Assignee: (unassigned) => Bartlomiej Zolnierkiewicz (bzolnier)

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

Title:
  mlx-bootctl: support RTC battery status read and clear

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]

  The RTC battery status is not directly accessible from the kernel user
  space. The recent Nvidia UEFI added SMC to report the RTC battery
  status and clear the status bit if needed.

  [Fix]

  * Added an rtc_battery entry in the bootctl driver.
  * Read the rtc_battery entry will trigger an SMC call to read the RTC battery 
status.

  [Test Case]

  * Check if the bootctl driver is loaded.
  * Check the rtc_battery entry:
  cat /sys/bus/platform/drivers/mlxbf-bootctl/rtc_battery
  A value of 0x0 means RTC battery voltage is good.
  A value of 0x80 means RTC battery voltage is low. The status bit is also 
cleared after the read.
  An error code will be return if this feature is missing from UEFI.

  [Other]
  * This code is likely to change depending on feedback we received from 
maintainers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2078881/+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 2078726] Re: VAIO freezes at poweroff

[Philip Cox]

Hi Antoine,

Thanks for the updates on the ticket.  I will go over all the data, and
give you an update.  And if there is a fix we identify, you can submit
it, sure.  I see you posted on irc in #ubuntu-kernel.  Feel free to
contact me there if you need any assistance.

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/2078726

Title:
  VAIO freezes at poweroff

Status in linux package in Ubuntu:
  New

Bug description:
  I have a VAIO SVS1511C5E from 2012. I am on the latest BIOS available
  (rev 3.7).

  On Ubuntu 24.04.1 LTS (kernel 6.8.0-41-generic), the laptop hangs
  during poweroff or reboot. In the logs, the last lines I get are:

  ===

  sept. 02 18:02:55 antoine-SVS1511C5E systemd[1]: Reached target 
poweroff.target - System Power Off.
  sept. 02 18:02:55 antoine-SVS1511C5E systemd[1]: Shutting down.
  sept. 02 18:02:55 antoine-SVS1511C5E systemd-shutdown[1]: Syncing filesystems 
and block devices.
  sept. 02 18:02:55 antoine-SVS1511C5E systemd-shutdown[1]: Sending SIGTERM to 
remaining processes...
  sept. 02 18:02:55 antoine-SVS1511C5E systemd-journald[338]: Received SIGTERM 
from PID 1 (systemd-shutdow).
  sept. 02 18:02:55 antoine-SVS1511C5E systemd-journald[338]: Journal stopped

  ===

  At each boot, dmesg displays a bug, which you can see in the attached
  file "CurrentDmesg.txt" at second 4.745697.

  My laptop also sometimes gets really slow (I can move the mouse, but
  launching a new window like the file manager or Firefox or even
  starting a new shell takes a minute). When that happens, I get a
  similar error multiple times in my journalctl (see attached file
  "journalctl logs").

  The folks over on IRC (libera #ubuntu) told me it might be a kernel
  bug related to power management, so I tried different releases.

  - 14.04 works (does not hang during power off)
  - 20.04 works
  - 21.04 works
  - 21.10 does not work (hangs during power off)
  - 22.04 does not work
  - 24.04 does not work

  I then tried to narrow it down to a kernel release so I tried a few
  kernels within 24.04.1.

  - 5.11.0 works (does not hang during power off)
  - 5.11.16 works
  - 5.11.20 works
  - 5.11.22 works (which is called 5.11.0-20 in 
https://kernel.ubuntu.com/mainline/v5.11.22/ so I'm not sure which version it 
is)
  - 5.12.0 does not work (hangs during power off)
  - 5.13.0 does not work

  Note that in kernel 5.11 and below, I do not get the aforementionned
  bug in dmesg, whereas it happens every times on kernels 5.12 and
  above. I also never experienced freeze in kernels 5.11 and below. (I
  tried booting with acpi=off in 24.04.1 with kernel 6.8.0, which did
  not seem to fix the issue.)

  Kernel 5.12 seems to be the culprit, and I see it added Dynamic
  Thermal Power Management (DTPM).

  Could my firmware be incompatible with DTPM?

  Thanks a lot for your help. Please let me know what I can do to help
  fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-41-generic 6.8.0-41.41
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:antoine1498 F pipewire
   /dev/snd/controlC0:  antoine1502 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  2 18:39:55 2024
  InstallationDate: Installed on 2024-08-28 (5 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: Sony Corporation SVS1511C5E
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-generic 
root=UUID=3b938f0a-0ea0-4249-9926-e254e0a94568 ro
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-41-generic N/A
   linux-backports-modules-6.8.0-41-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2012
  dmi.bios.release: 1.42
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0142C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 1.42
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:br1.42:efr1.42:svnSonyCorporation:pnSVS1511C5E:pvrC60AY9HK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVS1511C5E
  dmi

[Kernel-packages] [Bug 2078754] Re: ice driver in ubuntu 20.04 & 22.04 kernel drops a lot of packages

[Philip Cox]

Hello, thank you for taking the time to open this bug report.

Unfortunately, we cannot update just a single driver in the source tree
for most of the drivers in the linux kernel.  There are a few of options
that may help though.

1) If you are running Jammy (22.04), it initially shipped with the 5.15
kernel as you note, but there is now a 6.8 based kernel available for
it.  So, you can upgrade the kernel in the 22.04 install to the 7.8
based kernel, and this will include a newer version of the ice driver.
Perhaps this driver will be more stable for you.

2) You can test out the newest release,  Noble (24.04) which has a 6.8
based kernel, and will be moving to a newer kernel once 24.10 is
released.  The 6.8 kernel is the same one that we backport and make
available on 22.04.

3) If the Intel provided packages driver packages work for you, they may
be sufficient to use.  I cannot comment on this though, because I have
not tried the packages, and we do not support them.  So, if there are
issues, and we need to look into it, the first thing that will be
recommended is to uninstall those drivers.


I will be closing this bug, but if you disagree with my comments, or have any 
additional information, please re-open it, and let me know.


** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

Title:
  ice driver in ubuntu 20.04 & 22.04 kernel drops a lot of packages

Status in linux package in Ubuntu:
  Invalid

Bug description:
  We're using Ubuntu 20.04 LTS and 22.04 LTS on Supermicro servers with
  AOC-S25GC-i2S network card (Intel E810-XXVAM2 Ethernet Controller). We
  observed that the preloaded ice driver with the kernel (5.4.0-xxx in
  Ubuntu 20.04 and 5.15.0-xxx in Ubuntu 22.04) working abnormally, that
  made a lot of drop packages in the network interface (we're using LACP
  linux bonding). Manually update the driver to lastest version
  (https://www.intel.com/content/www/us/en/download/19630/822519/intel-
  network-adapter-driver-for-e810-series-devices-under-linux.html) solve
  the problem. Please load the new ice driver version to the next kernel
  version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078754/+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 2076217] Re: booting an 24.10 or 24.04 ec2 instance with SEV-SNP enabled hangs sometimes

[Philip Cox]

** Changed in: linux-aws (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

Title:
  booting an 24.10 or 24.04 ec2 instance with SEV-SNP enabled hangs
  sometimes

Status in cloud-images:
  New
Status in linux-aws package in Ubuntu:
  New

Bug description:
  I'm trying to test an EC2 instance with SEV-SNP enabled. But the boot
  process hangs at:

  [snipped]
  [0.609079] printk: legacy console [ttyS0] enabled
  [5.405931] ACPI: Core revision 20230628
  [5.430448] clocksource: hpet: mask: 0x max_cycles: 0x, 
max_idle_ns: 30580167144 ns
  [5.473066] APIC: Switch to symmetric I/O mode setup

  
  Steps to reproduce are:

  $ AWS_DEFAULT_REGION=eu-west-1 aws ec2 run-instances --image-id
  ami-005a44922e2ffd1fa --instance-type m6a.large --cpu-options
  AmdSevSnp=enabled --key-name toabctl --tag-specifications
  'ResourceType=instance,Tags=[{Key=Name,Value=toabctl-2410-sevsnp-
  testing}]'

  The AMI ami-005a44922e2ffd1fa is ubuntu/images-testing/hvm-ssd-
  gp3/ubuntu-oracular-daily-amd64-server-20240716 and does contain
  6.8.0-1008-aws .

  Attached is the full output from the EC2 serial console.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2076217/+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 2078726] Re: VAIO freezes at poweroff

[Philip Cox]

Hi Antoine,

Thank you for taking the time to open this bug report.  Can you please run the 
command right after a failed power down:
journalctl -b -1 -r

And give me the output please?



** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

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

Title:
  VAIO freezes at poweroff

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a VAIO SVS1511C5E from 2012. I am on the latest BIOS available
  (rev 3.7).

  On Ubuntu 24.04.1 LTS (kernel 6.8.0-41-generic), the laptop hangs
  during poweroff or reboot. In the logs, the last lines I get are:

  ===

  sept. 02 18:02:55 antoine-SVS1511C5E systemd[1]: Reached target 
poweroff.target - System Power Off.
  sept. 02 18:02:55 antoine-SVS1511C5E systemd[1]: Shutting down.
  sept. 02 18:02:55 antoine-SVS1511C5E systemd-shutdown[1]: Syncing filesystems 
and block devices.
  sept. 02 18:02:55 antoine-SVS1511C5E systemd-shutdown[1]: Sending SIGTERM to 
remaining processes...
  sept. 02 18:02:55 antoine-SVS1511C5E systemd-journald[338]: Received SIGTERM 
from PID 1 (systemd-shutdow).
  sept. 02 18:02:55 antoine-SVS1511C5E systemd-journald[338]: Journal stopped

  ===

  At each boot, dmesg displays a bug, which you can see in the attached
  file "CurrentDmesg.txt" at second 4.745697.

  My laptop also sometimes gets really slow (I can move the mouse, but
  launching a new window like the file manager or Firefox or even
  starting a new shell takes a minute). When that happens, I get a
  similar error multiple times in my journalctl (see attached file
  "journalctl logs").

  The folks over on IRC (libera #ubuntu) told me it might be a kernel
  bug related to power management, so I tried different releases.

  - 14.04 works (does not hang during power off)
  - 20.04 works
  - 21.04 works
  - 21.10 does not work (hangs during power off)
  - 22.04 does not work
  - 24.04 does not work

  I then tried to narrow it down to a kernel release so I tried a few
  kernels within 24.04.1.

  - 5.11.0 works (does not hang during power off)
  - 5.11.16 works
  - 5.11.20 works
  - 5.11.22 works (which is called 5.11.0-20 in 
https://kernel.ubuntu.com/mainline/v5.11.22/ so I'm not sure which version it 
is)
  - 5.12.0 does not work (hangs during power off)
  - 5.13.0 does not work

  Note that in kernel 5.11 and below, I do not get the aforementionned
  bug in dmesg, whereas it happens every times on kernels 5.12 and
  above. I also never experienced freeze in kernels 5.11 and below. (I
  tried booting with acpi=off in 24.04.1 with kernel 6.8.0, which did
  not seem to fix the issue.)

  Kernel 5.12 seems to be the culprit, and I see it added Dynamic
  Thermal Power Management (DTPM).

  Could my firmware be incompatible with DTPM?

  Thanks a lot for your help. Please let me know what I can do to help
  fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-41-generic 6.8.0-41.41
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:antoine1498 F pipewire
   /dev/snd/controlC0:  antoine1502 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  2 18:39:55 2024
  InstallationDate: Installed on 2024-08-28 (5 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: Sony Corporation SVS1511C5E
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-generic 
root=UUID=3b938f0a-0ea0-4249-9926-e254e0a94568 ro
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-41-generic N/A
   linux-backports-modules-6.8.0-41-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2012
  dmi.bios.release: 1.42
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0142C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 1.42
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0142C5:bd05/17/2012:br1.42:efr1.42:svnSonyCorporation:pnSVS1511C5E:pvrC60AY9HK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A:
  dm

[Kernel-packages] [Bug 2078725] Re: 24.04.1 LTS useless as a stratum 1 ntp server

[Philip Cox]

Hello Jim,

Thank you for taking the time to open this bug report.  Unfortunately,
there is not enough information for us to look into this at this point
in time.

Please run the command "apport-collect 2078725" to include the relevant
logs, and system information and we will look at it.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

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

Title:
  24.04.1 LTS useless as a stratum 1 ntp server

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a machine with a serial attached precision reference clock with
  a pps accuracy of +/- 1 nanosecond that I have been using as a stratum
  1 ntp server for years.

  Upon upgrading from 22.04.4 LTS to 24.04.1 LTS ntp went insane.

  ntpq -p shows:

  xNMEA(0) .PPS.0 l   12   16  377   0. -96.8229
  0.5427

  Previously that 'x', which means the source is being rejected, was
  'o', which means the source has pps, and the offset, which now shows
  as -96 milliseconds was under 1 millisecond.

  From syslog:

  ntpd[10299]: REFCLOCK: refclock_params: kernel PLL (hardpps, RFC 1589) not 
implemented
  ntpd[10299]: REFCLOCK: NMEA(0) set PPSAPI params fails

  It appears that the ppsapi has not been implemented in 24.04.1 LTS
  which makes it useless as a stratum 1 ntp server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078725/+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 2073695] Re: Deadlock occurs while suspending md raid

[Philip Cox]

@meireli,

The change was submitted to the generic noble Ubuntu 6.8 based kernel .
This means that it will end up in all of the noble kernels, and the 6.8
jammy kernels, not just the aws kernels.

So, this fix will appear in all 6.8 based ubuntu kernels, the jammy 6.8
kernels, and the noble kernels, for all platforms, not just 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/2073695

Title:
   Deadlock occurs while suspending md raid

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

Bug description:
  System hung while suspending the raid.

  Steps to reproduce:
  1. Create a raid with 2 devices
  2. Suspend via sysfs (echo 274877906944 > /sys/block/md_X/md/suspend_hi)

  this issue was seen in Ubuntu-aws-6.5-6.5.0-1023 version.

  I found a fix for that issue that was already submitted to upstream (commit 
611d5cbc0b35a752e657a83eebadf40d814d006b).
  link: 
https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git/commit/drivers/md/md.c?h=md-6.11&id=611d5cbc0b35a752e657a83eebadf40d814d006b

  this patch wasn't added to aws-6.5-next branch(Ubuntu-
  aws-6.5-6.5.0-1024)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073695/+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 2077472] Re: Bugs reintroduced with linux-image-6.8.0-40-generic on T14 AMD Gen3

[Philip Cox]

Hi Martin, thanks for the update.


** Changed in: linux-hwe-6.8 (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Bugs reintroduced with linux-image-6.8.0-40-generic on T14 AMD Gen3

Status in linux-hwe-6.8 package in Ubuntu:
  Invalid

Bug description:
  With kernel version 6.8.0-40 bugs are reintroduced that were already
  fixed.

  Hardware:
  OS: Xubuntu 22.04.4 LTS x86_64 
  Host: 21CF004NGE ThinkPad T14 Gen 3 
  Kernel: 6.5.0-45-generic 
  Resolution: 1920x1200 
  DE: Xfce 4.16 
  WM: Xfwm4 
  CPU: AMD Ryzen 7 PRO 6850U with Radeon Graphics (16) @ 4.768GHz 
  GPU: AMD ATI 04:00.0 Rembrandt 
  Memory: 2034MiB / 14737MiB 

  
  Regression 1:
  The micled problem is reintroduced, where the micled keeps lit regardless of 
mute/unmute status

  Regression 2:
  Connection to bluetooth speakers or headsets not possible anymore

  The good:
  amdgpu driver doesnt crash anymore when on laptop lid close and open.

  Thanks for reading.
  Best regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.8/+bug/2077472/+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 2077159] Re: i40e interfaces renamed after upgrade from hwe-6.5

[Philip Cox]

** Changed in: linux (Ubuntu)
 Assignee: Philip Cox (philcox) => Bethany Jamison (bjamison)

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

Title:
  i40e interfaces renamed after upgrade from hwe-6.5

Status in linux package in Ubuntu:
  New

Bug description:
  Server running Ubuntu 22.04.4 LTS

  Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:

  3: eno1:  mtu 9100 qdisc mq state DOWN 
mode DEFAULT group default qlen 1000
  altname enp102s0f0
  4: eno5:  mtu 1500 qdisc mq state DOWN 
mode DEFAULT group default qlen 1000
  altname enp183s0f0
  6: eno2:  mtu 1500 qdisc mq master mgmt 
state UP mode DEFAULT group default qlen 1000
  altname enp102s0f1
  7: eno6:  mtu 1500 qdisc mq master mgmt 
state DOWN mode DEFAULT group default qlen 1000
  altname enp183s0f1
  8: eno3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  altname enp102s0f2
  9: eno7:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  altname enp183s0f2
  10: eno4:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  altname enp102s0f3
  11: eno8:  mtu 1500 qdisc mq state DOWN 
mode DEFAULT group default qlen 1000
  altname enp183s0f3

  Interface names with linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3:

  3: eno5np0:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000 
  altname enp183s0f0np0 

 
  4: eno1:  mtu 9100 qdisc mq state DOWN 
mode DEFAULT group default qlen 1000
 
  altname enp102s0f0

 
  5: enp101s0f1np1:  mtu 9100 qdisc mq state 
DOWN mode DEFAULT group default qlen 1000
  6: eno2:  mtu 1500 qdisc mq master mgmt 
state UP mode DEFAULT group default qlen 1000
  altname enp102s0f1

 
  7: eno6np1:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  altname enp183s0f1np1 

 
  8: eno3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  altname enp102s0f2
 
  9: eno7np2:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  altname enp183s0f2np2 
 
  10: eno4:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  altname enp102s0f3
 
  11: eno8np3:  mtu 1500 qdisc noop state DOWN mode 
DEFAULT group default qlen 1000
  altname enp183s0f3np3

  Expected result: Static network configuration via netplan keeps
  working after the upgrade.

  Actual result: Static network configuration is no longer applied for the 
interface that changed their name.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 16 09:40 seq
   crw-rw 1 root audio 116, 33 Aug 16 09:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.6
  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
  CasperMD5json:
   {
 "result": "skip"
   }
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-12-04 (260 days ago)
  InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release 
amd64 (20230217.1)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Supermicro SYS-5019D-FN8TP
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic 
root=/dev/mapper/system-root ro
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  RebootRequiredPkgs: Err

[Kernel-packages] [Bug 2077823] Re: AX88179_178a USB-ethernet adapter not always initializes properly with the kernel 6.8

[Philip Cox]

> > It looks like the upstream patches required does include the one you
noted, but one other one as well.

> So, you mean that the next kernel package will contain the fix? It
would be great.

I will work on getting these patches in to the ubuntu kernel.

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

Title:
  AX88179_178a USB-ethernet adapter not always initializes properly with
  the kernel 6.8

Status in linux-hwe-6.8 package in Ubuntu:
  Triaged

Bug description:
  After upgrading the kernel packages to version 6.8 I encounter the
  following issue. My ax88179_178a-based USB-ethernet adapter sometimes
  does not initialize properly on the system boot. Approximately one
  time of five it comes up with the status "link down' ("link not
  detected"). Checking the physical connectivity shows no problems.
  Unplugging/plugging the cable does not help. Reloading the kernel
  module does help, i.e. after:

  sudo modprobe -r ax88179_178a && sudo modprobe ax88179_178a

  the link comes up and the problem goes away (until the moment when it
  appears again five or six reboots later).

  The issue is apparently sourced from here:
  https://lore.kernel.org/all/20240523130330.215273...@linuxfoundation.org/

  And it is probably solved already in the kernel 6.9.7:
  https://lwn.net/Articles/979848/

  It would be nice, if you backport the solution into Ubuntu 6.8 kernel
  (if I am right and this indeed is a solution).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.8/+bug/2077823/+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 2077082] Re: package linux-hwe-6.8-tools-6.8.0-40 6.8.0-40.40~22.04.3 failed to install/upgrade: problemas de dependência - deixando desconfigurado

[Philip Cox]

> With Ubuntu Live Patch turned on, will I be able to receive kernel
update according to Canonical's updates?


If you have Live Patch enabled, and it is set up and running on your machine, 
yes, you should receive kernel security updates.

Here is the documentation about Live Patch:
https://ubuntu.com/security/livepatch

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

Title:
  package linux-hwe-6.8-tools-6.8.0-40 6.8.0-40.40~22.04.3 failed to
  install/upgrade: problemas de dependência - deixando desconfigurado

Status in linux-hwe-6.8 package in Ubuntu:
  Invalid

Bug description:
  Computer was in sleep mode. Opened up the lid and got the error.
  Thinkpad L14 Gen 2 operating with liquorix kernel 6.8.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-hwe-6.8-tools-6.8.0-40 6.8.0-40.40~22.04.3
  Uname: Linux 6.9.12-1-liquorix-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   linux-image-6.5.0-1027-oem:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Aug 15 12:57:58 2024
  ErrorMessage: problemas de dependência - deixando desconfigurado
  InstallationDate: Installed on 2023-05-15 (457 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.3
   apt  2.4.12
  SourcePackage: linux-hwe-6.8
  Title: package linux-hwe-6.8-tools-6.8.0-40 6.8.0-40.40~22.04.3 failed to 
install/upgrade: problemas de dependência - deixando desconfigurado
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.8/+bug/2077082/+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 2078054] Re: Kernel 6.8 causes the screen to intermittently go black for several seconds

[Philip Cox]

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

Hi Paddy, thank you for taking the time to report this issue.

This looks like a duplicate of https://bugs.launchpad.net/bugs/2062951

If you disagree with this, please re-open this ticket, and include the
output from the command "lsmod" using both the Ubuntu kernel, and the
third party kernel you have installed.

I can examine the kernel modules that are loaded, and different between
the two kernels, and see if this is indeed the likely cause of this
behaviour.

In my experience, a missing driver would not cause intermittent issues
as you describe, but LP# 2062951 seems much more likely.

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

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

** This bug has been marked a duplicate of bug 2062951
   Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.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/2078054

Title:
  Kernel 6.8 causes the screen to intermittently go black for several
  seconds

Status in linux package in Ubuntu:
  New

Bug description:
  Since kernel 6.8, the screen has been going black intermittently and
  unpredictably for several seconds. Sometimes it happens several times
  in a row over half a minute or so, and other times just once. It
  happens regularly.

  dmesg shows this type of error every time:

  [ 7912.265657] usb 1-9: USB disconnect, device number 17
  [ 7913.557402] usb 1-9: new full-speed USB device number 18 using xhci_hcd
  [ 7913.685271] usb 1-9: New USB device found, idVendor=1fd2, idProduct=8105, 
bcdDevice= 1.00
  [ 7913.685275] usb 1-9: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 7913.685277] usb 1-9: Product: LGDisplay Incell Touch
  [ 7913.685278] usb 1-9: Manufacturer: Melfas
  [ 7913.690820] input: Melfas LGDisplay Incell Touch as 
/devices/pci:00/:00:14.0/usb1/1-9/1-9:1.0/0003:1FD2:8105.001F/input/input45
  [ 7913.691112] hid-multitouch 0003:1FD2:8105.001F: input,hidraw2: USB HID 
v1.11 Device [Melfas LGDisplay Incell Touch] on usb-:00:14.0-9/input0
  [ 7913.691960] hid-generic 0003:1FD2:8105.0020: hiddev1,hidraw3: USB HID 
v1.11 Device [Melfas LGDisplay Incell Touch] on usb-:00:14.0-9/input1

  This is quite possibly connected to bug #2049248 because the
  workaround that has been pointed out to me works also for this bug.

  WORKAROUND:

  From what I understand, Canonical's kernel has had some drivers
  removed, causing this problem. I am now using the kernel as provided
  by Zabbly [1], which is Canonical's kernel but with the drivers left
  in.

  [1] https://github.com/zabbly/linux

  Discussion on Ubuntu Forums for this bug [2] and bug #2049248 [3].

  [2] https://ubuntuforums.org/showthread.php?t=2499896

  [3] https://ubuntuforums.org/showthread.php?t=2494260

  Software: Ubuntu 22.04 with Pro enabled.

  Hardware: Dell OptiPlex 5480 AIO All-In-One with a touchscreen monitor

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3
  ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 12:56:20 2024
  InstallationDate: Installed on 2022-08-28 (731 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: linux-signed-hwe-6.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078054/+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 2078054] Re: Kernel 6.8 causes the screen to intermittently go black for several seconds

[Philip Cox]

** Package changed: linux-signed-hwe-6.8 (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

Title:
  Kernel 6.8 causes the screen to intermittently go black for several
  seconds

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since kernel 6.8, the screen has been going black intermittently and
  unpredictably for several seconds. Sometimes it happens several times
  in a row over half a minute or so, and other times just once. It
  happens regularly.

  dmesg shows this type of error every time:

  [ 7912.265657] usb 1-9: USB disconnect, device number 17
  [ 7913.557402] usb 1-9: new full-speed USB device number 18 using xhci_hcd
  [ 7913.685271] usb 1-9: New USB device found, idVendor=1fd2, idProduct=8105, 
bcdDevice= 1.00
  [ 7913.685275] usb 1-9: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 7913.685277] usb 1-9: Product: LGDisplay Incell Touch
  [ 7913.685278] usb 1-9: Manufacturer: Melfas
  [ 7913.690820] input: Melfas LGDisplay Incell Touch as 
/devices/pci:00/:00:14.0/usb1/1-9/1-9:1.0/0003:1FD2:8105.001F/input/input45
  [ 7913.691112] hid-multitouch 0003:1FD2:8105.001F: input,hidraw2: USB HID 
v1.11 Device [Melfas LGDisplay Incell Touch] on usb-:00:14.0-9/input0
  [ 7913.691960] hid-generic 0003:1FD2:8105.0020: hiddev1,hidraw3: USB HID 
v1.11 Device [Melfas LGDisplay Incell Touch] on usb-:00:14.0-9/input1

  This is quite possibly connected to bug #2049248 because the
  workaround that has been pointed out to me works also for this bug.

  WORKAROUND:

  From what I understand, Canonical's kernel has had some drivers
  removed, causing this problem. I am now using the kernel as provided
  by Zabbly [1], which is Canonical's kernel but with the drivers left
  in.

  [1] https://github.com/zabbly/linux

  Discussion on Ubuntu Forums for this bug [2] and bug #2049248 [3].

  [2] https://ubuntuforums.org/showthread.php?t=2499896

  [3] https://ubuntuforums.org/showthread.php?t=2494260

  Software: Ubuntu 22.04 with Pro enabled.

  Hardware: Dell OptiPlex 5480 AIO All-In-One with a touchscreen monitor

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3
  ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 12:56:20 2024
  InstallationDate: Installed on 2022-08-28 (731 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: linux-signed-hwe-6.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078054/+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 2077920] Re: [RTL8821CE] awful performance

[Philip Cox]

Can you describe the "awful" performance in more detail?

If the bad performance is just in using the machine, if you disable
WiFi, how responsive is the machine?  If you can see the sluggishness
without a network connection, can you try to see if it happens when the
wifi is disabled or in airplane mode?


If the machine is still sluggish when not connected to the network, can
you run something like "htop" or System Monitor, and tell me what does
the CPU, memory, and swap usage look like?

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

Title:
  [RTL8821CE] awful performance

Status in linux package in Ubuntu:
  New

Bug description:
  In most application there is "not responding" window displayed.
  Firefox, Google Chrome, Google Remote Desktopm (=Chrome). In Google
  Remote Desktop the sound is transfered in a "okish" delay. The display
  of the remote machine is delayed by about 2-5 seconds.

  The laptop is connected by wifi, the remote machine is connected by lan cable.
  The problem also occur if the laptop is used in the same network about 2-3 
meters away.

  There seems to be a driver issue. If graphic, "chipset", ram or harddisk: I 
dont know. The machine is very old but is quad core with 4 gb of ram. There 
SHOULD be a better performance.
  I used a dual core about 3-4 years ago and the performance was similar to 
this laptop now.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 27 05:28:35 2024
  DistUpgraded: 2024-05-10 01:30:53,777 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev d4) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Stoney [Radeon R2/R3/R4/R5 Graphics] 
[103c:84d0]
  InstallationDate: Installed on 2023-08-26 (366 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: HP HP Laptop 17-ca0xxx
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-generic 
root=UUID=23ccbdb2-528b-483e-9b2f-bd788ab9318a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-05-09 (109 days ago)
  dmi.bios.date: 11/27/2023
  dmi.bios.release: 15.66
  dmi.bios.vendor: AMI
  dmi.bios.version: F.66
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 84D0
  dmi.board.vendor: HP
  dmi.board.version: 90.48
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 90.48
  dmi.modalias: 
dmi:bvnAMI:bvrF.66:bd11/27/2023:br15.66:efr90.48:svnHP:pnHPLaptop17-ca0xxx:pvr:rvnHP:rn84D0:rvr90.48:cvnHP:ct10:cvrChassisVersion:sku5CU45EA#ABD:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 17-ca0xxx
  dmi.product.sku: 5CU45EA#ABD
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077920/+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 2077920] Re: [RTL8821CE] awful performance

[Philip Cox]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

Title:
  [RTL8821CE] awful performance

Status in linux package in Ubuntu:
  New

Bug description:
  In most application there is "not responding" window displayed.
  Firefox, Google Chrome, Google Remote Desktopm (=Chrome). In Google
  Remote Desktop the sound is transfered in a "okish" delay. The display
  of the remote machine is delayed by about 2-5 seconds.

  The laptop is connected by wifi, the remote machine is connected by lan cable.
  The problem also occur if the laptop is used in the same network about 2-3 
meters away.

  There seems to be a driver issue. If graphic, "chipset", ram or harddisk: I 
dont know. The machine is very old but is quad core with 4 gb of ram. There 
SHOULD be a better performance.
  I used a dual core about 3-4 years ago and the performance was similar to 
this laptop now.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 27 05:28:35 2024
  DistUpgraded: 2024-05-10 01:30:53,777 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev d4) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Stoney [Radeon R2/R3/R4/R5 Graphics] 
[103c:84d0]
  InstallationDate: Installed on 2023-08-26 (366 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: HP HP Laptop 17-ca0xxx
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-generic 
root=UUID=23ccbdb2-528b-483e-9b2f-bd788ab9318a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-05-09 (109 days ago)
  dmi.bios.date: 11/27/2023
  dmi.bios.release: 15.66
  dmi.bios.vendor: AMI
  dmi.bios.version: F.66
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 84D0
  dmi.board.vendor: HP
  dmi.board.version: 90.48
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 90.48
  dmi.modalias: 
dmi:bvnAMI:bvrF.66:bd11/27/2023:br15.66:efr90.48:svnHP:pnHPLaptop17-ca0xxx:pvr:rvnHP:rn84D0:rvr90.48:cvnHP:ct10:cvrChassisVersion:sku5CU45EA#ABD:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 17-ca0xxx
  dmi.product.sku: 5CU45EA#ABD
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077920/+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 2077945] Re: Error On Automatic suspend after sleep

[Philip Cox]

Hello, thank you for taking the time to open this bug report.

I see in the dmesg you've included, you have the kernel command line
option "acpi_sleep=deep" set.

1) Why is this set?

2) Can you please give me the output of the command: 
  cat /sys/power/mem_sleep

3) Can you please tell me how you are trying to suspend/sleep the
machine?  Using the GUI, or via the command line?

4) Also, can you check the BIOS settings for any options concerning
sleep/suspending the machine?  this might be more tricky because each
bios may have different options.  It might be under the ACPI section.
If you can share any options and their values, it might be helpful.

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

Title:
  Error On Automatic suspend after sleep

Status in linux package in Ubuntu:
  New

Bug description:
  When the system goes to sleep and automatic suspend , i cant wake the
  system instead it goes to a black screen. and also the fan speen
  raises . i dont know wheather the problem is with the kernal version
  or with my graphic driver.I had checked if the issue persist on
  downgrading the kernal version but the issue still persist.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-41-generic 6.8.0-41.41
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:prayag 2179 F pipewire
   /dev/snd/controlC0:  prayag 2183 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 27 13:13:36 2024
  InstallationDate: Installed on 2024-08-23 (3 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 25a7:fa70 Areson Technology Corp Hydra 10
   Bus 001 Device 003: ID 1ea7:0066 SHARKOON Technologies GmbH [Mediatrack Edge 
Mini Keyboard]
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: Micro-Star International Co., Ltd. GF63 Thin 9SCSR
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-generic 
root=UUID=56a0ebbe-0013-4945-917b-97c6d1ab0c73 ro quiet splash acpi_sleep=deep 
vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-41-generic N/A
   linux-backports-modules-6.8.0-41-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2020
  dmi.bios.release: 5.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16R4IMS.505
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16R4
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16R4IMS.505:bd11/05/2020:br5.5:svnMicro-StarInternationalCo.,Ltd.:pnGF63Thin9SCSR:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16R4:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku16R4.5:
  dmi.product.family: GF
  dmi.product.name: GF63 Thin 9SCSR
  dmi.product.sku: 16R4.5
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077945/+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 2077945] Re: Error On Automatic suspend after sleep

[Philip Cox]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Philip Cox (philcox)

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

Title:
  Error On Automatic suspend after sleep

Status in linux package in Ubuntu:
  New

Bug description:
  When the system goes to sleep and automatic suspend , i cant wake the
  system instead it goes to a black screen. and also the fan speen
  raises . i dont know wheather the problem is with the kernal version
  or with my graphic driver.I had checked if the issue persist on
  downgrading the kernal version but the issue still persist.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-41-generic 6.8.0-41.41
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:prayag 2179 F pipewire
   /dev/snd/controlC0:  prayag 2183 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 27 13:13:36 2024
  InstallationDate: Installed on 2024-08-23 (3 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 25a7:fa70 Areson Technology Corp Hydra 10
   Bus 001 Device 003: ID 1ea7:0066 SHARKOON Technologies GmbH [Mediatrack Edge 
Mini Keyboard]
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: Micro-Star International Co., Ltd. GF63 Thin 9SCSR
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-41-generic 
root=UUID=56a0ebbe-0013-4945-917b-97c6d1ab0c73 ro quiet splash acpi_sleep=deep 
vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-41-generic N/A
   linux-backports-modules-6.8.0-41-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2020
  dmi.bios.release: 5.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16R4IMS.505
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16R4
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16R4IMS.505:bd11/05/2020:br5.5:svnMicro-StarInternationalCo.,Ltd.:pnGF63Thin9SCSR:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16R4:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku16R4.5:
  dmi.product.family: GF
  dmi.product.name: GF63 Thin 9SCSR
  dmi.product.sku: 16R4.5
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077945/+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 2077291] Re: i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun in Ubuntu 22.04.4 LTS

[Philip Cox]

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

** This bug has been marked a duplicate of bug 2062951
   Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)

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

Title:
  i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun in Ubuntu
  22.04.4 LTS

Status in linux-signed-hwe-6.8 package in Ubuntu:
  Incomplete

Bug description:

  
  The screen flickers occasionally, specifically at night, since i added a RAM 
slot DDR4 in my laptop, i thought the RAM got loose, but i didn't see any 
errors in memory,
  so I ran command: "journalctl -p err -b"
  Got this in the logs from august 18 & august 19,2024:

  अगस्त 18 21:36:48 itsjustme-Lenovo-ideapad-320-15ISK kernel: i915 
:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
  अगस्त 19 09:54:14 itsjustme-Lenovo-ideapad-320-15ISK kernel: i915 
:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

  I have not tried to troubleshoot it yet, but i surfed the internet and
  got some hints :

  work with ubuntu kernel 5.15.0-39
  work with ubuntu kernel 5.15.0-46 and set 
GRUB_CMDLINE_LINUX="i915.enable_psr=0 intel_idle.max_cstate=2" into 
/etc/default/grub

  i haven't tried the commands but it would definitely be helpful if you
  explained what this does, and what exactly the problem is. I am
  looking forward for your reply and appreciate any help. Thanks! Have a
  great day.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3
  ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 19 10:04:26 2024
  InstallationDate: Installed on 2024-04-11 (129 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-hwe-6.8
  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.8/+bug/2077291/+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 2077218] Re: No signal for hdmi monitor (i915)

[Philip Cox]

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

** This bug is no longer a duplicate of bug 2077220
   (i915) external monitor flickering  in 6.8.0-40.40~22.04.3
** This bug has been marked a duplicate of bug 2062951
   Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.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/2077218

Title:
  No signal for hdmi monitor (i915)

Status in linux package in Ubuntu:
  New

Bug description:
  After I change my kernel to 6.8.0-40 I loose support to multiples
  monitors (using hdmi), before that I'm using the laptop monitor + hdmi
  external monitor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077218/+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 2077220] Re: (i915) external monitor flickering in 6.8.0-40.40~22.04.3

[Philip Cox]

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

I agree, this looks like a duplicate of LP# 2062951 so I have marked it
as such.

** This bug has been marked a duplicate of bug 2062951
   Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)

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

Title:
  (i915) external monitor flickering  in 6.8.0-40.40~22.04.3

Status in linux-hwe-6.8 package in Ubuntu:
  Confirmed

Bug description:
  I used sudo apt-get upgrade in Ubuntu 22.04.4 .
  Then karnel upgraded from 6.5.0-45.45~22.04.1 to 6.8.0-40.40~22.04.3.
  Now I am facing problem to my external monitor(1920x1080), that was blinking.
  Setting low resolution(ex:1680x1050) from settings for this monitor, blinking 
has gone.
  Another soluton That cause huze performance:- Changing karnel 
6.5.0-45.45~22.04.1 to 6.8.0-40.40~22.04.3 at the time of booting.

  I tried Ubuntu 24.04, But it has the same blinking problem.

  https://youtu.be/-BXSe5k0SAk

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.19
  ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CrashReports:
   640:0:124:4591909:2024-08-16 14:51:16.012351512 +0600:2024-08-16 
14:51:17.012351512 +0600:/var/crash/_usr_bin_grub-customizer.0.crash
   640:1000:124:536484:2024-08-16 23:46:35.262295246 +0600:2024-08-16 
23:46:36.262295246 +0600:/var/crash/_opt_google_chrome_chrome.1000.crash
   640:1000:124:12891878:2024-08-17 11:33:47.537503242 +0600:2024-08-17 
11:33:48.537503242 +0600:/var/crash/_usr_lib_slack_slack.1000.crash
   640:1000:124:1791389:2024-08-15 14:35:36.782359123 +0600:2024-08-15 
17:07:21.757640327 +0600:/var/crash/_usr_libexec_tracker-extract-3.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 17 14:43:12 2024
  InstallationDate: Installed on 2024-03-09 (161 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.8/+bug/2077220/+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 2077976] Re: mlxbf_livefish: driver build fails if CONFIG_ACPI not set

[Philip Cox]

** Changed in: linux-bluefield (Ubuntu)
 Assignee: (unassigned) => Bartlomiej Zolnierkiewicz (bzolnier)

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

Title:
  mlxbf_livefish: driver build fails if CONFIG_ACPI not set

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]

  The mlxbf_livefish driver depends on CONFIG_ACPI but that requirement
  is not specified in the driver's Kconfig.  So, any attempt to build a
  kernel with CONFIG_ACPI not set and CONFIG_MLXBF_LIVEFISH set will 
  result in a build error.

  [Fix]

  * Update the Kconfig file in drivers/platform/mellanox to specify
the CONFIG_ACPI dependency

  [Test Case]

  * Clear CONFIG_ACPI in kernel configuration
  * Verify there is no option to configure mlxbf_livefish driver
  * Verify that no build errors result

  [Regression Potential]

  * no known regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2077976/+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 2077966] Re: screen blinks sometime

[Philip Cox]

Hi Ayush,

Thank you for taking the time to open this bug report.

Unfortunately there is not enough information for us to look into this
at the moment.

Please run the command "apport-collect 2077966" to collect and add
information to the ticket, and please try to describe the scenario a
little more.  Are you using a laptop?  A desktop?  How many monitors are
connected?  How is it attached?  HDMI? DisplayPort?  VGA/DVI?

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

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

Title:
  screen blinks sometime

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  screen blinks sometime if I stop moving cursor and specially lower right 
section of laptop screen
  its intensity increase.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077966/+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 2076986] Re: Lenovo Touchpad not working or detected in 'Lenovo Legion 9 16IRX9' following Ubuntu 22.04 installation.

[Philip Cox]

Hi Cara, thanks for the update.

I've gone over the info provided and I don't see any clear pointers as
to what the issue may be.

Two things come to mind to try though.

1) the laptop you are using is fairly new.  Perhaps the support in the
Noble (24.04) Ubuntu version would be better for the hardware.  I
understand that the kernel may be the same, but there are other
libraries that may be involved.  If you made a bootable USB drive with
the 24.04 Ubuntu image, it would allow you to boot in to it, and just
see if the trackpad work, or the speakers work.  That would be useful to
know.

2) if you could run "apport-collect 2076986" which will include much
more system information, and I can dig through to see what I Can find to
help resolve this.

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

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

Title:
  Lenovo Touchpad not working or detected in 'Lenovo Legion 9 16IRX9'
  following Ubuntu 22.04 installation.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The Lenovo Legion 9 touchpad on my laptop is unresponsive after
  installing Ubuntu 22.04. How might I get it working again? A lot of
  solutions suggested to downgrade the kernel but the posts I found were
  from 2+ years ago.

  Below is the output from 'cat /proc/bus/input/devices'. Note that the
  Logitech mouse is a (functional) wired mouse I was using at the time.

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
  U: Uniq=
  H: Handlers=kbd event0
  B: PROP=0
  B: EV=3
  B: KEY=8000 10 0

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
  U: Uniq=
  H: Handlers=event1
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2
  B: PROP=0
  B: EV=3
  B: KEY=8000 10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=046d Product=c050 Version=0110
  N: Name="Logitech USB-PS/2 Optical Mouse"
  P: Phys=usb-:00:14.0-4/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:046D:C050.0003/input/input4
  U: Uniq=
  H: Handlers=mouse0 event4
  B: PROP=0
  B: EV=17
  B: KEY=ff 0 0 0 0
  B: REL=1943
  B: MSC=10

  I: Bus=0003 Vendor=048d Product=c990 Version=0110
  N: Name="ITE Tech. Inc. ITE Device(8258) Keyboard"
  P: Phys=usb-:00:14.0-6/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:048D:C990.0004/input/input5
  U: Uniq=
  H: Handlers=sysrq kbd event5 leds
  B: PROP=0
  B: EV=12001f
  B: KEY=33eff 0 0 48317aff32d bfd6 1 130c730b17c007 
ffbf7bfad9415fff febeffdfffef fffe
  B: REL=1040
  B: ABS=1
  B: MSC=10
  B: LED=1f

  I: Bus=0003 Vendor=048d Product=c990 Version=0110
  N: Name="ITE Tech. Inc. ITE Device(8258)"
  P: Phys=usb-:00:14.0-6/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:048D:C990.0004/input/input6
  U: Uniq=
  H: Handlers=event6
  B: PROP=0
  B: EV=9
  B: ABS=100

  I: Bus=0003 Vendor=048d Product=c990 Version=0110
  N: Name="ITE Tech. Inc. ITE Device(8258) Wireless Radio Control"
  P: Phys=usb-:00:14.0-6/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:048D:C990.0004/input/input7
  U: Uniq=
  H: Handlers=rfkill kbd event7
  B: PROP=0
  B: EV=13
  B: KEY=80 0 0 0
  B: MSC=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input8
  U: Uniq=
  H: Handlers=event8
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input9
  U: Uniq=
  H: Handlers=event9
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=8"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input10
  U: Uniq=
  H: Handlers=event10
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=9"
  P: Phys=ALSA
  S

[Kernel-packages] [Bug 2076986] Re: Lenovo Touchpad not working or detected in 'Lenovo Legion 9 16IRX9' following Ubuntu 22.04 installation.

[Philip Cox]

** Package changed: linux-signed-hwe-6.8 (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/2076986

Title:
  Lenovo Touchpad not working or detected in 'Lenovo Legion 9 16IRX9'
  following Ubuntu 22.04 installation.

Status in linux package in Ubuntu:
  New

Bug description:
  The Lenovo Legion 9 touchpad on my laptop is unresponsive after
  installing Ubuntu 22.04. How might I get it working again? A lot of
  solutions suggested to downgrade the kernel but the posts I found were
  from 2+ years ago.

  Below is the output from 'cat /proc/bus/input/devices'. Note that the
  Logitech mouse is a (functional) wired mouse I was using at the time.

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
  U: Uniq=
  H: Handlers=kbd event0
  B: PROP=0
  B: EV=3
  B: KEY=8000 10 0

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
  U: Uniq=
  H: Handlers=event1
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2
  B: PROP=0
  B: EV=3
  B: KEY=8000 10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=046d Product=c050 Version=0110
  N: Name="Logitech USB-PS/2 Optical Mouse"
  P: Phys=usb-:00:14.0-4/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:046D:C050.0003/input/input4
  U: Uniq=
  H: Handlers=mouse0 event4
  B: PROP=0
  B: EV=17
  B: KEY=ff 0 0 0 0
  B: REL=1943
  B: MSC=10

  I: Bus=0003 Vendor=048d Product=c990 Version=0110
  N: Name="ITE Tech. Inc. ITE Device(8258) Keyboard"
  P: Phys=usb-:00:14.0-6/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:048D:C990.0004/input/input5
  U: Uniq=
  H: Handlers=sysrq kbd event5 leds
  B: PROP=0
  B: EV=12001f
  B: KEY=33eff 0 0 48317aff32d bfd6 1 130c730b17c007 
ffbf7bfad9415fff febeffdfffef fffe
  B: REL=1040
  B: ABS=1
  B: MSC=10
  B: LED=1f

  I: Bus=0003 Vendor=048d Product=c990 Version=0110
  N: Name="ITE Tech. Inc. ITE Device(8258)"
  P: Phys=usb-:00:14.0-6/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:048D:C990.0004/input/input6
  U: Uniq=
  H: Handlers=event6
  B: PROP=0
  B: EV=9
  B: ABS=100

  I: Bus=0003 Vendor=048d Product=c990 Version=0110
  N: Name="ITE Tech. Inc. ITE Device(8258) Wireless Radio Control"
  P: Phys=usb-:00:14.0-6/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:048D:C990.0004/input/input7
  U: Uniq=
  H: Handlers=rfkill kbd event7
  B: PROP=0
  B: EV=13
  B: KEY=80 0 0 0
  B: MSC=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input8
  U: Uniq=
  H: Handlers=event8
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input9
  U: Uniq=
  H: Handlers=event9
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=8"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input10
  U: Uniq=
  H: Handlers=event10
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia HDMI/DP,pcm=9"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card0/input11
  U: Uniq=
  H: Handlers=event11
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:03/LNXVIDEO:00/input/input12
  U: Uniq=
  H: Handlers=kbd event12
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input13
  U: Uniq=
  H: Handlers=kbd event13
  B: PROP=0
  B: EV=3
  B: KEY=3e000b0

[Kernel-packages] [Bug 2077860] Re: Black screen upon waking from suspend; keyboard mostly unresponsive; issue resolved by using previous kernel version.

[Philip Cox]

Thanks for the update, and providing the data requested.  I will go over
the included info.

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/2077860

Title:
  Black screen upon waking from suspend; keyboard mostly unresponsive;
  issue resolved by using previous kernel version.

Status in linux package in Ubuntu:
  New

Bug description:
  Description: When I put my laptop into suspend and attempt to wake it,
  the screen remains black. This issue does not occur when rebooting or
  booting from a shutdown state. Additionally, the keyboard does not
  respond as expected; for example, pressing Alt + F2/F3 or trying to
  switch to an external screen using Super/Meta + P has no effect.
  However, I can perform a soft reboot using Ctrl + Alt + PrntScr +
  REISUB.

  This issue occurs both with and without Wayland disabled. I attempted
  the following modifications in the GRUB configuration without success:

  GRUB_CMD_LINUX="nouveau.modeset=0"
  GRUB_CMDLINE_LINUX="nouveau.blacklist=1"

  The issue was temporarily resolved by booting into the previous kernel
  version listed in Advanced Options for Ubuntu (6.5.0-45).

  Steps to Reproduce:

  Put the laptop into suspend mode.
  Attempt to wake the laptop from suspend.

  Expected Behavior: The screen should wake up normally, and the
  keyboard should be fully functional.

  Actual Behavior: The screen remains black, and the keyboard does not
  respond as expected.

  System Information:

  Description: Ubuntu 22.04.4 LTS x86_64
  Release: 22.04
  GNOME Version: 42.9
  CPU: 12th Gen Intel i7-1255U (12) @ 4.700GHz
  GPU: Intel Device 46a8
  Host: ThinkPad X1 Carbon Gen 10 (21CB009UGE)
  Kernel Version: 6.8.0-40-generic

  Additional Notes: The problem does not occur with the previous kernel version 
(6.5.0-45). Please advise on further troubleshooting steps or potential fixes.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  n0rdp0l1981 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-03-07 (538 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: LENOVO 21CB009UGE
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-40-generic 
root=UUID=feb85b6e-e87d-42c9-a3b0-56d5a9eb901e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-40-generic N/A
   linux-backports-modules-6.8.0-40-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.31
  Tags:  jammy
  Uname: Linux 6.8.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/24/2024
  dmi.bios.release: 1.46
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3AET81W (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CB009UGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 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.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3AET81W(1.46):bd04/24/2024:br1.46:efr1.24:svnLENOVO:pn21CB009UGE:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CB009UGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10:
  dmi.product.family: ThinkPad X1 Carbon Gen 10
  dmi.product.name: 21CB009UGE
  dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10
  dmi.product.version: ThinkPad X1 Carbon Gen 10
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077860/+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 2077575] Re: standby broken on ThinkPad 260 Yoga with 6.8

[Philip Cox]

I changed the package the ticket was opened against.  Can you try to run
the apport-collect again please?

** Package changed: linux-meta-hwe-6.8 (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/2077575

Title:
  standby broken on ThinkPad 260 Yoga with 6.8

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm on Ubuntu 22.04 with HWE, so I recently got the upgrade from 6.5
  to 6.8 and since then, standby doesn't work anymore. The screen goes
  black, the keyboard backlight goes off and the status LED goes from on
  to fading, but the fan and the LEDs on the keyboard stay on.

  The laptop also doesn't wake up anymore.

  The logs end here:

  Aug 21 20:57:20 systemd[1]: Starting System Suspend...
  Aug 21 20:57:20 wpa_supplicant[1259]: wlp4s0: CTRL-EVENT-DSCP-POLICY clear_all
  Aug 21 20:57:20 wpa_supplicant[1259]: wlp4s0: CTRL-EVENT-DSCP-POLICY clear_all
  Aug 21 20:57:20 wpa_supplicant[1259]: nl80211: deinit ifname=wlp4s0 
disabled_11b_rates=0
  Aug 21 20:57:20 systemd[1]: grub-common.service: Deactivated successfully.
  Aug 21 20:57:20 systemd[1]: Finished Record successful boot for GRUB.
  Aug 21 20:57:20 systemd-sleep[2204]: Entering sleep state 'suspend'...
  Aug 21 20:57:20 kernel: PM: suspend entry (deep)

  whereas they continue on 6.5:

  Aug 21 21:03:03 wpa_supplicant[1213]: wlp4s0: CTRL-EVENT-DSCP-POLICY clear_all
  Aug 21 21:03:03 wpa_supplicant[1213]: wlp4s0: CTRL-EVENT-DSCP-POLICY clear_all
  Aug 21 21:03:03 wpa_supplicant[1213]: nl80211: deinit ifname=wlp4s0 
disabled_11b_rates=0
  Aug 21 21:03:03 systemd-sleep[2158]: Entering sleep state 'suspend'...
  Aug 21 21:03:03 kernel: PM: suspend entry (deep)
  Aug 21 21:03:04 kernel: Filesystems sync: 0.392 seconds
  Aug 21 21:03:15 kernel: Freezing user space processes
  Aug 21 21:03:15 kernel: Freezing user space processes completed (elapsed 
0.001 seconds)
  Aug 21 21:03:15 kernel: OOM killer disabled.
  Aug 21 21:03:15 kernel: Freezing remaining freezable tasks
  Aug 21 21:03:15 kernel: Freezing remaining freezable tasks completed (elapsed 
0.001 seconds)
  Aug 21 21:03:15 kernel: printk: Suspending console(s) (use no_console_suspend 
to debug)
  Aug 21 21:03:15 kernel: e1000e: EEE TX LPI TIMER: 0011
  Aug 21 21:03:15 kernel: ACPI: EC: interrupt blocked
  Aug 21 21:03:15 kernel: ACPI: PM: Preparing to enter system sleep state S3
  Aug 21 21:03:15 kernel: ACPI: EC: event blocked
  Aug 21 21:03:15 kernel: ACPI: EC: EC stopped
  Aug 21 21:03:15 kernel: ACPI: PM: Saving platform NVS memory
  Aug 21 21:03:15 kernel: Disabling non-boot CPUs ...
  Aug 21 21:03:15 kernel: smpboot: CPU 1 is now offline
  Aug 21 21:03:15 kernel: smpboot: CPU 2 is now offline
  Aug 21 21:03:15 kernel: smpboot: CPU 3 is now offline
  Aug 21 21:03:15 kernel: ACPI: PM: Low-level resume complete
  Aug 21 21:03:15 kernel: ACPI: EC: EC started
  Aug 21 21:03:15 kernel: ACPI: PM: Restoring platform NVS memory
  Aug 21 21:03:15 kernel: Enabling non-boot CPUs ...
  Aug 21 21:03:15 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
  Aug 21 21:03:15 kernel: CPU1 is up
  Aug 21 21:03:15 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
  Aug 21 21:03:15 kernel: CPU2 is up
  Aug 21 21:03:15 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
  Aug 21 21:03:15 kernel: CPU3 is up
  Aug 21 21:03:15 kernel: ACPI: PM: Waking up from system sleep state S3
  Aug 21 21:03:15 kernel: ACPI: EC: interrupt unblocked
  Aug 21 21:03:15 kernel: ACPI: EC: event unblocked
  Aug 21 21:03:15 kernel: i915 :00:02.0: [drm] [ENCODER:94:DDI A/PHY A] is 
disabled/in DSI mode with an ungated>
  Aug 21 21:03:15 kernel: i915 :00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is 
disabled/in DSI mode with an ungate>
  Aug 21 21:03:15 kernel: i915 :00:02.0: [drm] [ENCODER:117:DDI C/PHY C] is 
disabled/in DSI mode with an ungate>
  Aug 21 21:03:15 kernel: nvme nvme0: Shutdown timeout set to 8 seconds
  Aug 21 21:03:15 kernel: nvme nvme0: 4/0/0 default/read/poll queues
  Aug 21 21:03:15 kernel: thinkpad_acpi: Unknown/reserved multi mode value 
0x for type 4, please report this to ibm-acpi-de...@lists.sourceforge.net
  Aug 21 21:03:15 kernel: usb 1-8: reset high-speed USB device number 3 using 
xhci_hcd
  Aug 21 21:03:15 kernel: usb 1-9: reset full-speed USB device number 4 using 
xhci_hcd
  Aug 21 21:03:15 kernel: OOM killer enabled.
  Aug 21 21:03:15 kernel: Restarting tasks ... done.
  Aug 21 21:03:15 kernel: random: crng reseeded on system resumption
  Aug 21 21:03:15 kernel: kauditd_printk_skb: 14405 callbacks suppressed
  Aug 21 21:03:15 systemd-resolved[708]: Clock change detected. Flushing caches.
  Aug 21 21:03:15 systemd-sleep[2158]: System returned from sleep state.
  Aug 21 21:03:15 kernel: PM: suspend exit
  Aug 21 21:03:15 systemd[1]: systemd-suspend.service: Deactivated successfully.
  Aug 21 21:03:15 systemd[1]: Finished System S

[Kernel-packages] [Bug 2077749] Re: Regression in Ubuntu 22.04 kernel 6.8.0 for module ath9k

[Philip Cox]

Thanks for providing the info.  I will go over the data.

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/2077749

Title:
  Regression in Ubuntu 22.04 kernel 6.8.0 for module ath9k

Status in linux package in Ubuntu:
  New

Bug description:
  Hi:

  Recent upgrade of the Linux kernel from 6.5 to 6.8 on Ubuntu 22.04
  broke my wifi atheros device functionality. Errors I am getting are
  pretty much the same error in kernel log. The regression makes my wifi
  unusable.

  Error:
  ath: phy0: DMA failed to stop in 10 ms AR_CR=0x0024 AR_DIAG_SW=0x0220 
DMADBG_7=0x6100

  Device: 04:00.0 Network controller: Qualcomm Atheros AR9462 Wireless
  Network Adapter (rev 01)

  Reverting back to kernel 6.5 fixes the issue.

  Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kon2887 F pulseaudio
   /dev/snd/pcmC1D0c:   kon2887 F...m pulseaudio
   /dev/snd/pcmC1D0p:   kon2887 F...m pulseaudio
   /dev/snd/controlC0:  kon2887 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  HibernationDevice:
   #RESUME=UUID=0af27d72-a014-4b03-bc9d-3a83ec3493c7
   RESUME=none
  InstallationDate: Installed on 2018-09-06 (2181 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK COMPUTER INC. G551JW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-41-generic 
root=UUID=fba1ce68-c157-431e-8b0c-13c48d42748f ro quiet splash 
cryptdevice=UUID=f31af448-5ede-43ab-b320-953466be3aba vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-41.41~22.04.2-generic 6.5.13
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-41-generic N/A
   linux-backports-modules-6.5.0-41-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.31
  Tags:  jammy
  Uname: Linux 6.5.0-41-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-27 (791 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/04/2016
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G551JW.209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G551JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG551JW.209:bd03/04/2016:br4.6:svnASUSTeKCOMPUTERINC.:pnG551JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG551JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: G
  dmi.product.name: G551JW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077749/+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 2077815] Re: Kernel 6.8: Incompatibility with NVIDIA Drivers Causing System Freezes, Crashes, and Suspend Failures

[Philip Cox]

Thank you for uploading the logs.  I will go over them.

** Changed in: linux-signed-hwe-6.8 (Ubuntu)
   Status: Incomplete => New

** Changed in: linux-signed-hwe-6.8 (Ubuntu)
   Importance: Undecided => High

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

Title:
  Kernel 6.8: Incompatibility with NVIDIA Drivers Causing System
  Freezes, Crashes, and Suspend Failures

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

Bug description:
  After upgrading to kernel 6.8 on Ubuntu 22.04.4, the system frequently
  freezes, crashes, and always fails to resume from suspend when using
  NVIDIA drivers (e.g., 535, 470). The issues do not occur with the
  Nouveau driver, nor do they occur with earlier kernels like 6.2,
  though I did experience occasional crashes in kernel 6.5. I haven't
  noticed anything revealing in the logs, other than:

  [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID
  0x0100] Failed to grab modeset ownership

  However, I see this error message with all kernel versions, including
  kernel 6.2 which works flawlessly, so I think it's unlikely it has
  anything to do with the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 25 07:29:29 2024
  InstallationDate: Installed on 2024-08-21 (3 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  SourcePackage: linux-signed-hwe-6.8
  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.8/+bug/2077815/+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 2077504] Re: Dell vostro 5481 does not go to suspend

[Philip Cox]

Thanks for providing the info as requested.  I will go over the data.

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

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Dell vostro 5481 does not go to suspend

Status in linux package in Ubuntu:
  New

Bug description:
  The system gets stuck with black  screen and I have to shut it down
  manually. On restart and shutdown it works normally.

  System info:

  [code]

  Kernel: 6.8.0-41-generic arch: x86_64 bits: 64 compiler: gcc v: 13.2.0 
clocksource: tsc
    Desktop: Cinnamon v: 6.2.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.2.0 tools: 
cinnamon-screensaver
  vt: 7 dm: LightDM v: 1.30.0 Distro: Linux Mint 22 Wilma base: Ubuntu 
24.04 noble
  Machine:
    Type: Laptop System: Dell product: Vostro 5481 v: N/A serial:  Chassis:
  type: 10 serial: 
    Mobo: Dell model: 05H37Y v: A00 serial:  part-nu: 08A7
  uuid:  UEFI: Dell v: 2.18.0 date: 11/11/2022
  Battery:
    ID-1: BAT0 charge: 39.1 Wh (100.0%) condition: 39.1/42.0 Wh (93.1%) volts: 
12.6 min: 11.4
  model: BYD DELL FW8KR38 type: Li-ion serial:  status: full
  CPU:
    Info: quad core model: Intel Core i7-8565U bits: 64 type: MT MCP smt: 
enabled arch: Whiskey Lake
  rev: B cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
    Speed (MHz): avg: 1631 high: 1831 min/max: 400/4600 cores: 1: 1831 2: 1806 
3: 1811 4: 1801
  5: 400 6: 1800 7: 1800 8: 1800 bogomips: 31999
    Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
    Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: Dell driver: 
i915 v: kernel
  arch: Gen-9.5 ports: active: DP-1 off: eDP-1 empty: HDMI-A-1,HDMI-A-2 
bus-ID: 00:02.0
  chip-ID: 8086:3ea0 class-ID: 0300
    Device-2: NVIDIA GM108M [GeForce MX130] vendor: Dell driver: nvidia v: 
535.183.01 arch: Maxwell
  pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 02:00.0 chip-ID: 10de:174d 
class-ID: 0302
    Device-3: Realtek Integrated_Webcam_HD driver: uvcvideo type: USB rev: 2.0 
speed: 480 Mb/s
  lanes: 1 bus-ID: 1-6:4 chip-ID: 0bda:5521 class-ID: 0e02 serial: 
    Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
  loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa dri: iris gpu: 
i915 display-ID: :0
  screens: 1
    Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1015x571mm (39.96x22.48")
  s-diag: 1165mm (45.85")
    Monitor-1: DP-1 pos: primary model: Acer B277K serial:  res: 
3840x2160 hz: 60 dpi: 164
  size: 596x336mm (23.46x13.23") diag: 684mm (26.9") modes: max: 3840x2160 
min: 640x480
    Monitor-2: eDP-1 note: disabled model: AU Optronics 0x453d res: 3840x2160 
dpi: 158
  size: 309x174mm (12.17x6.85") diag: 355mm (14") modes: 1920x1080
    API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0 drv: 
nvidia device: 1
  drv: iris device: 3 drv: swrast surfaceless: drv: nvidia x11: drv: iris
  inactive: gbm,wayland,device-2
    API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.0.9-0ubuntu0.1 
glx-v: 1.4
  direct-render: yes renderer: Mesa Intel UHD Graphics 620 (WHL GT2) 
device-ID: 8086:3ea0
  Audio:
    Device-1: Intel Cannon Point-LP High Definition Audio vendor: Dell driver: 
snd_hda_intel
  v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9dc8 class-ID: 0403
    API: ALSA v: k6.8.0-40-generic status: kernel-api
    Server-1: PipeWire v: 1.0.5 status: active with: 1: pipewire-pulse status: 
active
  2: wireplumber status: active 3: pipewire-alsa type: plugin
  Network:
    Device-1: Intel Cannon Point-LP CNVi [Wireless-AC] driver: iwlwifi v: 
kernel bus-ID: 00:14.3
  chip-ID: 8086:9df0 class-ID: 0280
    IF: wlo1 state: up mac: 
    Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
  vendor: Dell RTL8111/8168/8411 driver: r8169 v: kernel pcie: speed: 
Unknown lanes: 63 port: 3000
  bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
    IF: enp3s0 state: down mac: 
  Bluetooth:
    Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) driver: btusb v: 
0.8 type: USB rev: 2.0
  speed: 12 Mb/s lanes: 1 bus-ID: 1-10:5 chip-ID: 8087:0aaa class-ID: e001
    Report: hciconfig ID: hci0 rfk-id: 1 state: up address:  bt-v: 5.1 
lmp-v: 10 sub-v: 100
  hci-v: 10 rev: 100 class-ID: 7c010c
  Drives:
    Local Storage: total: 1.38 TiB used: 406.21 GiB (28.8%)
    ID-1: /dev/nvme0n1 vendor: Transcend model: TS512GMTE220S size: 476.94 GiB 
speed: 31.6 Gb/s
  lanes: 4 tech: SSD serial:  fw-rev: 42A7T36A temp: 40.9 C scheme: 
GPT
    ID-2: /dev/sda vendor: Western Digital model: WD10SPZX-24Z10T0 size: 931.51 
GiB speed: 6.0 Gb/s
  tech: HDD rpm: 5400 serial:  fw-rev: 1A01
  Partition:
    ID-1: / size: 467.89 GiB used: 120.09 GiB (25.7%) fs: ext4 dev: 
/dev/nvme0n1p2
    ID-2: /boot/efi size: 511 MiB used: 2

[Kernel-packages] [Bug 2077503] Re: Bus 001 Device 003: ID 0408:4033 Quanta Computer, Inc. ACER HD User Facing

[Philip Cox]

Thanks for the update.

Glad you have a resolution for this.  If you run the command I
mentioned, and include a copy of the patch you made to fix it for
yourself, I can get into into the Ubuntu kernel.  Or you could send it
to to Ubuntu kernel mailing list yourself if you would like.


Here is an outline of the process of submitting the patch to the mailing list.  
https://wiki.ubuntu.com/Kernel/Dev/StablePatchFormat

If you want to submit it yourself, or if you'd like me to submit it,
please reopen this ticket, and send me a comment, and I can assist
either way.  Otherwise, I will close this ticket for now.

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

Title:
  Bus 001 Device 003: ID 0408:4033 Quanta Computer, Inc. ACER HD User
  Facing

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I bought an Acer and I guess my webcam is not on kernel drivers. It's

  Bus 001 Device 003: ID 0408:4033 Quanta Computer, Inc. ACER HD User
  Facing

  Note the 4033 product id.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077503/+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 2077503] Re: Bus 001 Device 003: ID 0408:4033 Quanta Computer, Inc. ACER HD User Facing

[Philip Cox]

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/2077503

Title:
  Bus 001 Device 003: ID 0408:4033 Quanta Computer, Inc. ACER HD User
  Facing

Status in linux package in Ubuntu:
  New

Bug description:
  I bought an Acer and I guess my webcam is not on kernel drivers. It's

  Bus 001 Device 003: ID 0408:4033 Quanta Computer, Inc. ACER HD User
  Facing

  Note the 4033 product id.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077503/+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 2077405] Re: External screen flashing and cannot use after laptop lid closed

[Philip Cox]

Hi Oliver, I have updated the project that this bug is opened against.
Can you try to run the apport-collect again please?  It should gather
some useful information hopefully.

If that does not work please let me know.

** Package changed: linux-signed-hwe-6.8 (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/2077405

Title:
  External screen flashing and cannot use after laptop lid closed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With Kernel 6.8.0-40 (upgraded yesterday) 
  a) the external screen connected to my Lenovo T14 ThinkPad randomly turns 
black for a few seconds and then recovers,
  b) the laptop cannot be used after the lid has been closed. The power LED is 
lit (no stand-by) but screen is blank. No reaction to any key, also cannot open 
a terminal with Ctrl-Alt-Fx. Only a hard reset is possible.

  None of these problems occur with Kernel 6.5.0-45.

  I have previously attempted to use Ubuntu 24.04 LTS but faced exactly
  the same issues, therefore I re-installed Ubuntu 22.04 LTS which was
  working stable until yesterdays kernel upgrade.

  While working with 24.04 LTS for a few weeks I also noted frequent,
  random and complete system freezes which made it unusable with that
  laptop.

  $ lsb_release -rd
  Description:  Ubuntu 22.04.4 LTS
  Release:  22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.8.0-40-generic 6.8.0-40.40~22.04.3
  ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
  Uname: Linux 6.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Tue Aug 20 10:27:32 2024
  InstallationDate: Installed on 2024-08-05 (14 days ago)
  InstallationMedia: Xubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  SourcePackage: linux-signed-hwe-6.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077405/+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 2077231] Re: WiFi Bluetooth and Mouse not working after kernel upgrade

[Philip Cox]

Thank you for updating the ticket.  I will go over the info provided.

** Changed in: linux-signed-hwe-6.5 (Ubuntu)
   Status: Incomplete => New

** Changed in: linux-signed-hwe-6.5 (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  WiFi Bluetooth and Mouse not working after kernel upgrade

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

Bug description:
  Starting somewhere between kernel's 6.5.0-42 and 6.5.0-44, several
  devices and ports stopped working: HDMI port, Bluetooth + WiFi devices
  and the touchpad.

  There are no discernible error entries in dmesg.

  Last working kernel is 6.5.0-41.

  The new 6.8.X kernels present the same issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-44-generic (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-41.41~22.04.2-generic 6.5.13
  Uname: Linux 6.5.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 17 11:22:57 2024
  InstallationDate: Installed on 2024-07-14 (34 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: linux-signed-hwe-6.5
  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.5/+bug/2077231/+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