date:20231027

Hi Chengen,

Thanks for the great work for these SRUs.

I'd like to suggest an update/improvement to the Test Plan section.
Even though crash is so broken that it can't even open a file,
once it starts working at all, it would be important to check
that it is working _correctly_.

So, please, could you add verifications for basic correctness
of the commands being addressed per patch (for GA and HWE)?
e.g., kmem -s|-S, module memory layout, etc.

And I had questions on 2 patches:

Patch 3:
---

 31 +* commit e36ce448a08d removed kmem_cache.freelist_cache in 6.1,
 32 +* so use freelist_size instead.
 33  */
 34 -   if (MEMBER_EXISTS("kmem_cache", "freelist_cache")) {
 35 +   if (MEMBER_EXISTS("kmem_cache", "freelist_size")) {

This is an inconditional change before/after 6.1, which thus could
impact Jammy, as it ships both 5.15 and 6.2 kernels.

However, it seems the (new value) attribute 'freelist_size' already
exists, so it should be fine in Jammy _if_ 5.15 has it too.

Could you please confirm?

Patch 5:
---

Some of this backport's context update is because this patch is not included,
and it would also fit the 6.2 criteria (changes in 6.1). It seems only code
adds though, not sure how it changes any behavior (or more patches needed).

Can you clarify if it's not really needed for 6.5? 
(I haven't followed the maple tree closely, but the commit message suggests 
it's important.)

If it's not needed _right_ now, i.e., if this SRU is priority, and crash
at least _works_ (which is a good improvement), I think it would be fine
to add it later.

commit 872cad2d63b3a07f65323fe80a7abb29ea276b44
Author: Tao Liu 
Date:   Tue Jan 10 14:56:27 2023 +0800

Port the maple tree data structures and functions

There have been two ways to iterate vm_area_struct until Linux 6.0:
 1) by rbtree, aka vma.vm_rb;
 2) by linked list, aka vma.vm_{next,prev}.
However with the maple tree patches[1][2] in Linux 6.1, vm_rb and
vm_{next,prev} are removed from vm_area_struct. The vm_area_dump()
in crash mainly uses the linked list for vma iteration, which will
not work for this case. So the maple tree iteration needs to be
ported to crash.

This patch 5 is also big, adding a lot, anyway, but it goes to gdb-10.2.patch,
which only changed context lines for the backport, indeed.

A pure-code review against upstream seems a big effort (~2000 lines, I managed
up to ~1000, and it seems to match upstream).

I guess this patch will be reasonably verified if the crash commands to show 
module memory layout on kernel 6.4+ (6.5 in our case) run correctly.


** Changed in: crash (Ubuntu)
   Status: In Progress => Incomplete

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  Incomplete
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  In Progress
Status in crash source package in Mantic:
  In Progress

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.3++ (8.0.4 development)
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

The version in Noble is still the same as in Mantic, and Debian does not
have a newer version either to sync/merge [1], so it apparently will not
change soon.

Let's proceed with the Mantic debdiff plus changes for Noble.

Changes:
- Modified d/changelog style to '* Description (LP: #)' entry with '- 
d/p/.patch' sub-entries (more common).
- Numbered the patches (1-7).

Great work on DEP-3 headers, thank you! (Bug-Ubuntu, Origin, and
backport notes; all matching.)

I checked there have been no changes from these patches upstream (i.e.,
fix-up commits to add; except for patch 5 mentioned later, with another
strategy).

I'll attach the updated debdiff for now (keeping your name in signature
line, if you don't mind, as I haven't done serious changes).

...

$ rmadison -a source crash
 crash | 7.0.3-3ubuntu2 | trusty | source
 crash | 7.0.3-3ubuntu4.5   | trusty-updates | source
 crash | 7.1.4-1ubuntu4 | xenial | source
 crash | 7.2.1-1| bionic | source
 crash | 7.2.3+real-1~16.04.1   | xenial-updates | source
 crash | 7.2.8-1ubuntu0.18.04.2 | bionic-updates | source
 crash | 7.2.8-1ubuntu1 | focal  | source
 crash | 7.2.8-1ubuntu1.20.04.1 | focal-updates  | source
 crash | 8.0.0-1ubuntu1 | jammy  | source
 crash | 8.0.0-1ubuntu1 | lunar  | source
 crash | 8.0.2-1ubuntu1 | mantic | source
 crash | 8.0.2-1ubuntu1 | noble  | source

$ date
Fri Oct 27 05:10:39 PM -03 2023

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  Incomplete
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  In Progress
Status in crash source package in Mantic:
  In Progress

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.3++ (8.0.4 development)
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

** Patch added: "lp2038249-crash-noble.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2038249/+attachment/5713875/+files/lp2038249-crash-noble.debdiff

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  Incomplete
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  In Progress
Status in crash source package in Mantic:
  In Progress

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.3++ (8.0.4 development)
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "aarch64-unknown-linux-gnu".
  Type "show

[Kernel-packages] [Bug 2041702] [NEW] Jammy update: v5.15.132 upstream stable release

2023-10-27 Thread Kamal Mostafa

Public bug reported:


SRU Justification

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

   v5.15.132 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Jammy update: v5.15.132 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  New

Bug description:
  
  SRU Justification

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

 v5.15.132 upstream stable release
 from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041702/+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 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel

2023-10-27 Thread Philip

Hi,
has the same problem over the whole last week. Tried different distros.
I‘ve read that the kernel parameter solves it?
May e I try ubuntu again tomorrow with this kernel parameter.
I used arch and had the black screen problem. Maybe this kernel parameter fixes 
the problems on arch as well.

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

Title:
  [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Confirmed

Bug description:
  After upgrading from kernel 5.19.0-35-generic to 6.1.0-1007-oem there
  is occasional screen flicker/ tear. It happens around every minute; it
  seems connected to window/ pointer movement, but I have no clear way
  of reproducing. Disruption is minor,  but annoying.

  I'm running 22.04 LTS on a new Thinkpad T14s with AMD Ryzen 6850u. The
  system is fully functional. No crashes, nothing breaks.

  Background on the use of 6.1.0-1007-oem: 5.19.0-35-generic breaks
  suspend/ resume on my laptop, see
  https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718.

  In a way, running 6.1 is a 'flight forward', since 5.15.0-67-generic
  (previous 22.04.1 LTS kernel) works well, with working suspend/
  resume, and without screen flicker. But that's an 'old' kernel now,
  missing some nice improvements for the newer Ryzen APUs.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-oem-22.04c 6.1.0.1007.7
  ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6
  Uname: Linux 6.1.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 10 13:09:20 2023
  InstallationDate: Installed on 2023-02-06 (31 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: linux-meta-oem-6.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009952/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

2023-10-27 Thread Bug Watch Updater

Launchpad has imported 87 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=218003.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2023-10-12T07:44:05+00:00 suroto wrote:

Hello,

I have installed fedora workstation 38, with kernel default (versi 6.2 ??).
But keyboard not working.
Then I try ubuntu 22.04.3 LTS . it's same problem.
Then try upgrade kernel of Fedora Workstation 38 to kernel 6.6..
keyboard still not working.

It's possible fix it ?

Thank You
SUroto

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034477/comments/26

On 2023-10-12T08:25:24+00:00 suroto wrote:

additional details hardware:
S/N : Pf4DM1wG
Model Name:  Lenovo V14 G4 AMN.  ( before any typo mistake, G14)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034477/comments/27

On 2023-10-12T09:20:16+00:00 bagasdotme wrote:

(In reply to Suroto from comment #0)
> Hello,
> 
> I have installed fedora workstation 38, with kernel default (versi 6.2 ??).
> But keyboard not working.
> Then I try ubuntu 22.04.3 LTS . it's same problem.
> Then try upgrade kernel of Fedora Workstation 38 to kernel 6.6..
> keyboard still not working.
> 

Does hotkeys (usually laptop-specific) have problem?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034477/comments/28

On 2023-10-12T09:44:55+00:00 suroto wrote:

hotkey working only on the contras screen key

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034477/comments/29

On 2023-10-12T12:20:24+00:00 aros wrote:

Mario, could you take a look please?

This was reported months ago:

https://forum.manjaro.org/t/lenovo-amd-no-keyboard/141597/5

https://unix.stackexchange.com/questions/751668/lenovo-v15-g4-amn-mouse-
and-keyboard-is-not-working-under-linux

https://bugs.launchpad.net/ubuntu/+source/linux-signed-
hwe-6.2/+bug/2034477

https://askubuntu.com/questions/1480477/laptop-keyboard-and-mosuepad-
dosnt-work-on-lenovo-v15-g4-amn-type-82yu

Multiple Lenovo laptops exhibit this issue and the company doesn't seem
to care one bit. They could have fixed the issue themselves. Please just
don't buy or recommend their products to anyone who cares about Linux.
I've no idea who to ping or what to do.

I've heard that some modern laptops have some sort of I2C (?)
multiplexors which need to be set up properly in order to enable
keyboard input but how it all works, again I've no clue.

I'm CC'ing Mario Limonciello because I remember he knows something about
that. Maybe he could chime in and give the instructions how to debug the
issue and fix it all the affected people.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034477/comments/30

On 2023-10-12T12:28:21+00:00 aros wrote:

CC'ing Tamim Khan for good measure.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034477/comments/31

On 2023-10-13T01:56:45+00:00 suroto wrote:

Thank you for your explanation.

Since 15 years ago, I have installed Linux on various brands and types of 
computers,
Just recently, I encountered a hardware problem that Linux doesn't recognize.

I will try to send an issue ticket to Levono

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034477/comments/32

On 2023-10-13T15:29:25+00:00 p0lloc wrote:

Same issue with IdeaPad Slim 3 14AMN8, quite a lot of good info in
https://bugzilla.kernel.org/show_bug.cgi?id=217873 but no solution.

I have tried an immense amount of kernel parameter combinations and
patching the latest mainline kernel with IRQ quirks of different
combinations, to no avail.

The only combination of i8042 parameters that do ANYTHING is
"i8042.direct i8042.dumbkbd i8042.noloop i8042.nopnp" which finally gets
a working keyboard (but with an insane delay of 15-60 seconds per
keypress). Dumbkbd doesn't seem strictly necessary but you receive 10-20
commas before any actual keyboard input gets through.

Really hoping for a solution or any suggestions on what to try next.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034477/comments/39

On 2023-10-13T15:32:10+00:00 mario.limonciello wrote:

Can both of you guys please test with the latest 6.6-rc, and if it

[Kernel-packages] [Bug 2039926] Re: Error UBSAN: array-index-out-of-bounds amdgpu

2023-10-27 Thread Alex Deucher

This updates the rest of them:
https://patchwork.freedesktop.org/patch/564786/

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

Title:
  Error UBSAN: array-index-out-of-bounds amdgpu

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

Bug description:
  Error in boot:

  [8.597520] UBSAN: array-index-out-of-bounds in 
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4
  [8.597527] index 7 is out of range for type 
'ATOM_Polaris_SCLK_Dependency_Record [1]'

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-generic 6.5.0.9.11
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 09:28:16 2023
  InstallationDate: Installed on 2022-10-12 (373 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=9edc5478-c6c2-4cf3-9de8-01ccb697fb9e ro quiet splash audit=0 
mitigations=off amdgpu.ppfeaturemask=0x vt.global_cursor_default=0 
loglevel=2 rd.systemd.show_status=false rd.udev.log-prority=3 
sysrq_always_enabled=1 audit=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (6 days ago)
  dmi.bios.date: 07/11/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: D3EMW08.110
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: D3F3-EM
  dmi.board.vendor: MEDION
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrD3EMW08.110:bd07/11/2014:br4.6:svnMEDION:pnD3F3-EM:pvr1.0:rvnMEDION:rnD3F3-EM:rvr1.0:cvnMEDION:ct3:cvr:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: D3F3-EM
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDION

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039926/+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 2039926] Re: Error UBSAN: array-index-out-of-bounds amdgpu

2023-10-27 Thread Alex Deucher

FWIW, none of these are actually out of bound accesses.  These just
happen to use the old nomenclature for variable sized arrays.

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

Title:
  Error UBSAN: array-index-out-of-bounds amdgpu

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

Bug description:
  Error in boot:

  [8.597520] UBSAN: array-index-out-of-bounds in 
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4
  [8.597527] index 7 is out of range for type 
'ATOM_Polaris_SCLK_Dependency_Record [1]'

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-generic 6.5.0.9.11
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 09:28:16 2023
  InstallationDate: Installed on 2022-10-12 (373 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=9edc5478-c6c2-4cf3-9de8-01ccb697fb9e ro quiet splash audit=0 
mitigations=off amdgpu.ppfeaturemask=0x vt.global_cursor_default=0 
loglevel=2 rd.systemd.show_status=false rd.udev.log-prority=3 
sysrq_always_enabled=1 audit=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (6 days ago)
  dmi.bios.date: 07/11/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: D3EMW08.110
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: D3F3-EM
  dmi.board.vendor: MEDION
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrD3EMW08.110:bd07/11/2014:br4.6:svnMEDION:pnD3F3-EM:pvr1.0:rvnMEDION:rnD3F3-EM:rvr1.0:cvnMEDION:ct3:cvr:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: D3F3-EM
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDION

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039926/+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 1919154] Re: Enable CONFIG_NO_HZ_FULL on supported architectures

2023-10-27 Thread Jay Vosburgh

Gerald,

Using gettimeofday for testing the effects of NO_HZ_FULL on context
switch duration may not be measuring anything that changes with regards
to NO_HZ_FULL.  gettimeofday is implemented via VDSO, and is not an
actual system call that requires a context switch.

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

Title:
  Enable CONFIG_NO_HZ_FULL on supported architectures

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Won't Fix
Status in linux source package in Hirsute:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Lunar:
  In Progress
Status in linux source package in Mantic:
  In Progress

Bug description:
  [Impact]

  The CONFIG_NO_HZ_FULL=y Kconfig option causes the kernel to avoid
  sending scheduling-clock interrupts to CPUs with a single runnable task,
  and such CPUs are said to be "adaptive-ticks CPUs".  This is important
  for applications with aggressive real-time response constraints because
  it allows them to improve their worst-case response times by the maximum
  duration of a scheduling-clock interrupt.  It is also important for
  computationally intensive short-iteration workloads:  If any CPU is
  delayed during a given iteration, all the other CPUs will be forced to
  wait idle while the delayed CPU finishes.  Thus, the delay is multiplied
  by one less than the number of CPUs.  In these situations, there is
  again strong motivation to avoid sending scheduling-clock interrupts.

  [Test Plan]

  In order to verify the change will not cause performance issues in
  context switch we should compare the results for:

  ./stress-ng --seq 0 --metrics-brief -t 15

  Running on a dedicated machine and with the following services
  disabled: smartd.service, iscsid.service, apport.service,
  cron.service, anacron.timer, apt-daily.timer, apt-daily-upgrade.timer,
  fstrim.timer, logrotate.timer, motd-news.timer, man-db.timer.

  The results didn't show any performance regression:

  https://kernel.ubuntu.com/~mhcerri/lp1919154/

  [Where problems could occur]

  Performance degradation might happen for workloads with intensive
  context switching.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919154/+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 2039926] Re: Error UBSAN: array-index-out-of-bounds amdgpu

2023-10-27 Thread Olivier Duclos

The mentioned patches fix the issue for Polaris and Tonga, but other AMD
GPUs are also affected. I have a Radeon Vega 64 and here is a summary of
the UBSAN errors I see:

index 2 is out of range for type 'ATOM_Vega10_MM_Dependency_Record [1]'
index 1 is out of range for type 'ATOM_Vega10_CLK_Dependency_Record [1]'
index 5 is out of range for type 'ATOM_Vega10_CLK_Dependency_Record [1]'
index 1 is out of range for type 'ATOM_Vega10_MCLK_Dependency_Record [1]'
index 1 is out of range for type 'ATOM_Vega10_PCIE_Record [1]'
index 1 is out of range for type 'ATOM_Vega10_Voltage_Lookup_Record [1]'

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

Title:
  Error UBSAN: array-index-out-of-bounds amdgpu

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

Bug description:
  Error in boot:

  [8.597520] UBSAN: array-index-out-of-bounds in 
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4
  [8.597527] index 7 is out of range for type 
'ATOM_Polaris_SCLK_Dependency_Record [1]'

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-generic 6.5.0.9.11
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 09:28:16 2023
  InstallationDate: Installed on 2022-10-12 (373 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=9edc5478-c6c2-4cf3-9de8-01ccb697fb9e ro quiet splash audit=0 
mitigations=off amdgpu.ppfeaturemask=0x vt.global_cursor_default=0 
loglevel=2 rd.systemd.show_status=false rd.udev.log-prority=3 
sysrq_always_enabled=1 audit=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (6 days ago)
  dmi.bios.date: 07/11/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: D3EMW08.110
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: D3F3-EM
  dmi.board.vendor: MEDION
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrD3EMW08.110:bd07/11/2014:br4.6:svnMEDION:pnD3F3-EM:pvr1.0:rvnMEDION:rnD3F3-EM:rvr1.0:cvnMEDION:ct3:cvr:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: D3F3-EM
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDION

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

Re: [Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

2023-10-27 Thread Jean-Marie Tschanz

DONE...It works !!

I had to install flex + libelf-dev

I had to disable Secure Boot in order to avoid a "bad shim signature"
error

So no clean way...

Thnak you for your precious time-saving answer 

On Fri, 27 Oct 2023 at 17:12, Endre Olah <2034...@bugs.launchpad.net>
wrote:

> Hi Jean-Marie,
>
> "enter" is used in some comments and means either that you have to
> switch your current folder/directory when you are in terminal. So
> commands should be executed in the right folder, otherwise you might do
> something else or maybe nothing.
>
> So "enter kernel" means to  to cd to the decompressed folder of the
> kernel source files.
>
> Quinten's description worked for me and it is not that difficult to
> follow.
>
> Rgds
>
>  Endre
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2034477
>
> Title:
>   Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
>
> Status in ideapad-laptop:
>   New
> Status in libinput package in Ubuntu:
>   Confirmed
> Status in linux-signed-hwe-6.2 package in Ubuntu:
>   Confirmed
> Status in linux-signed-oem-6.5 package in Ubuntu:
>   Confirmed
> Status in Fedora:
>   New
>
> Bug description:
>   Hello.
>
>   Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
>   installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
>   laptop and it was noticed that keyboard, touchpad and microphone are
>   not working. The keyboard and touchpad work fine in BIOS setup and
>   till GRUB (command line). It was found that when external devices such
>   as keyboard, mouse and microphone are connected through USB and 3.5
>   jack, respectively, these work just fine. To confirm these are not
>   hardware problems, Microsoft Windows 11  (Home) was installed in
>   another disk partition and observed all these working alright. Hence a
>   bug is being reported to draw attention of the concerned team and I
>   request them to refer this issue and do the needful at the earliest.
>
>   Regards,
>   Pradip Kumar Das
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
>   ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
>   Uname: Linux 6.2.0-32-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu82.5
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Sep  6 08:04:42 2023
>   InstallationDate: Installed on 2023-08-14 (22 days ago)
>   InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64
> (20230223)
>   ProcEnviron:
>LANGUAGE=en_IN:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_IN
>SHELL=/bin/bash
>   SourcePackage: linux-signed-hwe-6.2
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions
>
>

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

Title:
  Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Status in ideapad-laptop:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  Hello.

  Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
  installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
  laptop and it was noticed that keyboard, touchpad and microphone are
  not working. The keyboard and touchpad work fine in BIOS setup and
  till GRUB (command line). It was found that when external devices such
  as keyboard, mouse and microphone are connected through USB and 3.5
  jack, respectively, these work just fine. To confirm these are not
  hardware problems, Microsoft Windows 11  (Home) was installed in
  another disk partition and observed all these working alright. Hence a
  bug is being reported to draw attention of the concerned team and I
  request them to refer this issue and do the needful at the earliest.

  Regards,
  Pradip Kumar Das

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

Updating the bug description with the crash versions/tags which
_contains_ the commit IDs.

Verified with the provided commit list:

$ cat

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

Submitted bug [1] (wishlist) to Debian maintainer to update crash from
8.0.2 to 8.0.3 (released April/2023) in sid/unstable.

With this we could merge a smaller set of changes later on.

[1] https://bugs.debian.org/1054805

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  In Progress
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  In Progress
Status in crash source package in Mantic:
  In Progress

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.3++ (8.0.4 development)
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was

[Kernel-packages] [Bug 2039280] Re: Support IP address protocol

2023-10-27 Thread Andreas Hasenack

I agree that a merge from debian would be better, since we are quite
behind:

iproute2   | 6.5.0-4  | testing

But we have been at 6.1.0 since at least lunar, so I don't know how long
that would take. I think we can take these patches for noble.

I would ask that you also add this one, though, to update the manpage
with the new option:

commit 1fbb61058d34e3eb9a34f5e9308d90c4a961
Author: Petr Machata 
Date:   Mon Mar 27 18:12:06 2023 +0200

man: man8: Add man page coverage for "ip address add ... proto"

Signed-off-by: Petr Machata 
Signed-off-by: David Ahern 


Also,  you could perhaps add your test script as a quick DEP8 test, what do you 
think? Something like this?

--- a/debian/tests/control
+++ b/debian/tests/control
@@ -3,3 +3,7 @@
 Tests: testsuite.sh
 Restrictions: allow-stderr, isolation-machine, needs-root, rw-build-tree
 Depends: build-essential, locales-all, dpkg-dev, sudo:native, kmod, @builddeps@
+
+Tests: test-protocol-attribute
+Restrictions: isolation-machine, needs-root
+Depends: iproute2
diff --git a/debian/tests/test-protocol-attribute.sh 
b/debian/tests/test-protocol-attribute.sh
new file mode 100755
index ..254b2906
--- /dev/null
+++ b/debian/tests/test-protocol-attribute.sh
@@ -0,0 +1,14 @@
+#!/bin/sh
+
+set -e
+
+addr=192.0.2.1/28
+ifr=test-dummy123
+
+ip link add name "$ifr" type dummy
+ip link set "$ifr" up
+
+ip address add dev "$ifr" "$addr" proto 0x99
+
+ip link del "$ifr"


Perhaps improve it with using a random address, and showing the "ip a" output 
and checking that "proto 0x99" was truly added.

Finally, it would also be good if the patches have a few more DEP3
headers. In particular, Origin, with a link to the upstream commit, and
also a pointer to this bug here (Bug-Ubuntu: ...). The hash in the
"From" bit in both patches didn't match the upstreams I could find
(git://git.kernel.org/pub/scm/network/iproute2/iproute2.git or
https://github.com/shemminger/iproute2.git), but I did find the commits
using a log search. It would help if the Origin tag were there, then,
with a direct link.


Regarding an SRU, I would have some concerns:

- what is the real user benefit for stable release users? Do we have
bugs filed against iproute2 asking for this feature? How much demand is
there for this? In which kind of deployment would this be most useful?

- I see that the "ip" output changes when this flag is present, with the
new "proto " string. What's the regression potential here for
parsing this output in scripts? I believe the new "proto " text is
only present if there was a protocol assigned, and if not, the default
value (0 I believe?) is not shown. But are there other regression
potentials here? Perhaps in the json output, or when some extra flag is
added to "ip" commands?

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

Title:
  Support IP address protocol

Status in iproute2 package in Ubuntu:
  Confirmed
Status in iproute2 source package in Mantic:
  Confirmed

Bug description:
  [Impact]

  IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
  provenance of the IP address. The attribute is modeled after ip route
  protocols, and essentially allows the administrator or userspace stack to
  tag addresses in some way that makes sense to the actor in question.
  Support for this feature was merged with commit 47f0bd503210 ("net: Add new
  protocol attribute to IP addresses"), for kernel 5.18.

  In this patch, add support for setting the protocol attribute at IP address
  addition, replacement, and listing requests.

  [Fix]

  Apply the attached patch

  [How to test]

  $ cat << EOF > test.sh
  #!/bin/sh

  addr=192.0.2.1/28
  addr2=${addr%/*}2/${addr#*/}
  ifr=test-dummy123

  sudo ip link add name "$ifr" type dummy
  sudo ip link set "$ifr" up

  sudo ip address add dev "$ifr" "$addr2" proto 0x99

  sudo ip link del "$ifr"
  EOF

  $chmod +x test.sh
  $test.sh
  $ echo $?
  0

  if you get an error instead, like:
  Error: either "local" is duplicate, or "proto" is a garbage.

  your iproute2 is not patched.
  Alternativerly, you could download Linux v6.5 source code and run:

  $ cd linux
  $ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto

  [Regression potential]

  Two clean upstream cherry-picks, regression potential should be low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+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 2038288] modified.conffile..etc.thermald.thermal-cpu-cdev-order.xml.txt

apport information

** Attachment added: 
"modified.conffile..etc.thermald.thermal-cpu-cdev-order.xml.txt"
   
https://bugs.launchpad.net/bugs/2038288/+attachment/5713836/+files/modified.conffile..etc.thermald.thermal-cpu-cdev-order.xml.txt

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start

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

apport information

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

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result 'core-dump'.

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

apport information

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

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result 'core-dump'.

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

apport information

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

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result 'core-dump'.

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

apport information

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

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]:

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

apport information

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

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]:

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

apport information

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

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result

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

apport information

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

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]:

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

apport information

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

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result 'core-dump'.

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

apport information

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

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]:

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

apport information

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

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]:

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

apport information

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

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result 'core-dump'.

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

apport information

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

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result 'core-dump'.

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

apport information

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

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]:

[Kernel-packages] [Bug 2038288] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/2038288/+attachment/5713822/+files/Dependencies.txt

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result 'core-dump'.

[Kernel-packages] [Bug 2038288] AlsaInfo.txt

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/2038288/+attachment/5713820/+files/AlsaInfo.txt

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result 'core-dump'.

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

apport information

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

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1117]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1180]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Start request repeated too quickly.
  systemd[1]: thermald.service: Failed with result 'core-dump'.

[Kernel-packages] [Bug 2038288] apport information

ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  henriqueqc   1730 F wireplumber
 /dev/snd/seq:henriqueqc   1723 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-10-27 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: thermald 2.5.4-2
PackageArchitecture: amd64
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=444c6838-7aaf-4dc7-942c-6ab87ca16805 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-10-generic N/A
 linux-backports-modules-6.5.0-10-generic  N/A
 linux-firmware20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 07/23/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.0
dmi.board.name: 09WC1G
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd07/23/2021:br1.15:svnDellInc.:pnInspiron7460:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr:sku0781:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7460
dmi.product.sku: 0781
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.init.thermald.conf: [deleted]
mtime.conffile..etc.thermald.thermal-cpu-cdev-order.xml: 2023-08-25T07:29:11

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

Title:
  Failed to start thermald.service

Status in linux package in Ubuntu:
  Confirmed
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  Get lot of thermald errors logged with that Mate session on Mantic

  dbus-broker-launch[775]: Invalid group-name in 
/usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power"
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[892]: *** stack smashing detected ***: terminated
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: Failed to start thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[982]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[982]: sensor id 10 : No temp sysfs for reading raw temp
  systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'signal'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1)
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp
  thermald[1049]: *** stack smashing detected ***: terminated
  systemd[1]: Started thermald.service - Thermal Daemon Service.
  systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: thermald.service: Failed with result 'core-dump'.
  systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3.
  systemd[1]: Stopped thermald.service - Thermal Daemon Service.
  systemd[1]: Starting thermald.service - Thermal Daemon Service...

[Kernel-packages] [Bug 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel

Sorry for delay looking at this.  I might have not been clear.  That
script needs to be run after the error has occurred.  I don't see the
error in this kernel log.

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

Title:
  [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Confirmed

Bug description:
  After upgrading from kernel 5.19.0-35-generic to 6.1.0-1007-oem there
  is occasional screen flicker/ tear. It happens around every minute; it
  seems connected to window/ pointer movement, but I have no clear way
  of reproducing. Disruption is minor,  but annoying.

  I'm running 22.04 LTS on a new Thinkpad T14s with AMD Ryzen 6850u. The
  system is fully functional. No crashes, nothing breaks.

  Background on the use of 6.1.0-1007-oem: 5.19.0-35-generic breaks
  suspend/ resume on my laptop, see
  https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718.

  In a way, running 6.1 is a 'flight forward', since 5.15.0-67-generic
  (previous 22.04.1 LTS kernel) works well, with working suspend/
  resume, and without screen flicker. But that's an 'old' kernel now,
  missing some nice improvements for the newer Ryzen APUs.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-oem-22.04c 6.1.0.1007.7
  ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6
  Uname: Linux 6.1.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 10 13:09:20 2023
  InstallationDate: Installed on 2023-02-06 (31 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: linux-meta-oem-6.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009952/+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 2040337] Re: Incorrect argument from SEV live-migration fix

2023-10-27 Thread John Cabaj

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

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

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

Title:
  Incorrect argument from SEV live-migration fix

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Focal:
  Fix Committed
Status in linux-gcp source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  * Google requested fix to notify_range_enc_status_changed() passing
  incorrect argument.

  [Fix]

  * Upstream ac3f9c9f1b37 introduced change to 
notify_range_enc_status_changed() to accept page size instead of number of 
pages, but function was not updated. Updating to send correct argument. 
Upstream implementation changed with TDX
  support, and is unaffected, so no plans to upstream.

  [Test Case]

  * Compile tested
  * Boot tested
  * Tested by Google

  [Where things could go wrong]

  * Low chance of regression. Isolated logic fix.

  [Other Info]

  * SF #00367134

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040337/+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 2041613] Re: correct cephfs pull request for uidmap support

submitted https://lists.ubuntu.com/archives/kernel-
team/2023-October/146593.html

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

Title:
  correct cephfs pull request for uidmap support

Status in linux package in Ubuntu:
  New
Status in linux source package in Mantic:
  New
Status in linux source package in Noble:
  New

Bug description:
  [ Impact ]

   * During mantic dev cycle, we pulled all of cephfs testing patches, rather 
than uidmapshift patches alone
   * We also pulled in debug patches that generate a lot of dmesg and delays in 
the cephfs module

  [ Test Plan ]

   * run ceph fs and experience less dmesg at info level

  [ Where problems could occur ]

   * Hopefully the reverts were done correctly, and none of the messages
  reference non-existing things, in all the code paths.

  [ Other Info ]

   * Story time how we got here:

  The following pull requests

  BugLink: https://bugs.launchpad.net/bugs/2038522
  BugLink: https://bugs.launchpad.net/bugs/2032959

  generated the following commit list 1:

  eddf9ed788 UBUNTU: [Config] disable shiftfs
  72e8806959 UBUNTU: SAUCE: ceph: enable unsafe idmapped mounts by default
  80b85e5d76 UBUNTU: SAUCE: ceph: allow idmapped mounts
  9d341bb8aa UBUNTU: SAUCE: ceph/file: allow idmapped atomic_open inode op
  ddd1a8ee19 UBUNTU: SAUCE: ceph/acl: allow idmapped set_acl inode op
  1b12f12987 UBUNTU: SAUCE: ceph: allow idmapped setattr inode op
  b1f695f0d1 UBUNTU: SAUCE: ceph: pass idmap to __ceph_setattr
  8a9a3b9e88 UBUNTU: SAUCE: ceph: allow idmapped permission inode op
  e5471722b3 UBUNTU: SAUCE: ceph: allow idmapped getattr inode op
  f6b1d353fa UBUNTU: SAUCE: ceph: pass an idmapping to mknod/symlink/mkdir
  5ecfa6f659 UBUNTU: SAUCE: ceph: add enable_unsafe_idmap module parameter
  19724a984a UBUNTU: SAUCE: ceph: handle idmapped mounts in 
create_request_message()
  6ec4e53238 UBUNTU: SAUCE: ceph: stash idmapping in mdsc request
  8006617c5e UBUNTU: SAUCE: fs: export mnt_idmap_get/mnt_idmap_put
  55f4f0afc5 UBUNTU: SAUCE: ceph: make num_fwd and num_retry to __u32
  54e03068d6 UBUNTU: SAUCE: ceph: make the members in struct 
ceph_mds_request_args_ext an union
  f7ec09aaac UBUNTU: SAUCE: ceph: print the client global_id in all the debug 
logs
  b2831559c5 UBUNTU: SAUCE: ceph: add ceph_inode_to_client() helper support
  a0852434ee UBUNTU: SAUCE: ceph: move mdsmap.h to fs/ceph/
  cfda2c4b70 UBUNTU: SAUCE: ceph: rename _to_client() to _to_fs_client()
  42924fda3a UBUNTU: SAUCE: ceph: pass the mdsc to several helpers
  9f6e6f9ce9 UBUNTU: SAUCE: ceph: add the *_client debug macros support
  8f61639667 UBUNTU: SAUCE: ceph: BUG if MDS changed truncate_seq with client 
caps still outstanding
  a53dba9297 UBUNTU: SAUCE: ceph: make sure all the files successfully put 
before unmounting
  17fcf5d75d UBUNTU: SAUCE: mm: BUG if filemap_alloc_folio gives us a folio 
with a non-NULL ->private
  834ebb591f UBUNTU: SAUCE: ceph: dump info about cap flushes when we're 
waiting too long for them
  498d08b9bd UBUNTU: SAUCE: rbd: bump RBD_MAX_PARENT_CHAIN_LEN to 128
  3ae75e2438 UBUNTU: SAUCE: libceph: do not include crypto/algapi.h
  d984763988 UBUNTU: SAUCE: ceph: switch ceph_lookup/atomic_open() to use new 
fscrypt helper
  8e298c72fb UBUNTU: SAUCE: ceph: fix updating i_truncate_pagecache_size for 
fscrypt
  288f935219 UBUNTU: SAUCE: ceph: wait for OSD requests' callbacks to finish 
when unmounting
  435fc54954 UBUNTU: SAUCE: ceph: drop messages from MDS when unmounting
  862a1e3c2a UBUNTU: SAUCE: ceph: update documentation regarding snapshot 
naming limitations
  904f39f283 UBUNTU: SAUCE: ceph: prevent snapshot creation in encrypted locked 
directories
  a47bdc0f8a UBUNTU: SAUCE: ceph: add support for encrypted snapshot names
  e4202a1c3e UBUNTU: SAUCE: ceph: invalidate pages when doing direct/sync writes
  9f781cfb0d UBUNTU: SAUCE: ceph: plumb in decryption during reads
  e76383977f UBUNTU: SAUCE: ceph: add encryption support to writepage and 
writepages
  0b571b2ac0 UBUNTU: SAUCE: ceph: add read/modify/write to ceph_sync_write
  a81bd5f1c8 UBUNTU: SAUCE: ceph: align data in pages in ceph_sync_write
  edbe3d2a62 UBUNTU: SAUCE: ceph: don't use special DIO path for encrypted 
inodes
  efed7d1764 UBUNTU: SAUCE: ceph: add truncate size handling support for fscrypt
  5d65284a6a UBUNTU: SAUCE: ceph: add object version support for sync read
  d76cff7c37 UBUNTU: SAUCE: libceph: allow ceph_osdc_new_request to accept a 
multi-op read
  53d1c3958e UBUNTU: SAUCE: libceph: add CEPH_OSD_OP_ASSERT_VER support
  7ecbaa5849 UBUNTU: SAUCE: ceph: add infrastructure for file encryption and 
decryption
  4142d15305 UBUNTU: SAUCE: ceph: handle fscrypt fields in cap messages from MDS
  53507ac6a8 UBUNTU: SAUCE: ceph: size handling in MClientRequest, cap updates 
and inode traces
  b9936d13f4 UBUNTU: SAUCE: ceph: mark directory as non-complete after loading 
key
  906d57a83b

[Kernel-packages] [Bug 2041613] Re: correct cephfs pull request for uidmap support

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

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

** Description changed:

  [ Impact ]
  
   * During mantic dev cycle, we pulled all of cephfs testing patches, rather 
than uidmapshift patches alone
   * We also pulled in debug patches that generate a lot of dmesg and delays in 
the cephfs module
  
  [ Test Plan ]
  
   * run ceph fs and experience less dmesg at info level
  
  [ Where problems could occur ]
  
   * Hopefully the reverts were done correctly, and none of the messages
  reference non-existing things, in all the code paths.
  
  [ Other Info ]
  
   * Story time how we got here:
  
  The following pull requests
  
  BugLink: https://bugs.launchpad.net/bugs/2038522
  BugLink: https://bugs.launchpad.net/bugs/2032959
  
  generated the following commit list 1:
  
  eddf9ed788 UBUNTU: [Config] disable shiftfs
  72e8806959 UBUNTU: SAUCE: ceph: enable unsafe idmapped mounts by default
  80b85e5d76 UBUNTU: SAUCE: ceph: allow idmapped mounts
  9d341bb8aa UBUNTU: SAUCE: ceph/file: allow idmapped atomic_open inode op
  ddd1a8ee19 UBUNTU: SAUCE: ceph/acl: allow idmapped set_acl inode op
  1b12f12987 UBUNTU: SAUCE: ceph: allow idmapped setattr inode op
  b1f695f0d1 UBUNTU: SAUCE: ceph: pass idmap to __ceph_setattr
  8a9a3b9e88 UBUNTU: SAUCE: ceph: allow idmapped permission inode op
  e5471722b3 UBUNTU: SAUCE: ceph: allow idmapped getattr inode op
  f6b1d353fa UBUNTU: SAUCE: ceph: pass an idmapping to mknod/symlink/mkdir
  5ecfa6f659 UBUNTU: SAUCE: ceph: add enable_unsafe_idmap module parameter
  19724a984a UBUNTU: SAUCE: ceph: handle idmapped mounts in 
create_request_message()
  6ec4e53238 UBUNTU: SAUCE: ceph: stash idmapping in mdsc request
  8006617c5e UBUNTU: SAUCE: fs: export mnt_idmap_get/mnt_idmap_put
  55f4f0afc5 UBUNTU: SAUCE: ceph: make num_fwd and num_retry to __u32
  54e03068d6 UBUNTU: SAUCE: ceph: make the members in struct 
ceph_mds_request_args_ext an union
  f7ec09aaac UBUNTU: SAUCE: ceph: print the client global_id in all the debug 
logs
  b2831559c5 UBUNTU: SAUCE: ceph: add ceph_inode_to_client() helper support
  a0852434ee UBUNTU: SAUCE: ceph: move mdsmap.h to fs/ceph/
  cfda2c4b70 UBUNTU: SAUCE: ceph: rename _to_client() to _to_fs_client()
  42924fda3a UBUNTU: SAUCE: ceph: pass the mdsc to several helpers
  9f6e6f9ce9 UBUNTU: SAUCE: ceph: add the *_client debug macros support
  8f61639667 UBUNTU: SAUCE: ceph: BUG if MDS changed truncate_seq with client 
caps still outstanding
  a53dba9297 UBUNTU: SAUCE: ceph: make sure all the files successfully put 
before unmounting
  17fcf5d75d UBUNTU: SAUCE: mm: BUG if filemap_alloc_folio gives us a folio 
with a non-NULL ->private
  834ebb591f UBUNTU: SAUCE: ceph: dump info about cap flushes when we're 
waiting too long for them
  498d08b9bd UBUNTU: SAUCE: rbd: bump RBD_MAX_PARENT_CHAIN_LEN to 128
  3ae75e2438 UBUNTU: SAUCE: libceph: do not include crypto/algapi.h
  d984763988 UBUNTU: SAUCE: ceph: switch ceph_lookup/atomic_open() to use new 
fscrypt helper
  8e298c72fb UBUNTU: SAUCE: ceph: fix updating i_truncate_pagecache_size for 
fscrypt
  288f935219 UBUNTU: SAUCE: ceph: wait for OSD requests' callbacks to finish 
when unmounting
  435fc54954 UBUNTU: SAUCE: ceph: drop messages from MDS when unmounting
  862a1e3c2a UBUNTU: SAUCE: ceph: update documentation regarding snapshot 
naming limitations
  904f39f283 UBUNTU: SAUCE: ceph: prevent snapshot creation in encrypted locked 
directories
  a47bdc0f8a UBUNTU: SAUCE: ceph: add support for encrypted snapshot names
  e4202a1c3e UBUNTU: SAUCE: ceph: invalidate pages when doing direct/sync writes
  9f781cfb0d UBUNTU: SAUCE: ceph: plumb in decryption during reads
  e76383977f UBUNTU: SAUCE: ceph: add encryption support to writepage and 
writepages
  0b571b2ac0 UBUNTU: SAUCE: ceph: add read/modify/write to ceph_sync_write
  a81bd5f1c8 UBUNTU: SAUCE: ceph: align data in pages in ceph_sync_write
  edbe3d2a62 UBUNTU: SAUCE: ceph: don't use special DIO path for encrypted 
inodes
  efed7d1764 UBUNTU: SAUCE: ceph: add truncate size handling support for fscrypt
  5d65284a6a UBUNTU: SAUCE: ceph: add object version support for sync read
  d76cff7c37 UBUNTU: SAUCE: libceph: allow ceph_osdc_new_request to accept a 
multi-op read
  53d1c3958e UBUNTU: SAUCE: libceph: add CEPH_OSD_OP_ASSERT_VER support
  7ecbaa5849 UBUNTU: SAUCE: ceph: add infrastructure for file encryption and 
decryption
  4142d15305 UBUNTU: SAUCE: ceph: handle fscrypt fields in cap messages from MDS
  53507ac6a8 UBUNTU: SAUCE: ceph: size handling in MClientRequest, cap updates 
and inode traces
  b9936d13f4 UBUNTU: SAUCE: ceph: mark directory as non-complete after loading 
key
  906d57a83b UBUNTU: SAUCE: ceph: allow encrypting a directory while not having 
Ax caps
  4a58d08c63 UBUNTU: SAUCE: ceph: add some fscrypt guardrails
  83229b1f64 UBUNTU: SAUCE: ceph: create symlinks with encrypted and 
base64-encoded targets
  6f10a0358e

[Kernel-packages] [Bug 2032136] Re: System reboot to BIOS boot menu

2023-10-27 Thread Mike Ferreira

This is still affected with Linux kernel 6.2.0-33-genric on this laptop.
Nothing has changed. It still will not do a "reboot" without ending up
at a BIOS Boot menu.

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

Title:
  System reboot to BIOS boot menu

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

Bug description:
  Ever since update of Linux kernel to 6.2.0-26, this laptop (Lenovo
  Thinkpad T520) on reboot, goes to a boot loop directly to the BIOS
  Boot menu. On  from there, still stuck in that
  loop.

  It displays an error message just before the BIOS Boot menu, but
  flashes by too fast to actually make out what is there.

  If it shutdown, and cold boot, it boots normally to the Grub2 Boot
  menu.

  There is a problem somewhere.

  This machine is ZFS-On-Root. Another User says he is having this same
  problem, but on an LVM2 install. The common denominator seems to be
  the update to Linux kernel 6.2.0-26.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  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 zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sun Aug 20 14:14:56 2023
  InstallationDate: Installed on 2021-09-23 (696 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-08-17 (368 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2032136/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

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

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

Title:
  Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Status in ideapad-laptop:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  Hello.

  Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
  installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
  laptop and it was noticed that keyboard, touchpad and microphone are
  not working. The keyboard and touchpad work fine in BIOS setup and
  till GRUB (command line). It was found that when external devices such
  as keyboard, mouse and microphone are connected through USB and 3.5
  jack, respectively, these work just fine. To confirm these are not
  hardware problems, Microsoft Windows 11  (Home) was installed in
  another disk partition and observed all these working alright. Hence a
  bug is being reported to draw attention of the concerned team and I
  request them to refer this issue and do the needful at the earliest.

  Regards,
  Pradip Kumar Das

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 08:04:42 2023
  InstallationDate: Installed on 2023-08-14 (22 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Please also take this fix at the same time for this same laptop.  It
will fix s2idle for it.

https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-
drivers-x86.git/commit/?h=fixes=3bde7ec13c971445faade32172cb0b4370b841d9

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

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

** No longer affects: linux-signed-oem-6.5 (Ubuntu)

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

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

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

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

** Also affects: libinput (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.1 (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: linux-hwe-6.2 (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.5 (Ubuntu Mantic)
   Importance: Undecided
   Status: New

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

** Also affects: libinput (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.1 (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: linux-hwe-6.2 (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.5 (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

** Also affects: libinput (Ubuntu Noble)
   Importance: Undecided
   Status: Invalid

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

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

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

** No longer affects: libinput (Ubuntu)

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

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

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

** No longer affects: linux-oem-6.1 (Ubuntu Lunar)

** No longer affects: linux-oem-6.1 (Ubuntu Mantic)

** No longer affects: linux-oem-6.1 (Ubuntu Noble)

** No longer affects: linux-oem-6.5 (Ubuntu Lunar)

** No longer affects: libinput (Ubuntu Jammy)

** No longer affects: libinput (Ubuntu Lunar)

** No longer affects: libinput (Ubuntu Mantic)

** No longer affects: libinput (Ubuntu Noble)

** No longer affects: linux-hwe-6.2 (Ubuntu Lunar)

** No longer affects: linux-hwe-6.2 (Ubuntu Mantic)

** No longer affects: linux-hwe-6.2 (Ubuntu Noble)

** No longer affects: linux-oem-6.5 (Ubuntu Mantic)

** No longer affects: linux-oem-6.5 (Ubuntu Noble)

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: New => Confirmed

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
   Status: New => Confirmed

** Changed in: linux-hwe-6.2 (Ubuntu Jammy)
   Status: New => Confirmed

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

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

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

Title:
  Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Status in ideapad-laptop:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Confirmed
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  Hello.

  Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
  installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
  laptop and it was noticed that keyboard, touchpad and microphone are
  not working. The keyboard and touchpad work fine in BIOS setup and
  till GRUB (command

[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Here is the upstream patch for this issue:

https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/urgent=38d54ecfe293ed8bb26d05e6f0270a0aaa6656c6

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=218003
   Importance: Unknown
   Status: Unknown

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

Title:
  Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Status in ideapad-laptop:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Confirmed
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux source package in Noble:
  Confirmed
Status in Fedora:
  New

Bug description:
  Hello.

  Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
  installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
  laptop and it was noticed that keyboard, touchpad and microphone are
  not working. The keyboard and touchpad work fine in BIOS setup and
  till GRUB (command line). It was found that when external devices such
  as keyboard, mouse and microphone are connected through USB and 3.5
  jack, respectively, these work just fine. To confirm these are not
  hardware problems, Microsoft Windows 11  (Home) was installed in
  another disk partition and observed all these working alright. Hence a
  bug is being reported to draw attention of the concerned team and I
  request them to refer this issue and do the needful at the earliest.

  Regards,
  Pradip Kumar Das

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 08:04:42 2023
  InstallationDate: Installed on 2023-08-14 (22 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 2036742] Re: VI dGPU fails to initialize on Intel platforms w/ 5.14+

Here's the mainline commit with the fix for your issue:

https://github.com/torvalds/linux/commit/64ffd2f1d00c6235dabe9704bbb0d9ce3e28147f

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

Title:
  VI dGPU fails to initialize on Intel platforms w/ 5.14+

Status in linux package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  Booting from USB the latest Mantic Desktop daily image (2023-09-20),
  just after the initial logs, nothing is displayed on screen. The
  system is still alive since _autoinstall_ works as intended. Once
  provisioned, the problem is still present.

  It seems related to https://bugs.launchpad.net/ubuntu/+source/linux-
  firmware/+bug/2029396 .

  dmesg attached.

  [Test Case]

  Live boot Ubuntu Mantic Desktop canary (2023-09-19)

  [Where Problems Could Occur]

  Dell Optiplex 5090
  - Intel Core(TM) i7-11700
  - Advanced Micro Devices, Inc. [AMD/ATI] - 1002:699f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+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 2039191] Re: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization

2023-10-27 Thread John Cabaj

Verified to boot successfully. 32-bit machines otherwise not used on
GCP, anyway.

** Tags removed: verification-needed-mantic-linux-gcp
** Tags added: verification-done-mantic-linux-gcp

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

Title:
  Kernel oops on 32-0bit kernels due to x86_cache_alignment
  initialization

Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-gcp package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Lunar:
  Triaged
Status in linux-gcp source package in Lunar:
  Fix Committed
Status in linux-aws source package in Mantic:
  In Progress
Status in linux-gcp source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from

git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar

  [Fix]

  * Clean cherry pick from linux-next, commit 3e3255265291

  [Test Case]

  * Compile tested
  * Boot tested
  * To be tested by Google

  [Where things could go wrong]

  * Low chance of regression, isolated fix slightly modifying when value becomes
available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2039191/+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 2041670] Re: tmpfs: O_DIRECT | O_CREATE open reports open failure but actually creates a file.

2023-10-27 Thread Bug Watch Updater

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=218049.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2023-10-27T13:53:48+00:00 colin.i.king wrote:

Created attachment 305300
C reproducer of the problem. Run it on a tmpfs file system mounted on /mnt/tmpfs

creating a file on tmpfs with open(filename, O_RDWR | O_DIRECT |
O_CREAT, 0666) reports an open failure error EINVAL, but still creates
the file. The file should not be created if we hit such an error.

Tested this on 6.6.0-rc7 and 6.1.0-13 mainline kernels, x86-64.

mkdir /mnt/tmpfs
sudo mount -t tmpfs -o size=1G,nr_inodes=10k,mode=777 tmpfs /mnt/tmpfs
sudo chmod 666 /mnt/tmpfs

Run the attached program. It reports an open failure (errno 22, EINVAL)
but still manages to create the file.

Note this was original discovered by running stress-ng on tmpfs with the
open stressor: stress-ng --open 1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041670/comments/0


On 2023-10-27T14:30:36+00:00 colin.i.king wrote:

See also: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041670

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041670/comments/3


On 2023-10-27T14:36:29+00:00 colin.i.king wrote:

Also occurs on ramfs too.

Seems to occur on kernels from 4.4.x to current 6.6-rc6 (not tested
anything newer).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041670/comments/4


On 2023-10-27T14:48:49+00:00 aros wrote:

Confirming and CC'ing Christian Brauner.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041670/comments/5


On 2023-10-27T14:50:39+00:00 aros wrote:

Actually Hugh Dickins added O_DIRECT support, CC'ing him as well.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041670/comments/6


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => 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/2041670

Title:
   tmpfs: O_DIRECT | O_CREATE open reports open failure but actually
  creates a file.

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

Bug description:
  creating a file on tmpfs with open(filename, O_RDWR | O_DIRECT |
  O_CREAT, 0666) reports an open failure error EINVAL, but still creates
  the file. The file should not be created if we hit such an error.

  Tested and fails on:
  mantic amd64: 6.5.0-10-generic
  lunar amd64: 6.2.0-35-generic
  jammie amd64: 5.15.0-generic
  focal: 5.4.0-165-generic
  bionic: 4.15.0-213-generic
  trusty: 4.4.0-148-generic

  
  sudo mkdir /mnt/tmpfs
  sudo mount -t tmpfs -o size=1G,nr_inodes=10k,mode=777 tmpfs /mnt/tmpfs
  sudo chmod 666 /mnt/tmpfs
  gcc reproducer.c -o reproducer
  sudo ./reproducer

  Run the attached program. It reports an open failure (errno 22,
  EINVAL) but still manages to create the file.

  Note this was original discovered by running stress-ng on tmpfs with
  the open stressor: stress-ng --open 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2041670/+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 2041613] Re: correct cephfs pull request for uidmap support

** Description changed:

  [ Impact ]
  
-  * During mantic dev cycle, we pulled all of cephfs testing patches, rather 
than uidmapshift patches alone
-  * We also pulled in debug patches that generate a lot of dmesg and delays in 
the cephfs module
+  * During mantic dev cycle, we pulled all of cephfs testing patches, rather 
than uidmapshift patches alone
+  * We also pulled in debug patches that generate a lot of dmesg and delays in 
the cephfs module
  
  [ Test Plan ]
  
-  * run ceph fs and experience less dmesg at info level
+  * run ceph fs and experience less dmesg at info level
  
  [ Where problems could occur ]
  
-  * Hopefully the reverts were done correctly, and none of the messages
+  * Hopefully the reverts were done correctly, and none of the messages
  reference non-existing things, in all the code paths.
  
  [ Other Info ]
-  
-  * Story time how we got here:
+ 
+  * Story time how we got here:
  
  The following pull requests
  
  BugLink: https://bugs.launchpad.net/bugs/2038522
  BugLink: https://bugs.launchpad.net/bugs/2032959
  
  generated the following commit list 1:
  
  eddf9ed788 UBUNTU: [Config] disable shiftfs
  72e8806959 UBUNTU: SAUCE: ceph: enable unsafe idmapped mounts by default
  80b85e5d76 UBUNTU: SAUCE: ceph: allow idmapped mounts
  9d341bb8aa UBUNTU: SAUCE: ceph/file: allow idmapped atomic_open inode op
  ddd1a8ee19 UBUNTU: SAUCE: ceph/acl: allow idmapped set_acl inode op
  1b12f12987 UBUNTU: SAUCE: ceph: allow idmapped setattr inode op
  b1f695f0d1 UBUNTU: SAUCE: ceph: pass idmap to __ceph_setattr
  8a9a3b9e88 UBUNTU: SAUCE: ceph: allow idmapped permission inode op
  e5471722b3 UBUNTU: SAUCE: ceph: allow idmapped getattr inode op
  f6b1d353fa UBUNTU: SAUCE: ceph: pass an idmapping to mknod/symlink/mkdir
  5ecfa6f659 UBUNTU: SAUCE: ceph: add enable_unsafe_idmap module parameter
  19724a984a UBUNTU: SAUCE: ceph: handle idmapped mounts in 
create_request_message()
  6ec4e53238 UBUNTU: SAUCE: ceph: stash idmapping in mdsc request
  8006617c5e UBUNTU: SAUCE: fs: export mnt_idmap_get/mnt_idmap_put
  55f4f0afc5 UBUNTU: SAUCE: ceph: make num_fwd and num_retry to __u32
  54e03068d6 UBUNTU: SAUCE: ceph: make the members in struct 
ceph_mds_request_args_ext an union
  f7ec09aaac UBUNTU: SAUCE: ceph: print the client global_id in all the debug 
logs
  b2831559c5 UBUNTU: SAUCE: ceph: add ceph_inode_to_client() helper support
  a0852434ee UBUNTU: SAUCE: ceph: move mdsmap.h to fs/ceph/
  cfda2c4b70 UBUNTU: SAUCE: ceph: rename _to_client() to _to_fs_client()
  42924fda3a UBUNTU: SAUCE: ceph: pass the mdsc to several helpers
  9f6e6f9ce9 UBUNTU: SAUCE: ceph: add the *_client debug macros support
  8f61639667 UBUNTU: SAUCE: ceph: BUG if MDS changed truncate_seq with client 
caps still outstanding
  a53dba9297 UBUNTU: SAUCE: ceph: make sure all the files successfully put 
before unmounting
  17fcf5d75d UBUNTU: SAUCE: mm: BUG if filemap_alloc_folio gives us a folio 
with a non-NULL ->private
  834ebb591f UBUNTU: SAUCE: ceph: dump info about cap flushes when we're 
waiting too long for them
  498d08b9bd UBUNTU: SAUCE: rbd: bump RBD_MAX_PARENT_CHAIN_LEN to 128
  3ae75e2438 UBUNTU: SAUCE: libceph: do not include crypto/algapi.h
  d984763988 UBUNTU: SAUCE: ceph: switch ceph_lookup/atomic_open() to use new 
fscrypt helper
  8e298c72fb UBUNTU: SAUCE: ceph: fix updating i_truncate_pagecache_size for 
fscrypt
  288f935219 UBUNTU: SAUCE: ceph: wait for OSD requests' callbacks to finish 
when unmounting
  435fc54954 UBUNTU: SAUCE: ceph: drop messages from MDS when unmounting
  862a1e3c2a UBUNTU: SAUCE: ceph: update documentation regarding snapshot 
naming limitations
  904f39f283 UBUNTU: SAUCE: ceph: prevent snapshot creation in encrypted locked 
directories
  a47bdc0f8a UBUNTU: SAUCE: ceph: add support for encrypted snapshot names
  e4202a1c3e UBUNTU: SAUCE: ceph: invalidate pages when doing direct/sync writes
  9f781cfb0d UBUNTU: SAUCE: ceph: plumb in decryption during reads
  e76383977f UBUNTU: SAUCE: ceph: add encryption support to writepage and 
writepages
  0b571b2ac0 UBUNTU: SAUCE: ceph: add read/modify/write to ceph_sync_write
  a81bd5f1c8 UBUNTU: SAUCE: ceph: align data in pages in ceph_sync_write
  edbe3d2a62 UBUNTU: SAUCE: ceph: don't use special DIO path for encrypted 
inodes
  efed7d1764 UBUNTU: SAUCE: ceph: add truncate size handling support for fscrypt
  5d65284a6a UBUNTU: SAUCE: ceph: add object version support for sync read
  d76cff7c37 UBUNTU: SAUCE: libceph: allow ceph_osdc_new_request to accept a 
multi-op read
  53d1c3958e UBUNTU: SAUCE: libceph: add CEPH_OSD_OP_ASSERT_VER support
  7ecbaa5849 UBUNTU: SAUCE: ceph: add infrastructure for file encryption and 
decryption
  4142d15305 UBUNTU: SAUCE: ceph: handle fscrypt fields in cap messages from MDS
  53507ac6a8 UBUNTU: SAUCE: ceph: size handling in MClientRequest, cap updates 
and inode traces
  b9936d13f4 UBUNTU: SAUCE: ceph: mark directory as non-complete after loading 
key
  906d57a83b UBUNTU: SAUCE: ceph: allow

[Kernel-packages] [Bug 2041613] Re: correct cephfs pull request for uidmap support

** Description changed:

- correct cephfs changes for uidmap support
+ The following pull requests
+ 
+ BugLink: https://bugs.launchpad.net/bugs/2038522
+ BugLink: https://bugs.launchpad.net/bugs/2032959
+ 
+ generating the following commit list 1:
+ 
+ eddf9ed788 UBUNTU: [Config] disable shiftfs
+ 72e8806959 UBUNTU: SAUCE: ceph: enable unsafe idmapped mounts by default
+ 80b85e5d76 UBUNTU: SAUCE: ceph: allow idmapped mounts
+ 9d341bb8aa UBUNTU: SAUCE: ceph/file: allow idmapped atomic_open inode op
+ ddd1a8ee19 UBUNTU: SAUCE: ceph/acl: allow idmapped set_acl inode op
+ 1b12f12987 UBUNTU: SAUCE: ceph: allow idmapped setattr inode op
+ b1f695f0d1 UBUNTU: SAUCE: ceph: pass idmap to __ceph_setattr
+ 8a9a3b9e88 UBUNTU: SAUCE: ceph: allow idmapped permission inode op
+ e5471722b3 UBUNTU: SAUCE: ceph: allow idmapped getattr inode op
+ f6b1d353fa UBUNTU: SAUCE: ceph: pass an idmapping to mknod/symlink/mkdir
+ 5ecfa6f659 UBUNTU: SAUCE: ceph: add enable_unsafe_idmap module parameter
+ 19724a984a UBUNTU: SAUCE: ceph: handle idmapped mounts in 
create_request_message()
+ 6ec4e53238 UBUNTU: SAUCE: ceph: stash idmapping in mdsc request
+ 8006617c5e UBUNTU: SAUCE: fs: export mnt_idmap_get/mnt_idmap_put
+ 55f4f0afc5 UBUNTU: SAUCE: ceph: make num_fwd and num_retry to __u32
+ 54e03068d6 UBUNTU: SAUCE: ceph: make the members in struct 
ceph_mds_request_args_ext an union
+ f7ec09aaac UBUNTU: SAUCE: ceph: print the client global_id in all the debug 
logs
+ b2831559c5 UBUNTU: SAUCE: ceph: add ceph_inode_to_client() helper support
+ a0852434ee UBUNTU: SAUCE: ceph: move mdsmap.h to fs/ceph/
+ cfda2c4b70 UBUNTU: SAUCE: ceph: rename _to_client() to _to_fs_client()
+ 42924fda3a UBUNTU: SAUCE: ceph: pass the mdsc to several helpers
+ 9f6e6f9ce9 UBUNTU: SAUCE: ceph: add the *_client debug macros support
+ 8f61639667 UBUNTU: SAUCE: ceph: BUG if MDS changed truncate_seq with client 
caps still outstanding
+ a53dba9297 UBUNTU: SAUCE: ceph: make sure all the files successfully put 
before unmounting
+ 17fcf5d75d UBUNTU: SAUCE: mm: BUG if filemap_alloc_folio gives us a folio 
with a non-NULL ->private
+ 834ebb591f UBUNTU: SAUCE: ceph: dump info about cap flushes when we're 
waiting too long for them
+ 498d08b9bd UBUNTU: SAUCE: rbd: bump RBD_MAX_PARENT_CHAIN_LEN to 128
+ 3ae75e2438 UBUNTU: SAUCE: libceph: do not include crypto/algapi.h
+ d984763988 UBUNTU: SAUCE: ceph: switch ceph_lookup/atomic_open() to use new 
fscrypt helper
+ 8e298c72fb UBUNTU: SAUCE: ceph: fix updating i_truncate_pagecache_size for 
fscrypt
+ 288f935219 UBUNTU: SAUCE: ceph: wait for OSD requests' callbacks to finish 
when unmounting
+ 435fc54954 UBUNTU: SAUCE: ceph: drop messages from MDS when unmounting
+ 862a1e3c2a UBUNTU: SAUCE: ceph: update documentation regarding snapshot 
naming limitations
+ 904f39f283 UBUNTU: SAUCE: ceph: prevent snapshot creation in encrypted locked 
directories
+ a47bdc0f8a UBUNTU: SAUCE: ceph: add support for encrypted snapshot names
+ e4202a1c3e UBUNTU: SAUCE: ceph: invalidate pages when doing direct/sync writes
+ 9f781cfb0d UBUNTU: SAUCE: ceph: plumb in decryption during reads
+ e76383977f UBUNTU: SAUCE: ceph: add encryption support to writepage and 
writepages
+ 0b571b2ac0 UBUNTU: SAUCE: ceph: add read/modify/write to ceph_sync_write
+ a81bd5f1c8 UBUNTU: SAUCE: ceph: align data in pages in ceph_sync_write
+ edbe3d2a62 UBUNTU: SAUCE: ceph: don't use special DIO path for encrypted 
inodes
+ efed7d1764 UBUNTU: SAUCE: ceph: add truncate size handling support for fscrypt
+ 5d65284a6a UBUNTU: SAUCE: ceph: add object version support for sync read
+ d76cff7c37 UBUNTU: SAUCE: libceph: allow ceph_osdc_new_request to accept a 
multi-op read
+ 53d1c3958e UBUNTU: SAUCE: libceph: add CEPH_OSD_OP_ASSERT_VER support
+ 7ecbaa5849 UBUNTU: SAUCE: ceph: add infrastructure for file encryption and 
decryption
+ 4142d15305 UBUNTU: SAUCE: ceph: handle fscrypt fields in cap messages from MDS
+ 53507ac6a8 UBUNTU: SAUCE: ceph: size handling in MClientRequest, cap updates 
and inode traces
+ b9936d13f4 UBUNTU: SAUCE: ceph: mark directory as non-complete after loading 
key
+ 906d57a83b UBUNTU: SAUCE: ceph: allow encrypting a directory while not having 
Ax caps
+ 4a58d08c63 UBUNTU: SAUCE: ceph: add some fscrypt guardrails
+ 83229b1f64 UBUNTU: SAUCE: ceph: create symlinks with encrypted and 
base64-encoded targets
+ 6f10a0358e UBUNTU: SAUCE: ceph: add support to readdir for encrypted names
+ 03584cc481 UBUNTU: SAUCE: ceph: pass the request to parse_reply_info_readdir()
+ a3743d846e UBUNTU: SAUCE: ceph: make ceph_fill_trace and ceph_get_name 
decrypt names
+ 6c9af9c3a8 UBUNTU: SAUCE: ceph: add helpers for converting names for userland 
presentation
+ 8c360700dd UBUNTU: SAUCE: ceph: make d_revalidate call fscrypt revalidator 
for encrypted dentries
+ 8344e0ee75 UBUNTU: SAUCE: ceph: set DCACHE_NOKEY_NAME flag in 
ceph_lookup/atomic_open()
+ 867d49582b UBUNTU: SAUCE: ceph: decode alternate_name in lease info
+ a4db7516c2 UBUNTU: SAUCE: ceph: send alternate_name in

[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

2023-10-27 Thread Endre Olah

Hi Jean-Marie,

"enter" is used in some comments and means either that you have to
switch your current folder/directory when you are in terminal. So
commands should be executed in the right folder, otherwise you might do
something else or maybe nothing.

So "enter kernel" means to  to cd to the decompressed folder of the
kernel source files.

Quinten's description worked for me and it is not that difficult to
follow.

Rgds

 Endre

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

Title:
  Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Status in ideapad-laptop:
  New
Status in libinput package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux-signed-oem-6.5 package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  Hello.

  Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
  installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
  laptop and it was noticed that keyboard, touchpad and microphone are
  not working. The keyboard and touchpad work fine in BIOS setup and
  till GRUB (command line). It was found that when external devices such
  as keyboard, mouse and microphone are connected through USB and 3.5
  jack, respectively, these work just fine. To confirm these are not
  hardware problems, Microsoft Windows 11  (Home) was installed in
  another disk partition and observed all these working alright. Hence a
  bug is being reported to draw attention of the concerned team and I
  request them to refer this issue and do the needful at the earliest.

  Regards,
  Pradip Kumar Das

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 08:04:42 2023
  InstallationDate: Installed on 2023-08-14 (22 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 2041613] Re: correct cephfs pull request for uidmap support

** Summary changed:

- correct cephfs changes for uidmap support
+ correct cephfs pull request for uidmap support

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

Title:
  correct cephfs pull request for uidmap support

Status in linux package in Ubuntu:
  New

Bug description:
  correct cephfs changes for uidmap support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041613/+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 2041670] [NEW] tmpfs: O_DIRECT | O_CREATE open reports open failure but actually creates a file.

2023-10-27 Thread Colin Ian King

Public bug reported:

creating a file on tmpfs with open(filename, O_RDWR | O_DIRECT |
O_CREAT, 0666) reports an open failure error EINVAL, but still creates
the file. The file should not be created if we hit such an error.

Tested and fails on:
mantic amd64: 6.5.0-10-generic
lunar amd64: 6.2.0-35-generic
jammie amd64: 5.15.0-generic
focal: 5.4.0-165-generic
bionic: 4.15.0-213-generic
trusty: 4.4.0-148-generic


sudo mkdir /mnt/tmpfs
sudo mount -t tmpfs -o size=1G,nr_inodes=10k,mode=777 tmpfs /mnt/tmpfs
sudo chmod 666 /mnt/tmpfs
gcc reproducer.c -o reproducer
sudo ./reproducer

Run the attached program. It reports an open failure (errno 22, EINVAL)
but still manages to create the file.

Note this was original discovered by running stress-ng on tmpfs with the
open stressor: stress-ng --open 1

** Affects: linux
 Importance: Unknown
 Status: Unknown

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

** Attachment added: "C source to reproduce the issue"
   
https://bugs.launchpad.net/bugs/2041670/+attachment/5713768/+files/reproducer.c

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

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=218049
   Importance: Unknown
   Status: Unknown

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

Title:
   tmpfs: O_DIRECT | O_CREATE open reports open failure but actually
  creates a file.

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New

Bug description:
  creating a file on tmpfs with open(filename, O_RDWR | O_DIRECT |
  O_CREAT, 0666) reports an open failure error EINVAL, but still creates
  the file. The file should not be created if we hit such an error.

  Tested and fails on:
  mantic amd64: 6.5.0-10-generic
  lunar amd64: 6.2.0-35-generic
  jammie amd64: 5.15.0-generic
  focal: 5.4.0-165-generic
  bionic: 4.15.0-213-generic
  trusty: 4.4.0-148-generic

  
  sudo mkdir /mnt/tmpfs
  sudo mount -t tmpfs -o size=1G,nr_inodes=10k,mode=777 tmpfs /mnt/tmpfs
  sudo chmod 666 /mnt/tmpfs
  gcc reproducer.c -o reproducer
  sudo ./reproducer

  Run the attached program. It reports an open failure (errno 22,
  EINVAL) but still manages to create the file.

  Note this was original discovered by running stress-ng on tmpfs with
  the open stressor: stress-ng --open 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2041670/+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 2041668] Re: Memory leak in 23.10 kernel (6.5.0-10)

** Attachment added: "dmesg.log"

https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2041668/+attachment/5713765/+files/dmesg.log

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

Title:
Memory leak in 23.10 kernel (6.5.0-10)

Status in linux-meta package in Ubuntu:
New

Bug description:
There appears to be a memory 'leak' in the kernel of the latest Ubuntu release
(Mantic Minotaur, kernel version 6.5.0-10). I put 'leak' in quotes because
this
memory appears to be allocated but never used. The kernel's memory
over-commit
mechanism seems to prevent this leak from manifesting in OOM killer triggers
or
other failures.

The primary symptom is a steady increase in the value reported as
'Committed_AS'
in '/proc/meminfo'. The other memory stats reported there remain reasonable,
though.

I've observed this problem on a fairly diverse set of machines (both VMs and
physical machines) with a variety of workloads. Busier machines seem to have
a
faster leak rate. I've tried to narrow down the issue by rebooting into
single
user mode, killing all userspace processes (except the systemd processes) and
removing as many kernel models as possible. The problem continues in that
state. I didn't see any obvious culprits in /proc/slabinfo nor
/proc/vmallocinfo.

So far, the only way I've been able to remediate this issue is to reboot back
into the Lunar Lobster kernel (6.2.0-35). I think this fact alone rules out
any
triggers that may be part of the 23.10 userspace environment.

I've attached the generic debug info requested by this component's bug
template
from an example machine. Please let me know if there is any more information I
can provide. It seems to be pretty trivial to reproduce though, and I'm
guessing it has not been reported yet because the leak doesn't actually
manifest
in an out-of-memory situation. At least, I haven't observed that yet. The
worst case I've observed was 150 GB of memory committed on a machine with 16
GB
of physical RAM after about 24 hours. Moving back to the previous kernel
version, the committed memory statistic holds fairly steady around 7 GB on
that
machine and workload.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2041668/+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 2041668] Re: Memory leak in 23.10 kernel (6.5.0-10)

** Attachment added: "lspci-vnvn.log"

https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2041668/+attachment/5713766/+files/lspci-vnvn.log

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

Title:
Memory leak in 23.10 kernel (6.5.0-10)

Status in linux-meta package in Ubuntu:
New

The primary symptom is a steady increase in the value reported as
'Committed_AS'
in '/proc/meminfo'. The other memory stats reported there remain reasonable,
though.

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

[Kernel-packages] [Bug 2041668] Re: Memory leak in 23.10 kernel (6.5.0-10)

** Attachment added: "version.log"

https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2041668/+attachment/5713764/+files/version.log

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

Title:
Memory leak in 23.10 kernel (6.5.0-10)

Status in linux-meta package in Ubuntu:
New

The primary symptom is a steady increase in the value reported as
'Committed_AS'
in '/proc/meminfo'. The other memory stats reported there remain reasonable,
though.

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

[Kernel-packages] [Bug 2041668] [NEW] Memory leak in 23.10 kernel (6.5.0-10)

Public bug reported:

There appears to be a memory 'leak' in the kernel of the latest Ubuntu release
(Mantic Minotaur, kernel version 6.5.0-10).  I put 'leak' in quotes because this
memory appears to be allocated but never used.  The kernel's memory over-commit
mechanism seems to prevent this leak from manifesting in OOM killer triggers or
other failures.

The primary symptom is a steady increase in the value reported as 'Committed_AS'
in '/proc/meminfo'.  The other memory stats reported there remain reasonable,
though.

I've observed this problem on a fairly diverse set of machines (both VMs and
physical machines) with a variety of workloads.  Busier machines seem to have a
faster leak rate.  I've tried to narrow down the issue by rebooting into single
user mode, killing all userspace processes (except the systemd processes) and
removing as many kernel models as possible.  The problem continues in that
state.  I didn't see any obvious culprits in /proc/slabinfo nor
/proc/vmallocinfo.

So far, the only way I've been able to remediate this issue is to reboot back
into the Lunar Lobster kernel (6.2.0-35).  I think this fact alone rules out any
triggers that may be part of the 23.10 userspace environment.

I've attached the generic debug info requested by this component's bug template
from an example machine. Please let me know if there is any more information I
can provide.  It seems to be pretty trivial to reproduce though, and I'm
guessing it has not been reported yet because the leak doesn't actually manifest
in an out-of-memory situation.  At least, I haven't observed that yet.  The
worst case I've observed was 150 GB of memory committed on a machine with 16 GB
of physical RAM after about 24 hours.  Moving back to the previous kernel
version, the committed memory statistic holds fairly steady around 7 GB on that
machine and workload.

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

** Attachment added: "uname-a.log"
   
https://bugs.launchpad.net/bugs/2041668/+attachment/5713763/+files/uname-a.log

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

Title:
  Memory leak in 23.10 kernel (6.5.0-10)

Status in linux-meta package in Ubuntu:
  New

Bug description:
  There appears to be a memory 'leak' in the kernel of the latest Ubuntu release
  (Mantic Minotaur, kernel version 6.5.0-10).  I put 'leak' in quotes because 
this
  memory appears to be allocated but never used.  The kernel's memory 
over-commit
  mechanism seems to prevent this leak from manifesting in OOM killer triggers 
or
  other failures.

  The primary symptom is a steady increase in the value reported as 
'Committed_AS'
  in '/proc/meminfo'.  The other memory stats reported there remain reasonable,
  though.

  I've observed this problem on a fairly diverse set of machines (both VMs and
  physical machines) with a variety of workloads.  Busier machines seem to have 
a
  faster leak rate.  I've tried to narrow down the issue by rebooting into 
single
  user mode, killing all userspace processes (except the systemd processes) and
  removing as many kernel models as possible.  The problem continues in that
  state.  I didn't see any obvious culprits in /proc/slabinfo nor
  /proc/vmallocinfo.

  So far, the only way I've been able to remediate this issue is to reboot back
  into the Lunar Lobster kernel (6.2.0-35).  I think this fact alone rules out 
any
  triggers that may be part of the 23.10 userspace environment.

  I've attached the generic debug info requested by this component's bug 
template
  from an example machine. Please let me know if there is any more information I
  can provide.  It seems to be pretty trivial to reproduce though, and I'm
  guessing it has not been reported yet because the leak doesn't actually 
manifest
  in an out-of-memory situation.  At least, I haven't observed that yet.  The
  worst case I've observed was 150 GB of memory committed on a machine with 16 
GB
  of physical RAM after about 24 hours.  Moving back to the previous kernel
  version, the committed memory statistic holds fairly steady around 7 GB on 
that
  machine and workload.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2041668/+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 1989256] Re: nvidia-dkms-460 460.80-0ubuntu0.20.04.2: nvidia kernel module failed to build

2023-10-27 Thread Launchpad Bug Tracker

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

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Status: New => Confirmed

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

Title:
  nvidia-dkms-460 460.80-0ubuntu0.20.04.2: nvidia kernel module failed
  to build

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed

Bug description:
  I don't know the reason for this

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-dkms-460 470.141.03-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31
  Uname: Linux 5.10.0-1026-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.14.0-1051-oem
  Date: Sat Sep 10 17:00:19 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  DuplicateSignature: 
dkms:nvidia-dkms-460:460.80-0ubuntu0.20.04.2:/var/lib/dkms/nvidia/460.80/build/common/inc/nv-time.h:208:18:
 error: ‘struct task_struct’ has no member named ‘state’; did you mean 
‘__state’?
  InstallationDate: Installed on 2022-05-24 (109 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  PackageVersion: 460.80-0ubuntu0.20.04.2
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: nvidia-graphics-drivers-470
  Title: nvidia-dkms-460 460.80-0ubuntu0.20.04.2: nvidia kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1989256/+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 2040181] Re: upgrade zfs-linux to 2.2.0 final

2023-10-27 Thread Timo Aaltonen

Hello Dimitri, or anyone else affected,

Accepted zfs-linux into mantic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/2.2.0-0ubuntu1~23.10 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: zfs-linux (Ubuntu Mantic)
   Status: Confirmed => Fix Committed

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

Title:
  upgrade zfs-linux to 2.2.0 final

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

Bug description:
  [ Impact ]

   * Potential data loss with zfs 2.2.0-rc3 resolved in -rc5, proposal
  to update to final

   * Ubuntu Mantic shipped 2.2.0-rc3 with approximately 10 additional
  cherrypicks, or kernel team created fixes that got contributed &
  accepted upstream. At the time this was the only way to get zfs
  working with  v6.5 kernels and also drop the need for shiftfs (due to
  zfs impovements). Since us shipping this package, upstream has
  identified and fixed multiple small bugfixes in the subsequent RC and
  the final releases, including one bug fix that can lead to potential
  data loss.

   * The 2.2.0 release branch was frozen for a long time already, and
  outstanding number of commits of fixes that Mantic does not have is
  less than 30 small patches.

   * Proposal to upgrade our build to 2.2.0 final, pick up all the
  regression fixes, and drop all the cherrypicked patches that enable
  v6.5 support. This will give us the best kernel driver to support in
  the runnup to next Ubuntu LTS.

  [ Test Plan ]

   * autopkgtest pass

   * kernel regression zfs testsuite pass

   * zsys integration test pass

   * LXD support retested

  [ Where problems could occur ]

   * LXD snap in edge shipped zfs tooling of RC5 version until 16th
  October when they upgraded to 2.2.0 final, there are no kernel-
  userspace incompatiblities between RC & final, but we should
  explicitly test this.

  [ Other Info ]

   * Upstream is alerting us to the potential data loss and requesting
  upgrade to 2.2.0-rc5 or better.

  [ Abbriviated changes being introduced ]

  $ git log --oneline 4a104ac047..95785196f2 -- cmd/ lib/ module/os/linux/ | 
grep -v compat
  810fc49a3e Ensure we call fput when cloning fails due to different devices.
  a80e1f1c90 zvol: Temporally disable blk-mq
  33d7c2d165 import: require force when cachefile hostid doesn't match on-disk
  8015e2ea66 Add '-u' - nomount flag for zfs set
  c53bc3837c Improve the handling of sharesmb,sharenfs properties
  e9dc31c74e Update the behavior of mountpoint property
  608741d062 Report ashift of L2ARC devices in zdb
  0ce1b2ca19 Invoke zdb by guid to avoid import errors
  0aabd6b482 ZIL: Avoid dbuf_read() in ztest_get_data()
  a199cac6cd status: report pool suspension state under failmode=continue
  729507d309 Fix occasional rsend test crashes
  3af63683fe cmd: add 'help' subcommand to zpool and zfs
  9aa1a2878e Fix incorrect expected error in ztest
  f7a07d76ee Retire z_nr_znodes
  54c6fbd378 zed: Allow autoreplace and fault LEDs for removed vdevs
  32949f2560 Relax error reporting in zpool import and zpool split
  63159e5bda checkstyle: fix action failures
  e99e684b33 zed: update zed.d/statechange-slot_off.sh
  d19304ffee zed: Add zedlet to power off slot when drive is faulted
  92f095a903 copy_file_range: fix fallback when source create on same txg
  895cb689d3 zfs_clone_range should return a descriptive error codes
  6bdc7259d1 libzfs: sendrecv: send_progress_thread: handle SIGINFO/SIGUSR1
  df8c9f351d ZIL: Second attempt to reduce scope of zl_issuer_lock.
  0ae7bfc0a4 zpool_vdev_remove() should handle EALREADY error return
  bd1eab16eb linux: zfs: ctldir: set [amc]time to snapshot's creation property
  c47f0f4417

[Kernel-packages] [Bug 2036627] Re: Azure: net: mana: Configure hwc timeout from hardware

2023-10-27 Thread Tim Gardner

** Tags removed: verification-needed-jammy-linux-azure-6.5 
verification-needed-lunar-linux-azure
** Tags added: verification-done-jammy-linux-azure-6.5 
verification-done-lunar-linux-azure

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

Title:
  Azure: net: mana: Configure hwc timeout from hardware

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

Bug description:
  SRU Justification

  [Impact]

  At present hwc timeout value is a fixed value. This patch sets the hwc
  timeout from the hardware. It now uses a new hardware capability
  GDMA_DRV_CAP_FLAG_1_HWC_TIMEOUT_RECONFIG to query and set the value
  in hwc_timeout.

  [Test Plan]

  Microsoft tested and approved.

  [Regression Potential]

  Timeouts could get mis-configured.

  [Other Info]

  SF: #00365762

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2036627/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland

#75

You can turn on proposed and then use ppa-purge command to remove my
PPA.

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

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy
  load in Wayland

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Committed
Status in linux source package in Mantic:
  Triaged
Status in mutter source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems,
  sometimes when the screen locks, sometimes when launching particular
  apps.

  [ Workaround ]

  Add this to /etc/environment:

    MUTTER_DEBUG_KMS_THREAD_TYPE=user

  and then reboot.

  [ Test Plan ]

  Not all Ryzen systems (including one I just purchased) are able to
  reproduce the bug. We have no choice but to leave final verification
  to the community. Anyone affected should try locking their screen and
  verify they are not instantly returned to the login screen.

  [ Where problems could occur ]

  Anywhere in frame scheduling and particularly for mouse cursor
  movement since that's what the real-time thread exists to optimize.

  [ Original Description ]

  I have this issue on Ubuntu 23.10. Lock screen works only with an external 
monitor connected. Otherwise the session is ended and the user is logged out 
and brought to the gdm screen.
  All works in xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 22:32:22 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-03 (3 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2034619/+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 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

2023-10-27 Thread Frank Heimes

@roxanan many thx for having accepted and applied this (even if it was a
bit late) - appreciate it!

** Changed in: ubuntu-z-systems
   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/2039575

Title:
  SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  Bug description by Nils H.:

  
   Overview: 
  
  The following line in the SMC stats code (net/smc/smc_stats.h) caught my 
attention when using a payload of exactly 4096 bytes:

  #define SMC_STAT_PAYLOAD_SUB(_smc_stats, _tech, key, _len, _rc) \
  do { \
typeof(_smc_stats) stats = (_smc_stats); \
typeof(_tech) t = (_tech); \
typeof(_len) l = (_len); \
int _pos = fls64((l) >> 13); \
typeof(_rc) r = (_rc); \
int m = SMC_BUF_MAX - 1; \
this_cpu_inc((*stats).smc[t].key ## _cnt); \
if (r <= 0) \
break; \
_pos = (_pos < m) ? ((l == 1 << (_pos + 12)) ? _pos - 1 : _pos) : m; \  
<---
this_cpu_inc((*stats).smc[t].key ## _pd.buf[_pos]); \
this_cpu_add((*stats).smc[t].key ## _bytes, r); \
  } \
  while (0)

  
  With l = 4096, _pos evaluates to -1.

  
  Checking with the following uperf profile:
  # cat rr1c-4kx4k---1.xml 
  
  



 











  

  
  smcd stats output:
  # smcd -d stats reset
  SMC-D Connections Summary
Total connections handled 2
SMC connections   2 (client 2, server 0)
  v1  0
  v2  2
Handshake errors  0 (client 0, server 0)
Avg requests per SMC conn14.0
TCP fallback  0 (client 0, server 0)

  RX Stats
Data transmitted (Bytes)   5796 (5.796K)
Total requests9
Buffer full   0 (0.00%)
Buffer downgrades 0
Buffer reuses 0
  8KB16KB32KB64KB   128KB   256KB   512KB  >512KB
Bufs0   0   0   2   0   0   0   1
Reqs8   0   0   0   0   0   0   0

  TX Stats
Data transmitted (Bytes)   9960 (9.960K)
Total requests   19
Buffer full   0 (0.00%)
Buffer full (remote)  0 (0.00%)
Buffer too small  0 (0.00%)
Buffer too small (remote) 0 (0.00%)
Buffer downgrades 0
Buffer reuses 0
  8KB16KB32KB64KB   128KB   256KB   512KB  >512KB
Bufs0   2   0   0   0   0   0   0
Reqs   18   0   0   0   0   0   0   1

  Extras
Special socket calls  0
  cork0
  nodelay 0
  sendpage0
  splice  0
  urgent data 0

  
  Instead of including the payload in the wrong >512KB buckets, output should 
be to have 19 reqs in the 8KB buckets for TX stats and 9 reqs in the 8KB bucket 
for RX stats.


  
   Repro:
  
  0. Install uperf.
  1. Reset SMC-D stats on client and server.
  2. Start uperf at server side: "uperf -vs".
  3. Update profile with remote IP (server IP) and start uperf at client: 
"uperf -vai 5 -m rr1c-4kx4k---1.xml" (uperf profile, see above)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2039575/+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 2040192] Re: AppArmor spams kernel log with assert when auditing

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

** Changed in: linux (Ubuntu Mantic)
   Status: Incomplete => Fix Committed

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => John Johansen (jjohansen)

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

Title:
  AppArmor spams kernel log with assert when auditing

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  A reply to a prompt request that denies all permissions requested will throw 
the following warning, because the auditing code does not expect the request 
field to be empty when generating the audit message.   
   

  Sep 27 22:48:14 ubuntu-mantic snapd[596]: listener.go:189: Sending access 
response back to kernel: {MsgNotification:{MsgHeader:{Length:0 Version:0} 
NotificationType:APPARMOR_NOTIF_RESP Signalled:0 NoCache:1 ID:2 Error:0} 
Error:-13 Allow:0 Deny:4}
  Sep 27 22:48:14 ubuntu-mantic kernel: [ cut here ]
  Sep 27 22:48:14 ubuntu-mantic kernel: AppArmor WARN aa_audit_file: 
((!ad.request)): 
  Sep 27 22:48:14 ubuntu-mantic kernel: WARNING: CPU: 3 PID: 2082 at 
security/apparmor/file.c:268 aa_audit_file+0x2b1/0x310
  Sep 27 22:48:14 ubuntu-mantic kernel: Modules linked in: snd_seq_dummy 
snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 
snd_timer snd soundcore binfmt_misc nls_iso8859_1 kvm_intel kvm irqbypass 
crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic 
ghash_clmulni_intel sha512_ssse3 aesni_intel virtio_gpu crypto_simd cryptd 
virtio_dma_buf drm_shmem_helper 9pnet_virtio drm_kms_helper 9pnet 
vmw_vsock_virtio_transport virtio_input vmw_vsock_virtio_transport_common 
input_leds joydev serio_raw vsock msr parport_pc ppdev lp parport drm virtiofs 
efi_pstore ip_tables x_tables autofs4 virtio_net xhci_pci ahci psmouse 
net_failover libahci xhci_pci_renesas failover virtio_rng
  Sep 27 22:48:14 ubuntu-mantic kernel: CPU: 3 PID: 2082 Comm: bash Not tainted 
6.5.0-5-generic #5+aa4.0.0+debug5-Ubuntu
  Sep 27 22:48:14 ubuntu-mantic kernel: Hardware name: QEMU Standard PC (Q35 + 
ICH9, 2009)/LXD, BIOS unknown 2/2/2022
  Sep 27 22:48:14 ubuntu-mantic kernel: RIP: 0010:aa_audit_file+0x2b1/0x310
  Sep 27 22:48:14 ubuntu-mantic kernel: Code: 3c ff ff ff e8 80 6f a8 ff 44 8b 
95 3c ff ff ff 5a 59 e9 e3 fe ff ff 48 c7 c6 98 5c 08 84 48 c7 c7 90 1a 60 84 
e8 9f da 9d ff <0f> 0b 8b 85 78 ff ff ff e9 05 ff ff ff 48 89 de 4c 89 f7 e8 b7 
f5
  Sep 27 22:48:14 ubuntu-mantic kernel: RSP: 0018:b66a82b57968 EFLAGS: 
00010246
  Sep 27 22:48:14 ubuntu-mantic kernel: RAX:  RBX: 
b66a82b57b24 RCX: 
  Sep 27 22:48:14 ubuntu-mantic kernel: RDX:  RSI: 
 RDI: 
  Sep 27 22:48:14 ubuntu-mantic kernel: RBP: b66a82b57a30 R08: 
 R09: 
  Sep 27 22:48:14 ubuntu-mantic kernel: R10:  R11: 
 R12: 
  Sep 27 22:48:14 ubuntu-mantic kernel: R13: 8b160239d800 R14: 
b66a82b57970 R15: 0001
  Sep 27 22:48:14 ubuntu-mantic kernel: FS:  7f1f7d3b3380() 
GS:8b17778c() knlGS:
  Sep 27 22:48:14 ubuntu-mantic kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Sep 27 22:48:14 ubuntu-mantic kernel: CR2: 55d4482063f0 CR3: 
000137e64000 CR4: 00750ee0
  Sep 27 22:48:14 ubuntu-mantic kernel: PKRU: 5554
  Sep 27 22:48:14 ubuntu-mantic kernel: Call Trace:
  Sep 27 22:48:14 ubuntu-mantic kernel:  
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? show_regs+0x6d/0x80
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? __warn+0x89/0x160
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? aa_audit_file+0x2b1/0x310
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? report_bug+0x17e/0x1b0
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? handle_bug+0x51/0xa0
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? exc_invalid_op+0x18/0x80
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? asm_exc_invalid_op+0x1b/0x20
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? aa_audit_file+0x2b1/0x310
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? aa_audit_file+0x2b1/0x310
  Sep 27 22:48:14 ubuntu-mantic kernel:  __aa_path_perm+0xaf/0x130
  Sep 27 22:48:14 ubuntu-mantic kernel:  aa_path_perm+0xf1/0x1c0
  Sep 27 22:48:14 ubuntu-mantic kernel:  apparmor_file_open+0x1bb/0x2e0
  Sep 27 22:48:14 ubuntu-mantic kernel:  security_file_open+0x2e/0x60
  Sep 27 22:48:14 ubuntu-mantic kernel:  do_dentry_open+0x10d/0x530
  Sep 27 22:48:14 ubuntu-mantic kernel:  vfs_open+0x33/0x50
  Sep 27 22:48:14 ubuntu-mantic kernel:  do_open+0x2ed/0x470
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? path_init+0x59/0x3d0
  Sep 27 22:48:14 ubuntu-mantic kernel:  path_openat+0x135/0x2d0
  Sep 27 22:48:14 ubuntu-mantic kernel:  ?

[Kernel-packages] [Bug 2040245] Re: apparmor oops when racing to retrieve a notification

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

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => John Johansen (jjohansen)

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

Title:
  apparmor oops when racing to retrieve a notification

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  When there is a race to receive a notification, the failing tasks 
  
  oopes when erroring   
  

  
  [  196.140988] BUG: kernel NULL pointer dereference, address: 
  
  [  196.140995] #PF: supervisor read access in kernel mode 
  
  [  196.140996] #PF: error_code(0x) - not-present page 
  
  [  196.140997] PGD 0 P4D 0
  
  [  196.140999] Oops:  [#1] PREEMPT SMP NOPTI  
  
  [  196.141001] CPU: 0 PID: 2316 Comm: aa-prompt Not tainted 6.5.0-9-generic 
#9-\
  Ubuntu
  
  [  196.141004] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 
1.15.0-\
  1 04/01/2014  
  
  [  196.141005] RIP: 0010:aa_listener_unotif_recv+0x11d/0x260  
  
  [  196.141011] Code: ff ff ff 8b 55 d0 48 8b 75 c8 4c 89 ef e8 6b db ff ff 49 
8\
  9 c2 48 85 c0 0f 88 c0 00 00 00 0f 84 25 ff ff ff 8b 05 3b 1c 1f 03 <49> 8b 
55 \
  00 83 e0 20 83 7a 08 07 74 66 85 c0 0f 85 01 01 00 00 48  
  
  [  196.141012] RSP: 0018:a2674075fdd8 EFLAGS: 00010246
  
  [  196.141014] RAX:  RBX: 974507a08404 RCX: 
000\
  0 
  
  [  196.141017] RDX:  RSI:  RDI: 
000\
  0 
  
  [  196.141017] RBP: a2674075fe10 R08:  R09: 
000\
  0 
  
  [  196.141018] R10: fffe R11:  R12: 
974507a0840\
  0 
  
  [  196.141019] R13:  R14: 974507a08430 R15: 
97451de00a0\
  0 
  
  [  196.141020] FS:  7f4ab6b30740() GS:97486fa0() 
knlGS:\
    
  
  [  196.141022] CS:  0010 DS:  ES:  CR0: 80050033  
  
  [  196.141024] CR2:  CR3: 000104cf2003 CR4: 
00770ef\
  0 
  
  [  196.141026] PKRU: 5554 
  
  [  196.141027] Call Trace:
  
  [  196.141032]  
  
  [  196.141034]  ? show_regs+0x6d/0x80 
  
  [  196.141041]  ? __die+0x24/0x80 
  
  [  196.141043]  ? page_fault_oops+0x99/0x1b0  
  
  [  196.141047]  ? do_user_addr_fault+0x316/0x6b0  
  
  [  196.141048]  ? filemap_map_pages+0x2b3/0x460   
  
  [  196.141056]  ? exc_page_fault+0x83/0x1b0   
  
  [  196.141068]  ? asm_exc_page_fault+0x27/0x30
  
  [  196.141079]  ? aa_listener_unotif_recv+0x11d/0x260 
  
  [  196.141081]  ? aa_listener_unotif_recv+0x184/0x260 
  
  [  196.141083]  listener_ioctl+0x1e1/0x260
  
  [  196.141088]  __x64_sys_ioctl+0xa0/0xf0 
  
  [  196.141092]  do_syscall_64+0x59/0x90   
  
  [  196.141094]  ? do_user_addr_fault+0x238/0x6b0  
  
  [  196.141095]  ? exit_to_user_mode_prepare+0x30/0xb0 
  
  [  196.141100]  ? irqentry_exit_to_user_mode+0x17/0x20
  
  [  196.141104]  ? irqentry_exit+0x43/0x50 
  
  [  196.141106]  ? exc_page_fault+0x94/0x1b0   
  
  [  196.141107]

[Kernel-packages] [Bug 2040194] Re: apparmor restricts read access of user namespace mediation sysctls to root

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

** Changed in: linux (Ubuntu Mantic)
   Status: Incomplete => Fix Committed

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => John Johansen (jjohansen)

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

Title:
  apparmor restricts read access of user namespace mediation sysctls to
  root

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  lxc and lxd currently need to determine if the apparmor restriction   
  
  on unprivileged user namespaces are being enforced, so that apparmor  
  
  restrictions won't break lxc/d, and they won't clutter the logs   
  
  by doing something like   
  

  
unshare true
  

  
  to test if the restrictions are being enforced.   
  

  
  Ideally access to this information would be restricted so that any
  
  unknown access would be logged, but lxc/d currently aren't ready for  
  
  this so in order to _not_ force lxc/d to probe whether enforcement is 
  
  enabled, open up read access to the sysctls for unprivileged user 
  
  namespace mediation.  
  
   
  https://github.com/canonical/lxd/issues/11920#issuecomment-1756110109

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040194/+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 2040284] Re: Focal update: v5.4.257 upstream stable release

2023-10-27 Thread Stefan Bader

Skipped "netfilter: xt_u32: validate user space input" as it is already applied 
as CVE-2023-39192.
Skipped "netfilter: xt_sctp: validate the flag_info count" as it is already 
applied as CVE-2023-39193.
Skipped "igb: set max size RX buffer when store bad packet is enabled" as it is 
already applied as CVE-2023-45871.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-39192

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-39193

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-45871

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

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

Title:
  Focal update: v5.4.257 upstream stable release

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

Bug description:
  SRU Justification

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

     v5.4.257 upstream stable release
     from git://git.kernel.org/

  erofs: ensure that the post-EOF tails are all zeroed
  ARM: pxa: remove use of symbol_get()
  mmc: au1xmmc: force non-modular build and remove symbol_get usage
  net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index
  rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff
  modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules
  UBUNTU: SAUCE: Revert "modules: only allow symbol_get of EXPORT_SYMBOL_GPL 
modules"
  USB: serial: option: add Quectel EM05G variant (0x030e)
  USB: serial: option: add FOXCONN T99W368/T99W373 product
  HID: wacom: remove the battery when the EKR is off
  staging: rtl8712: fix race condition
  Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race 
condition
  serial: sc16is7xx: fix bug when first setting GPIO direction
  firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe
  fsi: master-ast-cf: Add MODULE_FIRMWARE macro
  nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers()
  nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
  pinctrl: amd: Don't show `Invalid config param` errors
  9p: virtio: make sure 'offs' is initialized in zc_request
  ASoC: da7219: Flush pending AAD IRQ when suspending
  ASoC: da7219: Check for failure reading AAD IRQ events
  ethernet: atheros: fix return value check in atl1c_tso_csum()
  vxlan: generalize vxlan_parse_gpe_hdr and remove unused args
  m68k: Fix invalid .section syntax
  s390/dasd: use correct number of retries for ERP requests
  s390/dasd: fix hanging device after request requeue
  fs/nls: make load_nls() take a const parameter
  ASoc: codecs: ES8316: Fix DMIC config
  ASoC: atmel: Fix the 8K sample parameter in I2SC master
  platform/x86: intel: hid: Always call BTNL ACPI method
  platform/x86: huawei-wmi: Silence ambient light sensor
  security: keys: perform capable check only on privileged operations
  clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
  net: usb: qmi_wwan: add Quectel EM05GV2
  idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
  scsi: qedi: Fix potential deadlock on _percpu->p_work_lock
  netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
  bnx2x: fix page fault following EEH recovery
  sctp: handle invalid error codes without calling BUG()
  cifs: add a warning when the in-flight count goes negative
  scsi: storvsc: Always set no_report_opcodes
  ALSA: seq: oss: Fix racy open/close of MIDI devices
  platform/mellanox: Fix mlxbf-tmfifo not handling all virtio CONSOLE 
notifications
  powerpc/32s: Fix assembler warning about r0
  udf: Check consistency of Space Bitmap Descriptor
  udf: Handle error when adding extent to a file
  Revert "net: macsec: preserve ingress frame ordering"
  reiserfs: Check the return value from __getblk()
  eventfd: Export eventfd_ctx_do_read()
  eventfd: prevent underflow for eventfd semaphores
  new helper: lookup_positive_unlocked()
  fs: Fix error checking for d_hash_and_lookup()
  tmpfs: verify {g,u}id mount options correctly
  OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd()
  x86/asm: Make more symbols local
  x86/boot: Annotate local functions
  x86/decompressor: Don't rely on upper 32 bits of GPRs being preserved
  perf/imx_ddr: don't enable counter0 if none of 4 counters are used
  cpufreq: powernow-k8: Use related_cpus instead of cpus in driver.exit()
  bpf: Clear the probe_addr for uprobe
  tcp: tcp_enter_quickack_mode() should be static
  regmap: rbtree: Use alloc_flags for memory

[Kernel-packages] [Bug 2040250] Re: apparmor notification files verification

** Changed in: linux (Ubuntu Mantic)
   Status: Incomplete => Fix Committed

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

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => John Johansen (jjohansen)

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

Title:
  apparmor notification files verification

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  apparmor notifications on the 6.5 kernel are failing verification
  between the header size and the returned size.

  When strings are appended to the notification the header size should  
  
  be updated to reflect the correct size. While the size is also
  
  directly returned as part of delivering the notification, the header  
  
  should also be update to conform to specification and allow for   
  
  verification. 
  

  
  If verification is enabled and the notification contains appended 
  
  strings then notifications fail verification and won't be delivered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040250/+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 2041656] [NEW] Keybaord Keychron K3A1 buttons not registering

2023-10-27 Thread Petar Tahchiev

Public bug reported:

So I'm using Ubuntu Linux (Ubuntu 22.04.3 LTS) and I have external
keyboard Keychron K3A1. It's all been working fine for a few years until
some time ago, maybe a few months back, when after one of the overnight
ubuntu updates made the F5 and F6 keys to stop working.

Here's the output of showkey:

--
petar@xps~$ sudo showkey
kb mode was ?UNKNOWN?
[ if you are trying this under X, it might not work
since the X server is also reading /dev/console ]

press any key (program terminates 10s after last keypress)...
keycode  28 release
// HERE I PRESS F5 and F6 multiple times but nothing is registered
keycode  29 press
^Ccaught signal 2, cleaning up...
petar@xps~$ 
-

and same thing is with xev. Oddly enough - it is not a keyboard broken
key because Fn + F5 and Fn + F6 is working fine (dimming the keyboard
light and brightening the keyboard light).

And one more strange thing happened too. I have a key on my Keychron
keyboard that is supposed to take a screenshot. It was working fine, but
at the same time when the other problem started happening, this key
stopped working and in stead of getting a screenshot it now opens a new
terminal. I think somehow now it is mapped to Ctrl + Shift:

-
petar@xps~$ sudo showkey
kb mode was ?UNKNOWN?
[ if you are trying this under X, it might not work
since the X server is also reading /dev/console ]

press any key (program terminates 10s after last keypress)...
keycode  28 release
keycode  42 press //

[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

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

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

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

Title:
  SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  Bug description by Nils H.:

  
   Overview: 
  
  The following line in the SMC stats code (net/smc/smc_stats.h) caught my 
attention when using a payload of exactly 4096 bytes:

  #define SMC_STAT_PAYLOAD_SUB(_smc_stats, _tech, key, _len, _rc) \
  do { \
typeof(_smc_stats) stats = (_smc_stats); \
typeof(_tech) t = (_tech); \
typeof(_len) l = (_len); \
int _pos = fls64((l) >> 13); \
typeof(_rc) r = (_rc); \
int m = SMC_BUF_MAX - 1; \
this_cpu_inc((*stats).smc[t].key ## _cnt); \
if (r <= 0) \
break; \
_pos = (_pos < m) ? ((l == 1 << (_pos + 12)) ? _pos - 1 : _pos) : m; \  
<---
this_cpu_inc((*stats).smc[t].key ## _pd.buf[_pos]); \
this_cpu_add((*stats).smc[t].key ## _bytes, r); \
  } \
  while (0)

  
  With l = 4096, _pos evaluates to -1.

  
  Checking with the following uperf profile:
  # cat rr1c-4kx4k---1.xml 
  
  



 











  

  
  smcd stats output:
  # smcd -d stats reset
  SMC-D Connections Summary
Total connections handled 2
SMC connections   2 (client 2, server 0)
  v1  0
  v2  2
Handshake errors  0 (client 0, server 0)
Avg requests per SMC conn14.0
TCP fallback  0 (client 0, server 0)

  RX Stats
Data transmitted (Bytes)   5796 (5.796K)
Total requests9
Buffer full   0 (0.00%)
Buffer downgrades 0
Buffer reuses 0
  8KB16KB32KB64KB   128KB   256KB   512KB  >512KB
Bufs0   0   0   2   0   0   0   1
Reqs8   0   0   0   0   0   0   0

  TX Stats
Data transmitted (Bytes)   9960 (9.960K)
Total requests   19
Buffer full   0 (0.00%)
Buffer full (remote)  0 (0.00%)
Buffer too small  0 (0.00%)
Buffer too small (remote) 0 (0.00%)
Buffer downgrades 0
Buffer reuses 0
  8KB16KB32KB64KB   128KB   256KB   512KB  >512KB
Bufs0   2   0   0   0   0   0   0
Reqs   18   0   0   0   0   0   0   1

  Extras
Special socket calls  0
  cork0
  nodelay 0
  sendpage0
  splice  0
  urgent data 0

  
  Instead of including the payload in the wrong >512KB buckets, output should 
be to have 19 reqs in the 8KB buckets for TX stats and 9 reqs in the 8KB bucket 
for RX stats.


  
   Repro:
  
  0. Install uperf.
  1. Reset SMC-D stats on client and server.
  2. Start uperf at server side: "uperf -vs".
  3. Update profile with remote IP (server IP) and start uperf at client: 
"uperf -vai 5 -m rr1c-4kx4k---1.xml" (uperf profile, see above)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2039575/+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 2031412] Re: Support mipi camera on Intel Meteor Lake platform

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

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  New
Status in ivsc-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  New
Status in ivsc-driver source package in Jammy:
  New
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in ipu6-drivers source package in Mantic:
  New
Status in ivsc-driver source package in Mantic:
  New
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  == linux/linux-oem-6.5 ==

  [Impact]

  Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on
  MTL.

  [Fix]

  Two fixes in need. One, we need IOMMU passthrough for MTL platform.
  The other, fix is for handshake pin support for Lattice MIPI
  aggregator.

  The Intel IPU6 camera drivers are not yet all upstreamed yet. So far
  Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are
  in v6.6 already, and IPU6 ISYS is under upstream review. More components
  to come according to Intel.

  These two fixes are therefore for related components for not-yet fully
  upstreamed IPU6 as needed for out-of-tree dkms drivers.

  [Test Case]

  ```
  $ sudo dmesg | grep "Passthrough IOMMU for integrated Intel IPU"
  $ sudo dmesg | grep int3472
  # should have no "int3472-discrete INT3472:0c: GPIO type 0x12 unknown; the 
sensor may not work"
  ```

  [Where problems could occur]

  IOMMU Passthrough as necessary to enable IPU6 on Intel platforms, and
  it has been patching a few generations e.g. Bug 1989041 for Raptor
  Lake, Bug 1958004 for TGL and ADL. As IPU is not an external facing
  device which is not risky.

  For INT3472, the proposed patch might receive further updates per
  current upstream reviewers' opinions.

  [Other Info]

  Nominated for linux/mantic and oem-6.5/jammy as they're for MTL.

  == linux-firmware ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Firmware blobs from upstream ipu6-camera-bins repository.

  [Test Case]

  With firmware loaded correctly, there should be firmware version
  printed:

    intel-ipu6 intel-ipu: FW version: 20220510

  For camera functions, we'll need also updates in the ipu6-drivers, 
ivsc-drivers
  dkms as well.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic, so only Jammy/Mantic are nominated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2031412/+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 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

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

Title:
  [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  == SRU Justification ==
  The CONFIG_WWAN config is set to 'Y' for the generic and most derivative 
kernels.  This is affecting custom driver development for some partners.

  Change this config to be a loadable module and include it in linux-
  modules-*.

  Make this change to -generic kernels, so all derivatives will inherit
  it.

  
  == Fix ==
  UBUNTU: [Packaging] Make WWAN driver loadable modules

  
  == Regression Potential ==
  Medium.  This change is only to WWAN, and is changing it to a loadable module 
and not removing it.

  == Test Case ==
  A test kernel was built with this patch and tested by a partner.  It was also 
compile and boot tested internally.  Testing will also be performed on a WWAN 
device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland

2023-10-27 Thread Pirouette Cacahuète

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

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

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy
  load in Wayland

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Committed
Status in linux source package in Mantic:
  Triaged
Status in mutter source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems,
  sometimes when the screen locks, sometimes when launching particular
  apps.

  [ Workaround ]

  Add this to /etc/environment:

    MUTTER_DEBUG_KMS_THREAD_TYPE=user

  and then reboot.

  [ Test Plan ]

  Not all Ryzen systems (including one I just purchased) are able to
  reproduce the bug. We have no choice but to leave final verification
  to the community. Anyone affected should try locking their screen and
  verify they are not instantly returned to the login screen.

  [ Where problems could occur ]

  Anywhere in frame scheduling and particularly for mouse cursor
  movement since that's what the real-time thread exists to optimize.

  [ Original Description ]

  I have this issue on Ubuntu 23.10. Lock screen works only with an external 
monitor connected. Otherwise the session is ended and the user is logged out 
and brought to the gdm screen.
  All works in xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 22:32:22 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-03 (3 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2034619/+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 2039561] Re: mlxbf_pmc: Replace sauce patches with upstream commits

2023-10-27 Thread Shravan Kumar Ramani

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

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

Title:
  mlxbf_pmc: Replace sauce patches with upstream commits

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

Bug description:
  SRU Justification:

  [Impact]
  The mlxbf_pmc BlueField platform driver in the Jammy repo
  consists of some SAUCE patches. These need to be replaced.

  [Fix]
  The fix is to revert the four SAUCE patches, replacing them with
  upstream commits for the same functionality. 2 patches are from
  upstream linux, while the 3rd is from linux-next.

  [Test Case]
  * Boot BF2/BF3 platform, verify no new errors
  * Test sysfs interface exposed by driver for programming various
  counters and events.

  [Regression Potential]
  The upstream commits are not exactly the same as the SAUCE patches,
  so technically there is a chance of regression, but its been
  well-tested and the functionality is the same.

  [Other]
  n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2039561/+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 2018128] Re: Apport does not collect all logs when the package is HWE kernel

2023-10-27 Thread Benjamin Drung

I discussed this topic with Simon and we came up with a less fragile
solution:

Each kernel binary package can ship a symlink to
/usr/share/apport/package-hooks/source_linux.py. Example: linux-
image-5.19.0-50-generic should ship /usr/share/apport/package-
hooks/linux-image-5.19.0-50-generic.py -> source_linux.py

This will work without a regular expression that will break sooner or
later.

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

Title:
  Apport does not collect all logs when the package is HWE kernel

Status in apport package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 22.04 LTS with kernel 5.19.0-41-generic

  When filing bugs against the package 'linux' apport collects all the logs 
needed
  to the kernel

  But in case the user is not on stock kernel anymore and has the HWE kernel
  apport only imports 2 logs Dependencies.txt + ProcCpuInfoMinimal.txt

  and forwards the package 'linux' towards linux-signed-hwe-5.19 (in my
  case)

  would it be possible to make apport collect all the logs needed in all
  kernel cases?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.4
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 29 05:25:30 2023
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Re: [Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

2023-10-27 Thread Jean-Marie Tschanz

Thank you Ender,

Yes I have kernel 6.5.9 ready. But the instructions reads:

"then unzip the downloaded kernel and *enter it *as root"

I don't understand this instruction "enter it" .

On Fri, 27 Oct 2023 at 00:26, Endre Olah <2034...@bugs.launchpad.net>
wrote:

> Hi Jean-Marie,
>
> Download an d isntall Ubunte 22.04 LTS as suggested be Quinten, than
> follow his instructions: Download teh kernel 6.5.9 on kernel.org. And it
> seems to work. I can guarantee as I am just typing this on my laptop
> keyboard, which did nkt work before. So again Quinten's istructions are
> here:
>
> "I have kinda made progress in regards of being able to patch and
> install a kernel.
>
> First i'ill walk you through my assumptions,
>
> 1) you have the laptop and installed a debian/ubuntu based distro but the
> keyboard and touchpad don't work.
> 2) there is at least 64Gb of disk space available
> 3) you have the option of using the root user.
>
> so first off.
> Download the patch from above.
> https://bugzilla.kernel.org/attachment.cgi?id=305236
> run uname -r, this will return your kernel version, download the closest
> matching version to that version from kernel.org, but remeber only
> download later versions, so you are not using a version older than your
> current kernel.
>
> then run sudo apt install build-essential libncurses5-dev libssl-dev
> flex libelf-dev bc bison gcc make dwarves zstd
>
> then unzip the downloaded kernel and enter it as root.
> appply the patch by running the following as roon in the unzipped kernel
> directory: patch -p1 < path_to_patchfile
>
> it will return something notifying it's ready.
>
> then copy over the latest kernel config to the unzipped kernel this can
> be found in the /boot directory mine is /boot/config-6.1.59 for example.
> this is beceause i patched up the old kernel to this one. cp -r
> /boot/.conf .config replace latestkernel with the one you
> find in /boot
>
> then run make menuconfig as the root in the unzipped kernel.
> immediatly just hit save and exit
>
> run the following 2 lines as the root user in the unzipped kernel
> individually :) (been there done that)
>
> scripts/config --disable SYSTEM_TRUSTED_KEYS
> scripts/config --disable SYSTEM_REVOCATION_KEYS
>
> then run make -j 16
>
> and just hit enter whenever it prompts something, oh and get a coffee or
> a tea this is going to take a while :))
>
> when it completes, run as root in the unzipped kernel: make modules_install
> should'nt take too long
> whenever it completes run make install
> let it complete,
> congrats kernel installed,
> run; update-grub
> verify that the version of the kernel is somewhere in it's output.
>
> reboot, and pray.
> if it boots up, run a uname -r, try it with the laptop's builtin keyboard.
>
> if you've made it this far congrats.
> you have now patched and installed a kernel.
>
> above works on any distro i've tried. (zorin16 debian12 ubuntu2204)"
>
> Fully confirmed working on Ubuntu 22.04 LTS.
>
> Kind regards
>
>Endre
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2034477
>
> Title:
>   Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
>
> Status in ideapad-laptop:
>   New
> Status in libinput package in Ubuntu:
>   Confirmed
> Status in linux-signed-hwe-6.2 package in Ubuntu:
>   Confirmed
> Status in linux-signed-oem-6.5 package in Ubuntu:
>   Confirmed
> Status in Fedora:
>   New
>
> Bug description:
>   Hello.
>
>   Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
>   installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
>   laptop and it was noticed that keyboard, touchpad and microphone are
>   not working. The keyboard and touchpad work fine in BIOS setup and
>   till GRUB (command line). It was found that when external devices such
>   as keyboard, mouse and microphone are connected through USB and 3.5
>   jack, respectively, these work just fine. To confirm these are not
>   hardware problems, Microsoft Windows 11  (Home) was installed in
>   another disk partition and observed all these working alright. Hence a
>   bug is being reported to draw attention of the concerned team and I
>   request them to refer this issue and do the needful at the earliest.
>
>   Regards,
>   Pradip Kumar Das
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
>   ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
>   Uname: Linux 6.2.0-32-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu82.5
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Sep  6 08:04:42 2023
>   InstallationDate: Installed on 2023-08-14 (22 days ago)
>   InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64
> (20230223)
>   ProcEnviron:
>LANGUAGE=en_IN:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_IN
>SHELL=/bin/bash
>

[Kernel-packages] [Bug 2038539] Re: bluetooth connections are unstable with linux-image-6.5.0-6-generic and above (MANTIC)

2023-10-27 Thread Derk Willem te Bokkel

FYI a test install of fedora 39beta upgraded to latest
vmlinuz-6.5.9-300.fc39.x86_64 kernel has no bluetooth audio issues .. on
the same hardware .. different partions only..

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

Title:
  bluetooth connections are unstable with linux-image-6.5.0-6-generic
  and above (MANTIC)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Seems some random network activity regularly breaks bluetooth connections.. 
headphones connect and reconnect or suffer breaks in sound etc. 
  Started with this kernel version linux-image-6.5.0-7 .. previous kernel 
linux-image-6.5.0-5 works perfectly 
  Booting into the older kernel restores bluetooth stability.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-7-generic 6.5.0-7.7
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  derk   1690 F wireplumber
   /dev/snd/controlC0:  derk   1690 F wireplumber
   /dev/snd/seq:derk   1687 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Thu Oct  5 08:33:01 2023
  InstallationDate: Installed on 2023-10-04 (1 days ago)
  InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a 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.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: L9CN21WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76463 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Slim 5 16ABR8
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8:
  dmi.product.family: IdeaPad Slim 5 16ABR8
  dmi.product.name: 82XG
  dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8
  dmi.product.version: IdeaPad Slim 5 16ABR8
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  derk   1691 F wireplumber
   /dev/snd/controlC0:  derk   1691 F wireplumber
   /dev/snd/seq:derk   1688 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-10-04 (12 days ago)
  InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  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-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: L9CN21WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76463 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Slim 5 16ABR8
  dmi.ec.firmware.release: 1.21
  dmi.modalias:

[Kernel-packages] [Bug 2041613] [NEW] correct cephfs changes for uidmap support

Public bug reported:

correct cephfs changes for uidmap support

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

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

Title:
  correct cephfs changes for uidmap support

Status in linux package in Ubuntu:
  New

Bug description:
  correct cephfs changes for uidmap support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041613/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland

2023-10-27 Thread Pirouette Cacahuète

Enabled proposed repo on 23.10

```
$ $ sudo apt install -t mantic-proposed mutter  



Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait
Le paquet suivant a été installé automatiquement et n'est plus nécessaire :
  libjs-jquery-ui-theme-base
Veuillez utiliser « sudo apt autoremove » pour le supprimer.
Les paquets supplémentaires suivants seront installés :
  gir1.2-mutter-13 libmutter-13-0 mutter-common mutter-common-bin
Les NOUVEAUX paquets suivants seront installés :
  mutter
Les paquets suivants seront mis à jour :
  gir1.2-mutter-13 libmutter-13-0 mutter-common mutter-common-bin
4 mis à jour, 1 nouvellement installés, 0 à enlever et 26 non mis à jour.
Il est nécessaire de prendre 1 727 ko dans les archives.
Après cette opération, 205 ko d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer ? [O/n]
Réception de :1 http://fr.archive.ubuntu.com/ubuntu mantic-proposed/main amd64 
mutter-common all 45.0-3ubuntu3.1 [45,5 kB]
Réception de :2 http://fr.archive.ubuntu.com/ubuntu mantic-proposed/main amd64 
gir1.2-mutter-13 amd64 45.0-3ubuntu3.1 [130 kB]
Réception de :3 http://fr.archive.ubuntu.com/ubuntu mantic-proposed/main amd64 
libmutter-13-0 amd64 45.0-3ubuntu3.1 [1 391 kB]
Réception de :4 http://fr.archive.ubuntu.com/ubuntu mantic-proposed/main amd64 
mutter-common-bin amd64 45.0-3ubuntu3.1 [49,3 kB]
Réception de :5 http://fr.archive.ubuntu.com/ubuntu mantic-proposed/universe 
amd64 mutter amd64 45.0-3ubuntu3.1 [111 kB]
1 727 ko réceptionnés en 0s (7 132 ko/s)
(Lecture de la base de données... 313559 fichiers et répertoires déjà 
installés.)
Préparation du dépaquetage de .../mutter-common_45.0-3ubuntu3.1_all.deb ...
Dépaquetage de mutter-common (45.0-3ubuntu3.1) sur (45.0-3ubuntu3) ...
Préparation du dépaquetage de .../gir1.2-mutter-13_45.0-3ubuntu3.1_amd64.deb ...
Dépaquetage de gir1.2-mutter-13:amd64 (45.0-3ubuntu3.1) sur (45.0-3ubuntu3) ...
Préparation du dépaquetage de .../libmutter-13-0_45.0-3ubuntu3.1_amd64.deb ...
Dépaquetage de libmutter-13-0:amd64 (45.0-3ubuntu3.1) sur (45.0-3ubuntu3) ...
Préparation du dépaquetage de .../mutter-common-bin_45.0-3ubuntu3.1_amd64.deb 
...
Dépaquetage de mutter-common-bin (45.0-3ubuntu3.1) sur (45.0-3ubuntu3) ...
Sélection du paquet mutter précédemment désélectionné.
Préparation du dépaquetage de .../mutter_45.0-3ubuntu3.1_amd64.deb ...
Dépaquetage de mutter (45.0-3ubuntu3.1) ...
Paramétrage de mutter-common (45.0-3ubuntu3.1) ...
Paramétrage de mutter-common-bin (45.0-3ubuntu3.1) ...
Traitement des actions différées (« triggers ») pour libglib2.0-0:amd64 
(2.78.0-2) ...
Traitement des actions différées (« triggers ») pour libglib2.0-0:i386 
(2.78.0-2) ...
Traitement des actions différées (« triggers ») pour libc-bin (2.38-1ubuntu6) 
...
Traitement des actions différées (« triggers ») pour man-db (2.11.2-3) ...
Paramétrage de libmutter-13-0:amd64 (45.0-3ubuntu3.1) ...
Paramétrage de mutter (45.0-3ubuntu3.1) ...
update-alternatives: utilisation de « /usr/bin/mutter » pour fournir « 
/usr/bin/x-window-manager » (x-window-manager) en mode automatique
Paramétrage de gir1.2-mutter-13:amd64 (45.0-3ubuntu3.1) ...
Traitement des actions différées (« triggers ») pour libc-bin (2.38-1ubuntu6) 
...
```

Closed GNOME session, reopened it, unplugged from dock, force lock
screen, and I cannot reproduce the problem anymore.

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

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy
  load in Wayland

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Committed
Status in linux source package in Mantic:
  Triaged
Status in mutter source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems,
  sometimes when the screen locks, sometimes when launching particular
  apps.

  [ Workaround ]

  Add this to /etc/environment:

    MUTTER_DEBUG_KMS_THREAD_TYPE=user

  and then reboot.

  [ Test Plan ]

  Not all Ryzen systems (including one I just purchased) are able to
  reproduce the bug. We have no choice but to leave final verification
  to the community. Anyone affected should try locking their screen and
  verify they are not instantly returned to the login screen.

  [ Where problems could occur ]

  Anywhere in frame scheduling and particularly for mouse cursor
  movement since that's what the real-time thread exists to optimize.

  [ Original

[Kernel-packages] [Bug 2041558] [NEW] failed to load firmware renesas_usb_fw.mem

2023-10-27 Thread Zhanglei Mao

Public bug reported:

the log show below: 
xhci_hcd :27:00.0: failed to load firmware renesas_usb_fw.mem, fallback to 
ROM

>From this below, it seems just need to add renesas_usb_fw.mem into the
initrd.

https://bbs.archlinux.org/viewtopic.php?pid=1922549#p1922549

When the firmware is required and is not present,  kernel message: Direct 
firmware load for renesas_usb_fw.mem failed with error
When the firmware is required and is an empty file,  kernel message: FW has 
invalid version,  followed by the above message.

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

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

Title:
  failed to load firmware renesas_usb_fw.mem

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

Bug description:
  the log show below: 
  xhci_hcd :27:00.0: failed to load firmware renesas_usb_fw.mem, fallback 
to ROM

  From this below, it seems just need to add renesas_usb_fw.mem into the
  initrd.

  https://bbs.archlinux.org/viewtopic.php?pid=1922549#p1922549

  When the firmware is required and is not present,  kernel message: Direct 
firmware load for renesas_usb_fw.mem failed with error
  When the firmware is required and is an empty file,  kernel message: FW has 
invalid version,  followed by the above message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2041558/+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 2039144] Re: [X13s] Set unique wifi mac address

2023-10-27 Thread Juerg Haefliger

** Changed in: ubuntu-concept
   Status: New => Invalid

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

Title:
  [X13s] Set unique wifi mac address

Status in ubuntu-concept:
  Invalid
Status in linux-meta-laptop package in Ubuntu:
  New

Bug description:
  Currently, the wifi NIC comes up with a random MAC address which
  causes issues in some environments (routers sending out 'new device
  added' messages after every reboot).

  Instead, set a unique MAC address at boot and let network manager
  handle MAC randomization if that is desired.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-concept/+bug/2039144/+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 2041219] Re: GUI Freezes Randomly

Please see new bug report for Gnome Shell #2041521

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

Title:
  GUI Freezes Randomly

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2038263] Re: Add SoF topology support on Intel RaptorLake DELL SKU 0C11

2023-10-27 Thread Chris Chiu

** Tags removed: verification-needed-jammy-linux-oem-6.1
** Tags added: verification-done-jammy-linux-oem-6.1

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

Title:
  Add SoF topology support on Intel RaptorLake DELL SKU 0C11

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in firmware-sof source package in Lunar:
  Won't Fix
Status in linux source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in firmware-sof source package in Mantic:
  New
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  SRU Jusitification for firmware-sof

  [Impact]
  To support audio functions on RPL Dell SKU 0C11, it requires the topology 
file from sof-tplg-v2.2.7

  [Fix]
  Pull the sof-rpl-rt711-l0-rt1316-l12.tplg from 
https://github.com/thesofproject/sof-bin/releases/tag/v2023.09

  [Test Case]
  Install the fixes on the target platform(RPL Dell SKU 0C11) and verify the 
audio function.
  1. Install the firmware-sof on platform(RPL) Dell SKU 0C11
  2. Make sure the audio output/input devices are not dummy in audio settings.

  [Where problems could occur]
  New firmware is only for the RPL platforms which requires the specific 
topology file.

  [Misc]
  https://github.com/thesofproject/sof-bin/releases/tag/v2023.09

  

  [Impact]
  Audio play/capture are not functional on specific Dell machines of Intel RPL 
platforms

  [Fix]
  Backport the fix from Intel in https://github.com/thesofproject/linux

  [Test Case]
  1. Power on the machine and open the audio settings
  2. Verify it's not `Dummy` shown on the Audio output/input option

  [Where problems could occur]
  Only affect specific Intel RPL platforms. The risk of regression is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2038263/+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 2041219] Re: GUI Freezes Randomly

2023-10-27 Thread Juerg Haefliger

Not seeing any kernel issues in the log but gnome-shell stack traces:

Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: Object 
.Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x557967942990), has been already 
disposed — impossible to get any property from it. This might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: Object 
.Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x557967942990), has been already 
disposed — impossible to get any property from it. This might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: == Stack trace for 
context 0x5579631c7180 ==
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #0   7ffdfcf6b3f0 b   
resource:///org/gnome/shell/ui/workspacesView.js:639 (61fcff5c1a0 @ 33)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #1   7ffdfcf6b540 b   
resource:///org/gnome/shell/ui/workspacesView.js:686 (61fcff5c240 @ 488)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #2   7ffdfcf6cfe0 b   
resource:///org/gnome/shell/ui/workspace.js:855 (61fcff08510 @ 370)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #3   7ffdfcf6d700 b   
resource:///org/gnome/shell/ui/workspace.js:806 (61fcff08470 @ 17)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #4   5579632ca070 i   
resource:///org/gnome/shell/ui/workspacesView.js:1016 (61fcff5cc40 @ 124)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #5   5579632c9fe0 i   
resource:///org/gnome/shell/ui/overviewControls.js:715 (2744d0ebcd80 @ 39)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #6   5579632c9f58 i   
resource:///org/gnome/shell/ui/layout.js:347 (133181930510 @ 22)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #7   5579632c9ec8 i   
resource:///org/gnome/shell/ui/overview.js:641 (2744d0ebabf0 @ 175)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #8   5579632c9e48 i   
resource:///org/gnome/shell/ui/overview.js:624 (2744d0ebaba0 @ 12)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #9   5579632c9dc8 i   
resource:///org/gnome/shell/ui/overviewControls.js:757 (2744d0ebcf60 @ 55)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #10   7ffdfcf73460 b   
resource:///org/gnome/shell/ui/environment.js:151 (1331819cc4c0 @ 39)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #11   7ffdfcf73520 b   
resource:///org/gnome/shell/ui/environment.js:317 (1331819cc9c0 @ 14)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: == Stack trace for 
context 0x5579631c7180 ==
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #0   7ffdfcf6b540 b   
resource:///org/gnome/shell/ui/workspacesView.js:688 (61fcff5c240 @ 505)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #1   7ffdfcf6cfe0 b   
resource:///org/gnome/shell/ui/workspace.js:855 (61fcff08510 @ 370)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #2   7ffdfcf6d700 b   
resource:///org/gnome/shell/ui/workspace.js:806 (61fcff08470 @ 17)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #3   5579632ca070 i   
resource:///org/gnome/shell/ui/workspacesView.js:1016 (61fcff5cc40 @ 124)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #4   5579632c9fe0 i   
resource:///org/gnome/shell/ui/overviewControls.js:715 (2744d0ebcd80 @ 39)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #5   5579632c9f58 i   
resource:///org/gnome/shell/ui/layout.js:347 (133181930510 @ 22)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #6   5579632c9ec8 i   
resource:///org/gnome/shell/ui/overview.js:641 (2744d0ebabf0 @ 175)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #7   5579632c9e48 i   
resource:///org/gnome/shell/ui/overview.js:624 (2744d0ebaba0 @ 12)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #8   5579632c9dc8 i   
resource:///org/gnome/shell/ui/overviewControls.js:757 (2744d0ebcf60 @ 55)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #9   7ffdfcf73460 b   
resource:///org/gnome/shell/ui/environment.js:151 (1331819cc4c0 @ 39)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #10   7ffdfcf73520 b   
resource:///org/gnome/shell/ui/environment.js:317 (1331819cc9c0 @ 14)
Oct 26 10:32:45 darian-W94-95-97JU gnome-shell[2648]: Object St.Button 
(0x5579632bdff0), has been already disposed — impossible to get any property 
from it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
Oct 26 10:32:45 darian-W94-95-97JU gnome-shell[2648]: Object St.Label 
(0x557968471c40), has been already disposed — impossible to get any property 
from it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
Oct 26 10:32:45 darian-W94-95-97JU gnome-shell[2648]: == Stack trace for 
context

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

apport information

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

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

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

Title:
  GUI Freezes Randomly

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2041219] RfKill.txt

apport information

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

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

Title:
  GUI Freezes Randomly

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2041219] WifiSyslog.txt

apport information

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

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

Title:
  GUI Freezes Randomly

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2041219] UdevDb.txt

apport information

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

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

Title:
  GUI Freezes Randomly

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2041219] ProcInterrupts.txt

apport information

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

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

Title:
  GUI Freezes Randomly

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2041219] PulseList.txt

apport information

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

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

Title:
  GUI Freezes Randomly

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2041219] ProcEnviron.txt

apport information

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

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

Title:
  GUI Freezes Randomly

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2041219] ProcModules.txt

apport information

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

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

Title:
  GUI Freezes Randomly

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2041219] ProcCpuinfoMinimal.txt

apport information

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

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

Title:
  GUI Freezes Randomly

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2041219] ProcCpuinfo.txt

apport information

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

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

Title:
  GUI Freezes Randomly

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2041219] PaInfo.txt

apport information

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

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

Title:
  GUI Freezes Randomly

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2041219] Lspci.txt

apport information

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

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

Title:
  GUI Freezes Randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

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

apport information

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

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

Title:
  GUI Freezes Randomly

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2041219] Lsusb-t.txt

apport information

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

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

Title:
  GUI Freezes Randomly

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2041219] Lsusb.txt

apport information

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

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

Title:
  GUI Freezes Randomly

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2041219] Lspci-vt.txt

apport information

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

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

Title:
  GUI Freezes Randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

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

apport information

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

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

Title:
  GUI Freezes Randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  So everything would be working normally and then all of a sudden the
  laptop would freeze and nothing works.

  There's nothing in /var/crash.

  This has been run:

  cd ~/.local/share/gnome-shell/

  rm -rf extensions

  output of journalctl -b-1 > prevboot.txt is attached
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darian 2556 F pulseaudio
   /dev/snd/pcmC0D0p:   darian 2556 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-21 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: PC Specialist Limited W94_95_97JU
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-35-generic N/A
   linux-backports-modules-6.2.0-35-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.21
  Tags:  jammy
  Uname: Linux 6.2.0-35-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/21/2015
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W94_95_97JU
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: W94_95_97JU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

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