[Kernel-packages] [Bug 1690085]

[seowork.ssnutracare]

Hello

https://ssnutracare.com/product/derma-depot-ayurvedic-hair-oil-100-natural-ingredients-like-amla-kalonji-kadi-patta-prevents-hair-fall-grey-hair/
https://glowoxygluta.com/glow-oxygluta-kumkumadi-tailam/

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

[Kernel-packages] [Bug 2044334] Re: Unable to put CPU back online on AWS x1e.xlarge instance with kernel 6.2+

[Po-Hsu Lin]

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

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

Title:
  Unable to put CPU back online on AWS x1e.xlarge instance with kernel
  6.2+

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Issue found on AWS x1e.xlarge instance with:
  * M-aws 6.5.0-1011.11
  * L-aws 6.2.0-1007.7 
  * J-aws-6.5.0-1008.8~22.04.1
  * J-aws-6.2.0-1005.5~22.04.1 

  J-aws-5.15 looks OK. And I can't see this failure on other instances
  in our pool.

  CPU can be offlined but you won't be able to put it back online.

  There are 4 CPUs on this instance.
  $ uname -a
  Linux ip-172-31-2-102 6.5.0-1011-aws #11~22.04.1-Ubuntu SMP Mon Nov 20 
18:38:58 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  $ grep CONFIG_HOTPLUG_CPU /boot/config-6.5.0-1011-aws 
  CONFIG_HOTPLUG_CPU=y
  $ cat /sys/devices/system/cpu/cpu3/online
  1
  $ echo 0| sudo tee /sys/devices/system/cpu/cpu3/online
  0
  $ echo 1| sudo tee /sys/devices/system/cpu/cpu3/online
  1
  tee: /sys/devices/system/cpu/cpu3/online: Input/output error

  Output from 
  # Offline cpu3 - OK
  Nov 23 06:21:06 ip-172-31-2-102 kernel: [ 1124.449748] smpboot: CPU 3 is now 
offline
  # Online cpu3 - Failed
  Nov 23 06:21:14 ip-172-31-2-102 kernel: [ 1132.310197] installing Xen timer 
for CPU 3
  Nov 23 06:21:14 ip-172-31-2-102 kernel: [ 1132.310424] smpboot: Booting Node 
0 Processor 3 APIC 0x3
  Nov 23 06:21:24 ip-172-31-2-102 kernel: [ 1142.312481] CPU3 failed to report 
alive state

  This is affecting the ubuntu_kernel_selftests/cpu-hotplug:cpu-on-off-
  test.sh and ubuntu_ltp/cpuhotplug:cpuhotplug02, cpuhotplug03,
  cpuhotplug04, cpuhotplug06

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2044334/+subscriptions


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

[Kernel-packages] [Bug 2036737] Re: Enable dynamic boost control in ccp kernel driver

[Rex Tsai]

dynamic boost control is landed in upstream kernel 6.6, noble will have
such feature by default.

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

Title:
  Enable dynamic boost control in ccp kernel driver

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  We need to backport dynamic boost control into OEM-6.5 kernel. This
  request is to backport the ccp changes.

  Here are the commits necessary to backport to OEM-6.5 kernel from
  kernel 6.6:

  b58276372182 crypto: ccp - Rename macro for security attributes
  2e424c33d8e7 crypto: ccp - Add support for displaying PSP firmware versions
  e938b08ad8cd crypto: ccp - Add bootloader and TEE version offsets
  b8440d55f7d4 crypto: ccp - move setting PSP master to earlier in the init
  c04cf9e14f10 crypto: ccp - Add support for fetching a nonce for dynamic boost 
control
  d9408716d212 crypto: ccp - Add support for setting user ID for dynamic boost 
control
  e2cfe05e9277 crypto: ccp - Add support for getting and setting DBC parameters

  Here are the commits necessary to backport to OEM-6.5 kernel from
  kernel 6.7:

  53f7f779f45c crypto: ccp - Get a free page to use while fetching
  initial nonce

  [Test case]

  WIP

  [Regression potential]

  WIP

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


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

[Kernel-packages] [Bug 2044330] [NEW] Update soundwire topology files for Intel RPL platforms

[Chris Chiu]

Public bug reported:

[Impact]
Old RPL soundwire topology files are found to be muted when doing audio capture 
on left channel.

[Fix]

The commit from https://github.com/thesofproject/sof-bin/ is required.
* 
https://github.com/thesofproject/sof-bin/commit/0abfe1a0aebec57bde94c5cfb9b21d6726bd804d
 (Update v2.2.8 topology files for Intel RPL platforms)


[Test Case]

Test audio functions on Dell MayaBay RTL platforms.

[Where problems could occur]
Most topology files for Intel RPL are updated. Need more confirmation on Intel 
RPL platforms.

** Affects: firmware-sof (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: firmware-sof (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: firmware-sof (Ubuntu Mantic)
 Importance: Undecided
 Status: New

** Also affects: firmware-sof (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: firmware-sof (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

Title:
  Update soundwire topology files for Intel RPL platforms

Status in firmware-sof package in Ubuntu:
  New
Status in firmware-sof source package in Jammy:
  New
Status in firmware-sof source package in Mantic:
  New

Bug description:
  [Impact]
  Old RPL soundwire topology files are found to be muted when doing audio 
capture on left channel.

  [Fix]

  The commit from https://github.com/thesofproject/sof-bin/ is required.
  * 
https://github.com/thesofproject/sof-bin/commit/0abfe1a0aebec57bde94c5cfb9b21d6726bd804d
 (Update v2.2.8 topology files for Intel RPL platforms)

  
  [Test Case]

  Test audio functions on Dell MayaBay RTL platforms.

  [Where problems could occur]
  Most topology files for Intel RPL are updated. Need more confirmation on 
Intel RPL platforms.

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


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

[Kernel-packages] [Bug 2044027] Re: [Toshiba Satellite C855D-11X] keyboard, mouse and black screen after rebooting on ubuntu os only

[Daniel van Vugt]

Since this is probably a kernel issue and you can't officially increase
the kernel version any further on this older Ubuntu release, I suggest
trying a newer Ubuntu release like 22.04.3:

  https://ubuntu.com/download/desktop

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

Title:
  [Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
  rebooting on ubuntu os only

Status in linux package in Ubuntu:
  New

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")

  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
  the following video can prove my problem  on ubuntu   
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem 843 F pulseaudio
   /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
   /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
   /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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


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

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar and jammy

[Kevin Yeh]

@smb @kaihengfeng
I also found this regression on 5.4.0-168-generic

Following is the journal log.
Nov 22 20:22:56 dell-inspiron-5480-c26321 kernel: usb 2-2: device descriptor 
read/8, error -71
Nov 22 20:22:56 dell-inspiron-5480-c26321 kernel: usb 2-2: new SuperSpeed Gen 1 
USB device number 7 using xhci_hcd
Nov 22 20:22:56 dell-inspiron-5480-c26321 kernel: usb 2-2: device descriptor 
read/8, error -71
Nov 22 20:22:56 dell-inspiron-5480-c26321 kernel: usb usb2-port2: attempt power 
cycle
Nov 22 20:22:56 dell-inspiron-5480-c26321 kernel: usb 2-2: new SuperSpeed Gen 1 
USB device number 8 using xhci_hcd

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

** No longer affects: focal (Ubuntu)

** No longer affects: focal (Ubuntu Jammy)

** No longer affects: focal (Ubuntu Lunar)

** Also affects: linux (Ubuntu Focal)
   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/2043197

Title:
  USB bus error after upgrading to proposed kernel on lunar and jammy

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  New
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  == SRU Justification ==
  [Impact]
  USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel.

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

  [Test]
  With the patch applied, SuperSpeed devices can be enumerated across
  several reboots.

  [Where problems could occur]
  The switch case for Wireless USB (not USB WiFi dongle) was removed by
  the fix. I am not aware of the existence of any Wireless USB device. But
  if they do exist, this patch may the packet size encoding on them.

  == Original Bug Report ==
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6.2.0-38-generic and linux-
  image-5.15.0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   

[Kernel-packages] [Bug 2019153] Re: ntfs3 kernel driver corrupts volume during file move operations

[Andreas Kromke]

Anscheinend. Mein Fehlerbericht ist mehr als sechs Monate alt, hat
tierisch viel Arbeit gemacht und interessiert kein einziges Exemplar der
Gattung porcus. Es geht ja auch nur um Datenverlust, da gibt es viel
größere Probleme. Geradezu lächerlich.

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

Title:
  ntfs3 kernel driver corrupts volume during file move operations

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dual boot system Windows 10 / Ubuntu.
  Shared magnetic disk drive (4 TB), mounted via "ntfs3".

  Windows fast boot is deactivated to avoid corruption while Windows is
  hibernating.

  I had no problems with Ubuntu 22.10. Then I installed Ubuntu 23.04,
  and soon the shared disk was corrupted (after some file move and
  rename operations via Nautilus file manager). I do not know if Ubuntu
  22.10 also used "ntfs3" or the old "fuse" mechanism.

  Windows could not repair the drive (-> chkdsk-Protokoll-1.txt), and I
  had to reboot Windows.

  On the next start Windows repaired the drive (-> chkdsk-
  Protokoll-2.txt).

  Then I started Ubuntu, moved some more files, and the drive was again
  corrupted.

  Finally I started Windows again, and it repaired the drive without
  further reboots (-> chkdsk-Protokoll-3.txt).

  I did not dare to start Ubuntu again.

  PS: Obviously this dangerous malfunction is not new, and the same
  symptoms were described before. I found these witnesses via internet
  search:

  https://forums.gentoo.org/viewtopic-p-8746048.html

  https://randthoughts.github.io/i-tried-paragons-ntfs3-and-it-didnt-go-
  well/

  
https://www.reddit.com/r/archlinux/comments/13ona5u/ntfs3_driver_keeps_corrupting_ntfs_filesystem_on/
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  and2082 F wireplumber
   /dev/snd/controlC1:  and2082 F wireplumber
   /dev/snd/seq:and2078 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2022-11-29 (175 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   virbr0no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7D25
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=b8ec5967-60c8-454b-911f-b973bfd36212 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-01 (22 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/14/2022
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.92
  dmi.board.asset.tag: Default string
  dmi.board.name: PRO Z690-A DDR4(MS-7D25)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.92:bd10/14/2022:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-ADDR4(MS-7D25):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D25
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Kernel-packages] [Bug 2019153] Re: ntfs3 kernel driver corrupts volume during file move operations

[Thomas Pohl]

Maybe related: https://bugs.launchpad.net/bugs/2043924

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

Title:
  ntfs3 kernel driver corrupts volume during file move operations

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dual boot system Windows 10 / Ubuntu.
  Shared magnetic disk drive (4 TB), mounted via "ntfs3".

  Windows fast boot is deactivated to avoid corruption while Windows is
  hibernating.

  I had no problems with Ubuntu 22.10. Then I installed Ubuntu 23.04,
  and soon the shared disk was corrupted (after some file move and
  rename operations via Nautilus file manager). I do not know if Ubuntu
  22.10 also used "ntfs3" or the old "fuse" mechanism.

  Windows could not repair the drive (-> chkdsk-Protokoll-1.txt), and I
  had to reboot Windows.

  On the next start Windows repaired the drive (-> chkdsk-
  Protokoll-2.txt).

  Then I started Ubuntu, moved some more files, and the drive was again
  corrupted.

  Finally I started Windows again, and it repaired the drive without
  further reboots (-> chkdsk-Protokoll-3.txt).

  I did not dare to start Ubuntu again.

  PS: Obviously this dangerous malfunction is not new, and the same
  symptoms were described before. I found these witnesses via internet
  search:

  https://forums.gentoo.org/viewtopic-p-8746048.html

  https://randthoughts.github.io/i-tried-paragons-ntfs3-and-it-didnt-go-
  well/

  
https://www.reddit.com/r/archlinux/comments/13ona5u/ntfs3_driver_keeps_corrupting_ntfs_filesystem_on/
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  and2082 F wireplumber
   /dev/snd/controlC1:  and2082 F wireplumber
   /dev/snd/seq:and2078 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2022-11-29 (175 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   virbr0no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7D25
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=b8ec5967-60c8-454b-911f-b973bfd36212 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-01 (22 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/14/2022
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.92
  dmi.board.asset.tag: Default string
  dmi.board.name: PRO Z690-A DDR4(MS-7D25)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.92:bd10/14/2022:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-ADDR4(MS-7D25):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D25
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Kernel-packages] [Bug 2044139] Re: Kernel image 6.5 (web-)midi problems

[Launchpad Bug Tracker]

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

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

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

Title:
  Kernel image 6.5 (web-)midi problems

Status in linux-signed-lowlatency package in Ubuntu:
  Confirmed

Bug description:
  After the update to mantis, I have a problem with (at least - i have
  not yet researched further issues) Web-Midi applications running in
  the browser.

  Up to Kernel 6.2 it works just fine (also when downgrading the kernel
  to 6.2 in mantis)to use https://app.electra.one/
  http://components.novationmusic.com/ with a web midi enabled browser
  (must be google chrome installed by deb or chromium installed from
  their nightly builds or via nixos - because the snap version doesn't
  properly allow web midi for some reason that I still need to
  investigate further).

  When using any 6.5 or later kernel as included in mantis, or also when
  building my own from kernel.org, the devices I want to be managed with
  are basically identified, but no further actions are possible.

  This is 100% reproducible, switching back and forth between 6.5+ and 6.2 
kernels is very clearly showing the old version always works easily, but the 
newer version doesn't.
  Also a 6.6.1 mainlne kernel from kernel.org still has the issue.

  I have fiddled with this quite some hours, I suspected it has something to to 
with the midi 2.0 change in kernel 6.5 and tried turning it off with module 
parameters, but also when disabled or compiled a kernel without midi 2.0 
support the problem, persists. 
  The same with the latest 6.6.1 kernel.

  I have not found any error output in dmesg or journalctl that seems to
  be related to the problem so far, and also no other way to try to
  trigger the problem but the above described web midi thing.

  All tests have been done with the ubuntu kernel config - and the
  mainline configs created with make oldconfig.

  So I might additionally test the default mainline configuration, and
  also later mainline versions like 6.6.2 and try to identify other
  erratic behaviours in midi usage (of controllers etc) and add
  information about it... also I did not yet try the normal "generic"
  kernels, just

  Also I found this thing right now:

  https://forum.cockos.com/showthread.php?t=283086

  at the end it says there has been a bug in the kernel in the midi
  code.

  But I'm not sure if that is the same issue. For one I have not seen similar 
error messages in my system, but mainly this post says the bug is fixed in 
6.5.6  https://lwn.net/Articles/946853/ - and I have tested 6.5.11 mainline 
form kernel.org with the problem still persisting. 
  It might be there is some more wrong with the 6.5+ kernels in the midi area.

  
  if there are any further tests or logs needed or helpful, please let me know.

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


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

[Kernel-packages] [Bug 1916314] Re: HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until ~30-60 seconds after boot

[Joel Newman]

As of 2023 I can not get this module to work; if I understand correctly
it seems like changes to how DKMS/modpost works have made it so that
this now fails to build. I still have this issue and it is extremely
annoying. Is anyone working on this at all?

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

Title:
  HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until
  ~30-60 seconds after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is
  inoperable for ~30-60 seconds after system boot.

  Kernel logging reveals that it did not detect the keyboard during this
  time.

  An analysis of this and a patch can be found at:

  https://www.spinics.net/lists/linux-input/msg71677.html

  
  A workaround is to add i8042.nopnp to the kernel command line
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maxb   1195 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2021-02-03 (23 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: HP HP Spectre x360 Convertible 14-ea0xxx
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-44-generic N/A
   linux-backports-modules-5.8.0-44-generic  N/A
   linux-firmware1.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-44-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: 01/13/2021
  dmi.bios.release: 15.9
  dmi.bios.vendor: AMI
  dmi.bios.version: F.09
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 87F7
  dmi.board.vendor: HP
  dmi.board.version: 40.43
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 40.43
  dmi.modalias: 
dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx
  dmi.product.sku: 2G2C7EA#ABU
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-6.2/6.2.0.1018.18~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-azure-6.2 
(6.2.0.1018.18~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

linux-azure-6.2/6.2.0-1018.18~22.04.1 (arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

Re: [Kernel-packages] [Bug 2044153] Re: package linux-headers-6.2.0-37-generic 6.2.0-37.38~22.04.1 failed to install/upgrade: installed linux-headers-6.2.0-37-generic package post-installation script

[nelsinchi]

Hi Juerg, good day,

The problem was caused via the following package. The package was not 
regenerating the kernel module with the upgrade. So, my remediation was 
to remove it from my installation:

intel-i915-dkms

I had had recently the same error with this particular package. After I 
removed it, the upgrade went just fine.

Thanks for your support.


Kind regards,

Nelson Fonseca


On 11/22/23 02:40, Juerg Haefliger wrote:
> You have a broken DKMS installation that prevents kernel header package
> installation.
>
> ** 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-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2044153

Title:
  package linux-headers-6.2.0-37-generic 6.2.0-37.38~22.04.1 failed to
  install/upgrade: installed linux-headers-6.2.0-37-generic package
  post-installation script subprocess returned error exit status 1

Status in linux-hwe-6.2 package in Ubuntu:
  Invalid

Bug description:
  Setting up linux-headers-6.2.0-37-generic (6.2.0-37.38~22.04.1) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-37-generic
  Error! Could not locate dkms.conf file.
  File: /var/lib/dkms/intel-i915-dkms.bak/1.23.7.17.230608.24/source/dkms.conf 
does not exist.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4
  dpkg: error processing package linux-headers-6.2.0-37-generic (--configure):
   installed linux-headers-6.2.0-37-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of 
linux-headers-generic-hwe-22.04:
   linux-headers-generic-hwe-22.04 depends on linux-headers-6.2.0-37-generic; 
however:
Package linux-headers-6.2.0-37-generic is not configured yet.

  dpkg: error processing package linux-headers-generic-hwe-22.04 (--configure):
   dependency problems - leaving unconfigured
  Setting up linux-image-generic-hwe-22.04 (6.2.0.37.38~22.04.15) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

dpkg: dependency problems prevent configuration of 
linux-generic-hwe-22.04:
   linux-generic-hwe-22.04 depends on linux-headers-generic-hwe-22.04 (= 
6.2.0.37.38~22.04.15); however:
Package linux-headers-generic-hwe-22.04 is not configured yet.

  dpkg: error processing package linux-generic-hwe-22.04 (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for hicolor-icon-theme (0.17-2) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

Processing triggers for gnome-menus 
(3.36.0-1ubuntu3) ...
  Processing triggers for libc-bin (2.35-0ubuntu3.4) ...
  Processing triggers for man-db (2.10.2-1) ...
  Processing triggers for dbus (1.12.20-2ubuntu4.1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for desktop-file-utils (0.26-1ubuntu3) ...
  Processing triggers for linux-image-6.2.0-37-generic (6.2.0-37.38~22.04.1) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-37-generic
  Error! Could not locate dkms.conf file.
  File: /var/lib/dkms/intel-i915-dkms.bak/1.23.7.17.230608.24/source/dkms.conf 
does not exist.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 4
  dpkg: error processing package linux-image-6.2.0-37-generic (--configure):
   installed linux-image-6.2.0-37-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-headers-6.2.0-37-generic
   linux-headers-generic-hwe-22.04
   linux-generic-hwe-22.04
   linux-image-6.2.0-37-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-headers-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Nov 21 11:04:17 2023
  ErrorMessage: installed linux-headers-6.2.0-37-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-10-28 (23 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, 

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[Andreas Hasenack]

The src:ivsc-driver package produces bin:intel-vsc-dkms

The src:ipu6-drivers package produces bin:intel-ipu6-dkms

We need the test case to use these binary dkms packages from mantic-
proposed (once they get accepted). These are the packages being proposed
for the SRU, so they are the ones that have to be used for the test, not
packages from a ppa. I understand these dkms packages replace the linux-
modules-{ipu6,ivsc}-oem ones from the ppa?

As you said, the ppa is for ease/convenience, but we need to test the
dkms packages that this update is providing, even if that means an extra
step for users (install dkms, wait for build).

Can you change your testing instructions to use the dkms packages
produced by this SRU, and the current mantic kernel from proposed
(6.5.0-14.14)?

-- 
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:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
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:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
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:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  Incomplete
Status in ivsc-driver source package in Mantic:
  Incomplete
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
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [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 and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform. Need both
  firmware and driver change to probe the hardware correctly.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == 

[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device

[Athos Ribeiro]

Hi Artur,

is this last patch the one for noble? The changelog entry still says
mantic there.

Do note that the mantic version will need to be adjusted as per the SRU
policy in item 4.1 in
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure.

Finally, once you are done, could you adjust the tasks for each series
in this launchpad bug as suggested by Paride? Thanks!

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

Title:
  ucm2: soundwire: add rt713 SDCA device

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

Bug description:
  [ Impact ]
  Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack 
Codec-ALC713.
  Without correct configurations in userspace above codecs cannot be used. Thus 
in Settings > Sound > Output test doesn't produce sounds and Input device is 
greyed out.

  [ Fix ]
  Adding rt713 config files in ucm2 will allow to utilize those codecs.
  Upstream commit added support: 
https://github.com/alsa-project/alsa-ucm-conf/pull/363

  [ Test Plan ]
  Device with the soundwire card

  $ cat /proc/asound/cards
   0 [sofsoundwire   ]: sof-soundwire - sof-soundwire
    Intel Soundwire SOF

  Before fix:

  1. $ alsactl init
  alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration 
file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf
  alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file 
/usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2
  alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use 
case configuration -2
  Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" 
"HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 
mic:rt713-dmic" "" ""
  Hardware is initialized using a generic method

  2. $ amixer contents
  ...
  numid=24,iface=MIXER,name='Headphone Switch'
    ; type=BOOLEAN,access=rw--,values=1
    : values=off
  ...
  numid=33,iface=MIXER,name='IEC958 Playback Switch'
    ; type=BOOLEAN,access=rw--,values=1
    : values=off

  After fix: after adding patch files

  1. $ alsactl init
  alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf 
/var/lib/alsa/card0.conf.d' failed (exit code 1)

  (note: assuming that failed to remove the empty directory is not a
  critical problem)

  2. $ amixer contents
  ...
  numid=24,iface=MIXER,name='Headphone Switch'
    ; type=BOOLEAN,access=rw--,values=1
    : values=on
  ...
  numid=33,iface=MIXER,name='IEC958 Playback Switch'
    ; type=BOOLEAN,access=rw--,values=1
    : values=on

  [Where problems could occur]

   * This change adds new hardware support.

   * The change only adds new hardware support,
     it will not affect other codec device.

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


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

[Kernel-packages] [Bug 2044165] Re: package linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-36-generic package pre-removal script subprocess ret

[MrSurly]

Actually, I was removing "old" kernels before rebooting, via CLI.  I
aborted that after it warned me.  Later, the "problem occured" GUI popup
appeared, which resulted in this report; I didn't connect the dots until
now.

It's probably safe to simply close this as "operator error".

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

Title:
  package linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 failed to
  install/upgrade: installed linux-image-6.2.0-36-generic package pre-
  removal script subprocess returned error exit status 1

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

Bug description:
  While updating my system, had a window pop up stating it was a bug,
  and sent me to this page.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Nov 21 09:05:42 2023
  ErrorMessage: installed linux-image-6.2.0-36-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2020-08-25 (1182 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.12, unpackaged
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: linux-signed-hwe-6.2
  Title: package linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 failed to 
install/upgrade: installed linux-image-6.2.0-36-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-12-15 (341 days ago)

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


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

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

[Ubuntu SRU Bot]

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

digimend-dkms/10-4 (amd64, arm64)
systemd/249.11-0ubuntu3.11 (arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2042039] Re: AUDIO POPPING After New Kernel install: 5.15.0-88.98

[JS]

Seems like it confirms that the issue is related to "snd_hda_intel"
driver or settings related to it in ALSA. All reports (here & Linux Mint
Forum) mention this - independent of computer brand - except one
(separate) post probably unrelated on Linux Mint Forum
(https://forums.linuxmint.com/viewtopic.php?t=407183).

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

Title:
  AUDIO POPPING After New Kernel install: 5.15.0-88.98

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  10.30.23 20:18

  RE: Linux Kernel 5.15.0-88.98

  ISSUE. BUG REPORT: New Kernel Makes Audio "POP".

  After upgrading to the New Kernel, whenever the audio is accessed, there is 
an annoying
  "popping sound", as if the channel is being turned on. This happens before 
any audio plays,
  sometimes after if the channel is shutting down. Audio output I am reporting 
is coming out
  of the 3.5mm TRRS speaker/mic jack to my headphones, etc.

  VERY ANNOYING, I rolled back to the previous kernel.

  I do have Pulse Audio installed, not sure if it might be an issue.
  Will report back if removal or reinstall fixes it.

  - Mic

  System:
Kernel: 5.15.0-87-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: 
Cinnamon 5.8.4
  tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.2 Victoria 
base: Ubuntu 22.04 jammy
  Machine:
Type: Laptop System: Acer product: Aspire E5-576G v: V1.47 serial: 

Mobo: KBL model: Ironman_SK v: V1.47 serial:  
UEFI-[Legacy]: Insyde
  v: 1.47 date: 09/06/2018
  Battery:
ID-1: BAT1 charge: 26.5 Wh (100.0%) condition: 26.5/62.2 Wh (42.7%) volts: 
12.7 min: 11.1
  model: PANASONIC AS16B5J serial:  status: Full
Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 
serial: 
  charge: 55% (should be ignored) status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M187 serial: 

  charge: 50% (should be ignored) status: N/A
  CPU:
Info: quad core model: Intel Core i5-8250U bits: 64 type: MT MCP arch: 
Coffee Lake rev: A cache:
  L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 1471 high: 3156 min/max: 400/3400 cores: 1: 2498 2: 1973 
3: 1000 4: 794
  5: 796 6: 3156 7: 799 8: 758 bogomips: 28800
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel UHD Graphics 620 vendor: Acer Incorporated ALI driver: i915 
v: kernel ports:
  active: DP-1 off: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:5917
Device-2: NVIDIA GP108M [GeForce MX150] vendor: Acer Incorporated ALI 
driver: nvidia
  v: 535.113.01 pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 01:00.0 chip-ID: 
10de:1d10
Device-3: Quanta HD WebCam type: USB driver: uvcvideo bus-ID: 1-7:6 
chip-ID: 0408:a030
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting,nvidia
  unloaded: fbdev,nouveau,vesa gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
Monitor-1: DP-1 model: ViewSonic VX2757 res: 1920x1080 dpi: 82 diag: 686mm 
(27")
OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 
23.0.4-0ubuntu1~22.04.1
  direct render: Yes
  Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
  v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71
Sound Server-1: ALSA v: k5.15.0-87-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
  Network:
Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi 
v: kernel pcie:
  speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:24fb
IF: wlp3s0 state: down mac: 
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: 
Acer Incorporated ALI
  driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 
04:00.1
  chip-ID: 10ec:8168
IF: enp4s0f1 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
Local Storage: total: 1.36 TiB used: 143.29 GiB (10.3%)
ID-1: /dev/sda model: SD Ultra 3D 1TB size: 931.51 GiB speed: 6.0 Gb/s 
serial: 
ID-2: /dev/sdb vendor: Crucial model: CT500MX500SSD4 size: 465.76 GiB 
speed: 6.0 Gb/s
  serial: 
  Partition:
ID-1: / size: 915.32 GiB used: 143.28 GiB (15.7%) fs: ext4 dev: /dev/sda3
ID-2: /boot/efi size: 512 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda2
  Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: 
/swapfile
  Sensors:
System Temperatures: cpu: 48.0 C pch: 37.0 C mobo: N/A
Fan Speeds (RPM): N/A
  Repos:
Packages: 3240 apt: 3217 flatpak: 23
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/audio-recorder-ppa-jammy.list
  1: deb [signed-by=/etc/apt/keyrings/audio-recorder-ppa-jammy.gpg] https: 

[Kernel-packages] [Bug 2041000] Re: [X13s] Bluetooth not enabled

[Juerg Haefliger]

** Summary changed:

- [X13s] Bluetoothtooth not enabled
+ [X13s] Bluetooth not enabled

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

Title:
  [X13s] Bluetooth not enabled

Status in ubuntu-concept:
  Invalid
Status in linux-meta-laptop package in Ubuntu:
  Invalid
Status in linux-meta-laptop source package in Mantic:
  Fix Committed

Bug description:
  [Summary]
  Bluetooth cannot be turned.

  [Steps to reproduce]
  1. Go to `Settings` > `Bluetooth`
  2. Turn it on

  [Expected result]
  Turn on successfully.

  [Actual result]
  Cannot be turned on.

  [Failure rate]
  5/5

  [Additional information]
  CID: 202308-31941
  SKU: Lenovo X13s Gen 1
  system-manufacturer: LENOVO
  system-product-name: 21BYZ9SNUS
  bios-version: N3HET86W (1.58 )
  CPU: 
  GPU: 
  kernel-version: 6.5.0-1004-laptop

  [Stage]
  Issue reported and logs collected right after it happened

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-concept/+bug/2041000/+subscriptions


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

[Kernel-packages] [Bug 2041000] Re: [X13s] Bluetoothtooth not enabled

[Juerg Haefliger]

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

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

Title:
  [X13s] Bluetoothtooth not enabled

Status in ubuntu-concept:
  Invalid
Status in linux-meta-laptop package in Ubuntu:
  Invalid
Status in linux-meta-laptop source package in Mantic:
  Fix Committed

Bug description:
  [Summary]
  Bluetooth cannot be turned.

  [Steps to reproduce]
  1. Go to `Settings` > `Bluetooth`
  2. Turn it on

  [Expected result]
  Turn on successfully.

  [Actual result]
  Cannot be turned on.

  [Failure rate]
  5/5

  [Additional information]
  CID: 202308-31941
  SKU: Lenovo X13s Gen 1
  system-manufacturer: LENOVO
  system-product-name: 21BYZ9SNUS
  bios-version: N3HET86W (1.58 )
  CPU: 
  GPU: 
  kernel-version: 6.5.0-1004-laptop

  [Stage]
  Issue reported and logs collected right after it happened

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-concept/+bug/2041000/+subscriptions


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

[Kernel-packages] [Bug 2037534] Re: [X13s] Set unique bluetooth mac address

[Juerg Haefliger]

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

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

Title:
  [X13s] Set unique bluetooth mac address

Status in linux-meta-laptop package in Ubuntu:
  Invalid
Status in linux-meta-laptop source package in Mantic:
  Fix Committed

Bug description:
  On windows side MAC address for WLAN and Bluetooth are similar - like
  off by 4 from each other. I am guessing that a range of MACs is used
  per device (i.e. sequentially for wlan, sim cards, bluetooth).

  On linux side we do not currently have ability to find out the
  expected device MAC.

  Currently setting to static one is ok, but will not work when all of
  us are in Riga with all of our X13s devices.

  [Unit]
  Description=Set Bluetooth Address
  After=bluetooth.target
  Requires=bluetooth.target

  [Service]
  Type=simple
  ExecStartPre=/usr/bin/sleep 5
  ExecStart=/bin/bash -c "/usr/bin/yes | /usr/bin/btmgmt public-addr 
AD:5A:00:F0:FD:8C"

  [Install]
  WantedBy=multi-user.target

  Imho this should be impoved as follows:

  1) make this wantedby individual bluetooth device, not bluetooth.target
  2) make it bind to bluetooth device, such that it is stopped/started upon 
device poweroff/poweron (need to check if needed to set address every time)
  3) make it conditional on btmgmt to be available
  4) set or derive MAC from /etc/machine-id (maybe systemd should be able to do 
this for us?)
  5) use btmgmt --timeout option for interactive use
  6) Hopefully above will mean there is no need to do sleep 5 either

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


-- 
Mailing list: https://launchpad.net/~kernel-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

[Juerg Haefliger]

** Changed in: linux-meta-laptop (Ubuntu)
   Status: New => Fix Committed

-- 
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:
  Fix Committed

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 2041496] Re: btmgmt --index broken in Mantic

[Launchpad Bug Tracker]

This bug was fixed in the package bluez - 5.70-0ubuntu2

---
bluez (5.70-0ubuntu2) noble; urgency=medium

  * Fix btmgmt --index option (thanks to Juerg Haefliger) (LP: #2041496)

 -- Dimitri John Ledkov   Tue, 21 Nov 2023
11:08:37 +

** Changed in: bluez (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  btmgmt --index broken in Mantic

Status in Bluez Utilities:
  Unknown
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  On Mantic:

  $ btmgmt --index 1 info
  Unable to open 1: No such file or directory (2)
  Index list with 1 item
  hci0: Primary controller
   addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c
   supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy 
configuration static-addr phy-configuration
   current settings: powered ssp br/edr le secure-conn
   name rpi-5b-rev1d0-f88b
   short name
  hci0: Configuration options
   supported options: public-address
   missing options:

  Note the error 'Unable to open...' above.

  The machine has only a single hci so index 1 is invalid. The correct
  result should be:

  $ btmgmt --index 1 info
  Reading hci1 info failed with status 0x11 (Invalid Index)

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


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

[Kernel-packages] [Bug 2039368] Re: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3

[Eduardo-sanchez-mata]

Can confirm. Dell Latitude E5570 with AMD Radeon R7 GPU (Topaz XT)
running kernel 6.5.0-13-generic with libdrm-amdgpu1 2.4.115-1 in Xorg

Kernel UBSAN errors in amdgpu, apparently in
drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c

** Attachment added: "my dmesg with ubsan amdgpu traces"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039368/+attachment/5722326/+files/dmesg-ubsan-amdgpu.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/2039368

Title:
  UBSAN: array-index-out-of-bounds in
  /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since I upgraded from lunar to mantic I get a load of those errors (41
  on a fresh boot) in dmesg:

  ```
  [4.277343] UBSAN: array-index-out-of-bounds in 
/build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3
  [4.277728] index 4 is out of range for type 'btree_iter_set [4]'
  [4.277925] CPU: 7 PID: 247 Comm: kworker/7:1 Not tainted 6.5.0-9-generic 
#9-Ubuntu
  [4.278132] Hardware name: Default string Default string/Default string, 
BIOS WRX80SU8-F6 06/08/2023
  [4.278531] Workqueue: events register_cache_worker [bcache]
  [4.278754] Call Trace:
  [4.278949]  
  [4.279143]  dump_stack_lvl+0x48/0x70
  [4.279337]  dump_stack+0x10/0x20
  [4.279526]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [4.279721]  bch_btree_iter_push+0x4e6/0x4f0 [bcache]
  [4.279929]  bch_btree_node_read_done+0xcb/0x410 [bcache]
  [4.280142]  bch_btree_node_read+0xf8/0x1e0 [bcache]
  [4.280349]  ? __pfx_closure_sync_fn+0x10/0x10 [bcache]
  [4.280557]  bch_btree_node_get.part.0+0x15c/0x330 [bcache]
  [4.280764]  ? __bch_btree_ptr_invalid+0x66/0xe0 [bcache]
  [4.280975]  ? __pfx_up_write+0x10/0x10
  [4.281170]  bch_btree_node_get+0x16/0x30 [bcache]
  [4.281375]  run_cache_set+0x596/0x850 [bcache]
  [4.281578]  ? srso_return_thunk+0x5/0x10
  [4.281773]  register_cache_set+0x1a2/0x210 [bcache]
  [4.281984]  register_cache+0x11a/0x1a0 [bcache]
  [4.282187]  register_cache_worker+0x22/0x80 [bcache]
  [4.282387]  process_one_work+0x223/0x440
  [4.282573]  worker_thread+0x4d/0x3f0
  [4.282753]  ? srso_return_thunk+0x5/0x10
  [4.282931]  ? _raw_spin_lock_irqsave+0xe/0x20
  [4.283113]  ? __pfx_worker_thread+0x10/0x10
  [4.283286]  kthread+0xf2/0x120
  [4.283458]  ? __pfx_kthread+0x10/0x10
  [4.283631]  ret_from_fork+0x47/0x70
  [4.283800]  ? __pfx_kthread+0x10/0x10
  [4.283972]  ret_from_fork_asm+0x1b/0x30
  [4.284143]  
  ```

  This system has 4 bcache backing devices and 4 bcache cache devices,
  though they are not associated for now and caching is disabled. It was
  already like that when I upgraded, so the kernel only uses the backing
  code, not the caching one.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  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: unknown
  CurrentDesktop: GNOME
  Date: Sat Oct 14 23:16:33 2023
  HibernationDevice: RESUME=none
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB:
   0 amdgpudrmfb
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic 
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@ 
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1 
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1 
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
  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
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2023
  dmi.bios.release: 5.23
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: WRX80SU8-F6
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80SU8-F6:bd06/08/2023:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default 

Re: [Kernel-packages] [Bug 2044027] Re: [Toshiba Satellite C855D-11X] keyboard, mouse and black screen after rebooting on ubuntu os only

[samybarbond]

[image: Screenshot from 2023-11-22 17-28-41.png]this is an error on
launchpad when i want to send the video from the Add attachment or patch

link to add the file
this is the video
 VID_20231122_143704.mkv

video


On Wed, 22 Nov 2023 at 05:40, Daniel van Vugt <2044...@bugs.launchpad.net>
wrote:

> ** Summary changed:
>
> - keyboard , mouse and black screen after rebooting on ubuntu os only
> + [Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
> rebooting on ubuntu os only
>
> ** Changed in: linux (Ubuntu)
>Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2044027
>
> Title:
>   [Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
>   rebooting on ubuntu os only
>
> Status in linux package in Ubuntu:
>   New
>
> Bug description:
>   For input devices : gnome-shell
>For rebooting process : init system
>   the following is what appears on my screen when i login to gnome-shell
> desktop environment (ubuntu-desktop) the below message appears twice times
>   ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous
> error (AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
>   ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is
> beyond end of object (length 0xA) (20210331/exoparg2-393)
>   __common_interrupt: 1.55 No irq handler for vector")
>   At the start process  : both keyboard and mouse internal doesnot work
> with the issue above , at the end when performing a reboot process after
> rebooting my device it appears on my screen a black screen resulting to
> turning off from  the btn on my laptop. always this incident happens with
> me and only on ubuntu 16.04 and later systems  the problem occurs while on
> other oses the problem does not occur any more (rebooting  keyboard and
> mouse "internal")
>
>   note : secondary storage ,optical disks external devices like keyboard
> are working fine on ubuntu systems with all versions and all other os
> including windows os
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.11-0ubuntu27.27
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  oem 843 F pulseaudio
>/dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
>/dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
>/dev/snd/controlC0:  oem 843 F pulseaudio
>   CasperMD5CheckResult: skip
>   DistroRelease: Ubuntu 20.04
>   InstallationDate: Installed on 2023-11-20 (0 days ago)
>   InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64
> (20220223)
>   MachineType: TOSHIBA SATELLITE C855D-11X
>   Package: linux (not installed)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 radeondrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic
> root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
>   ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions:
>linux-restricted-modules-5.13.0-30-generic N/A
>linux-backports-modules-5.13.0-30-generic  N/A
>linux-firmware 1.187.39
>   Tags:  focal
>   Uname: Linux 5.13.0-30-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: N/A
>   _MarkForUpload: True
>   dmi.bios.date: 12/06/2012
>   dmi.bios.release: 6.30
>   dmi.bios.vendor: Insyde Corp.
>   dmi.bios.version: 6.30
>   dmi.board.asset.tag: Base Board Asset Tag
>   dmi.board.name: Pumori
>   dmi.board.vendor: AMD
>   dmi.board.version: Base Board Version
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: OEM Chassis Manufacturer
>   dmi.chassis.version: OEM Chassis Version
>   dmi.ec.firmware.release: 1.60
>   dmi.modalias:
> dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
>   dmi.product.family: Type1Family
>   dmi.product.name: SATELLITE C855D-11X
>   dmi.product.sku: PSKCYE-009002N5
>   dmi.product.version: PSKCYE-009002N5
>   dmi.sys.vendor: TOSHIBA
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044027/+subscriptions
>
>


** Attachment added: "Screenshot from 2023-11-22 17-28-41.png"
   
https://bugs.launchpad.net/bugs/2044027/+attachment/5722325/+files/Screenshot%20from%202023-11-22%2017-28-41.png

-- 
You received this bug notification because you are 

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws-6.5/6.5.0.1011.11~22.04.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-aws-6.5 
(6.5.0.1011.11~22.04.2) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

linux-aws-6.5/6.5.0-1011.11~22.04.1 (arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2038675] Re: mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet)

[Tim Gardner]

** Tags removed: verification-needed-lunar-linux-azure 
verification-needed-mantic-linux-azure
** Tags added: verification-done-lunar-linux-azure 
verification-done-mantic-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/2038675

Title:
  mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0
  Packet)

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

Bug description:
  SRU Justification

  [Impact]

  The Microsoft MANA network driver does not accurately report some
  statistics and does not correctly handle some error conditions.

  [Fix]

  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=b2b69a4c
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=7a54de926574
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=a43e8e9ffa0d

  [Test Plan]

  Microsoft tested.

  [Regression Potential]

  GSO packets may not be correctly reported. Some error conditions may
  cause incorrect statistics to be recorded, or flood the kernel log
  with error messages.

  [Other Info]

  SF: 00370665

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


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

[Kernel-packages] [Bug 2038837] Re: kernel: evict_inodes inode 000000006048f67c, i_count = 1, was skipped!

[Pivert]

Confirmed.

As you can see in the below details:
- Installed the linux-image-6.5.0-10008-tuxedo kernel on the morning then 
reboot, and immediately got those messages.
- Below are the details of the machine & disks.


root@tuxedo:~# ls -ltrh /boot/ | tail -n1
-rw-r--r-- 1 root  root   93M Nov 22 08:57 initrd.img-6.5.0-10008-tuxedo
root@tuxedo:~# journalctl -k --since '-1d' | rg evict_inodes | wc -l
6869
root@tuxedo:~# journalctl -k --since '-10d' | rg evict_inodes | wc -l
6869
root@tuxedo:~# journalctl -k --since '-1d' | rg evict_inodes | head -n1
Nov 22 08:59:39 tuxedo kernel: evict_inodes inode 289cf219, i_count = 
1, was skipped!
root@tuxedo:~# journalctl -k -n 20 --no-pager
Nov 22 14:28:42 tuxedo kernel: evict_inodes inode c14a1a03, i_count = 
1, was skipped!
Nov 22 14:28:42 tuxedo kernel: evict_inodes inode e0bfc1f6, i_count = 
1, was skipped!
Nov 22 14:28:42 tuxedo kernel: evict_inodes inode 77f3c1ed, i_count = 
1, was skipped!
Nov 22 14:28:42 tuxedo kernel: evict_inodes inode 19b8a253, i_count = 
1, was skipped!
Nov 22 14:28:42 tuxedo kernel: evict_inodes inode 97761c57, i_count = 
1, was skipped!
Nov 22 14:29:25 tuxedo kernel: evict_inodes inode a3e9205e, i_count = 
1, was skipped!
Nov 22 14:29:25 tuxedo kernel: evict_inodes inode 969f43be, i_count = 
1, was skipped!
Nov 22 14:29:25 tuxedo kernel: evict_inodes inode 47a3b3ed, i_count = 
1, was skipped!
Nov 22 14:29:25 tuxedo kernel: evict_inodes inode d9749e3d, i_count = 
1, was skipped!
Nov 22 14:29:25 tuxedo kernel: evict_inodes inode 152496a5, i_count = 
1, was skipped!
Nov 22 14:29:25 tuxedo kernel: evict_inodes inode af218771, i_count = 
1, was skipped!
Nov 22 14:29:25 tuxedo kernel: evict_inodes inode 6d0ee1b0, i_count = 
1, was skipped!
Nov 22 14:29:25 tuxedo kernel: evict_inodes inode 75d41850, i_count = 
1, was skipped!
Nov 22 14:29:25 tuxedo kernel: evict_inodes inode b6f3411f, i_count = 
1, was skipped!
Nov 22 14:29:25 tuxedo kernel: evict_inodes inode 9d8b31d4, i_count = 
1, was skipped!
Nov 22 14:29:25 tuxedo kernel: evict_inodes inode 72cd4997, i_count = 
1, was skipped!
Nov 22 14:29:25 tuxedo kernel: evict_inodes inode c10e15f0, i_count = 
1, was skipped!
Nov 22 14:29:25 tuxedo kernel: evict_inodes inode 31bfa671, i_count = 
1, was skipped!
Nov 22 14:29:25 tuxedo kernel: evict_inodes inode 5b07323e, i_count = 
1, was skipped!
Nov 22 14:29:25 tuxedo kernel: evict_inodes inode 710e1230, i_count = 
1, was skipped!
root@tuxedo:~# inxi -DMz
Machine:
  Type: Laptop System: TUXEDO product: TUXEDO InfinityBook Pro Gen7 (MK2)
v: Standard serial: 
  Mobo: NB02 model: PH6AG01_PH6AQ71_PH6AQI1 v: Standard serial: 
UEFI: American Megatrends LLC. v: N.1.08A08 date: 12/28/2022
Drives:
  Local Storage: total: 931.52 GiB used: 335.6 GiB (36.0%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 PRO 500GB
size: 465.76 GiB
  ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 980 PRO 500GB
size: 465.76 GiB

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

Title:
  kernel: evict_inodes inode 6048f67c, i_count = 1, was skipped!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This gets spammed after I shutdown, though the inode values are
  different for each line.  Had to phyically reboot to get it to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  yamiyuki   6735 F wireplumber
   /dev/snd/controlC0:  yamiyuki   6735 F wireplumber
   /dev/snd/controlC1:  yamiyuki   6735 F wireplumber
   /dev/snd/seq:yamiyuki   6731 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Mon Oct  9 11:32:47 2023
  InstallationDate: Installed on 2022-01-14 (634 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro 
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x 
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.5.0-9-generic
  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   

[Kernel-packages] [Bug 2037534] Re: [X13s] Set unique bluetooth mac address

[Juerg Haefliger]

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

** No longer affects: ubuntu-concept

** Project changed: systemd => ubuntu

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

** Also affects: Ubuntu Mantic
   Importance: Undecided
   Status: New

** No longer affects: Ubuntu Mantic

** No longer affects: ubuntu

** Changed in: linux-meta-laptop (Ubuntu)
   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/2037534

Title:
  [X13s] Set unique bluetooth mac address

Status in linux-meta-laptop package in Ubuntu:
  Invalid
Status in linux-meta-laptop source package in Mantic:
  New

Bug description:
  On windows side MAC address for WLAN and Bluetooth are similar - like
  off by 4 from each other. I am guessing that a range of MACs is used
  per device (i.e. sequentially for wlan, sim cards, bluetooth).

  On linux side we do not currently have ability to find out the
  expected device MAC.

  Currently setting to static one is ok, but will not work when all of
  us are in Riga with all of our X13s devices.

  [Unit]
  Description=Set Bluetooth Address
  After=bluetooth.target
  Requires=bluetooth.target

  [Service]
  Type=simple
  ExecStartPre=/usr/bin/sleep 5
  ExecStart=/bin/bash -c "/usr/bin/yes | /usr/bin/btmgmt public-addr 
AD:5A:00:F0:FD:8C"

  [Install]
  WantedBy=multi-user.target

  Imho this should be impoved as follows:

  1) make this wantedby individual bluetooth device, not bluetooth.target
  2) make it bind to bluetooth device, such that it is stopped/started upon 
device poweroff/poweron (need to check if needed to set address every time)
  3) make it conditional on btmgmt to be available
  4) set or derive MAC from /etc/machine-id (maybe systemd should be able to do 
this for us?)
  5) use btmgmt --timeout option for interactive use
  6) Hopefully above will mean there is no need to do sleep 5 either

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


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

[Kernel-packages] [Bug 2041000] Re: [X13s] Bluetoothtooth not enabled

[Juerg Haefliger]

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

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

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

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

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

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

Title:
  [X13s] Bluetoothtooth not enabled

Status in ubuntu-concept:
  Invalid
Status in linux-meta-laptop package in Ubuntu:
  Invalid
Status in linux-meta-laptop source package in Mantic:
  Confirmed

Bug description:
  [Summary]
  Bluetooth cannot be turned.

  [Steps to reproduce]
  1. Go to `Settings` > `Bluetooth`
  2. Turn it on

  [Expected result]
  Turn on successfully.

  [Actual result]
  Cannot be turned on.

  [Failure rate]
  5/5

  [Additional information]
  CID: 202308-31941
  SKU: Lenovo X13s Gen 1
  system-manufacturer: LENOVO
  system-product-name: 21BYZ9SNUS
  bios-version: N3HET86W (1.58 )
  CPU: 
  GPU: 
  kernel-version: 6.5.0-1004-laptop

  [Stage]
  Issue reported and logs collected right after it happened

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-concept/+bug/2041000/+subscriptions


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

[Kernel-packages] [Bug 2044027] Re: [Toshiba Satellite C855D-11X] keyboard, mouse and black screen after rebooting on ubuntu os only

[samybarbond]

** Description changed:

  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above , at the end when performing a reboot process after rebooting 
my device it appears on my screen a black screen resulting to turning off from  
the btn on my laptop. always this incident happens with me and only on ubuntu 
16.04 and later systems  the problem occurs while on other oses the problem 
does not occur any more (rebooting  keyboard and mouse "internal")
  
  note : secondary storage ,optical disks external devices like keyboard are 
working fine on ubuntu systems with all versions and all other os including 
windows os
- --- 
+ the following video can prove my problem  on ubuntu   
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  oem 843 F pulseaudio
-  /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
-  /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
-  /dev/snd/controlC0:  oem 843 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  oem 843 F pulseaudio
+  /dev/snd/pcmC1D0c:   oem 843 F...m pulseaudio
+  /dev/snd/pcmC1D0p:   oem 843 F...m pulseaudio
+  /dev/snd/controlC0:  oem 843 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2023-11-20 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: TOSHIBA SATELLITE C855D-11X
  Package: linux (not installed)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=ebe99476-bee4-4cb6-ba03-027e52714d6e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-5.13.0-30-generic N/A
-  linux-backports-modules-5.13.0-30-generic  N/A
-  linux-firmware 1.187.39
+  linux-restricted-modules-5.13.0-30-generic N/A
+  linux-backports-modules-5.13.0-30-generic  N/A
+  linux-firmware 1.187.39
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.release: 6.30
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Pumori
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.60
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:br6.30:efr1.60:svnTOSHIBA:pnSATELLITEC855D-11X:pvrPSKCYE-009002N5:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKCYE-009002N5:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855D-11X
  dmi.product.sku: PSKCYE-009002N5
  dmi.product.version: PSKCYE-009002N5
  dmi.sys.vendor: TOSHIBA

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

Title:
  [Toshiba Satellite C855D-11X] keyboard, mouse and black screen after
  rebooting on ubuntu os only

Status in linux package in Ubuntu:
  New

Bug description:
  For input devices : gnome-shell
   For rebooting process : init system
  the following is what appears on my screen when i login to gnome-shell 
desktop environment (ubuntu-desktop) the below message appears twice times
  ("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error 
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
  ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond 
end of object (length 0xA) (20210331/exoparg2-393)
  __common_interrupt: 1.55 No irq handler for vector")
  At the start process  : both keyboard and mouse internal doesnot work with 
the issue above 

[Kernel-packages] [Bug 1946303] Re: No video after wake from S3 due to Nvidia driver crash

[Mateusz Łącki]

I noticed that if I change driver to a *-server line, the suspend works
just like that. I have tested 525 and 535 server driver package.  In
non-server line of drivers the above issues exist in all drivers
installable through GUI 470, 535, and in the newest 545.29.02 as well.

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

Title:
  No video after wake from S3 due to Nvidia driver crash

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

Bug description:
  Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake 
from suspend. It does start running again, but there is no video output. I'm 
attaching text for two crashes from kernel log output. First is:
  /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 
nv_restore_user_channels+0xce/0xe0 [nvidia]
  Second is:
  /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 
nv_set_system_power_state+0x2c8/0x3d0 [nvidia]

  Apparently I'm not the only one having this problem with 470 drivers.
  https://forums.linuxmint.com/viewtopic.php?t=354445
  
https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150

  Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system-
  sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu
  21.04 and sleep was reliable then. Right now I'm going back to driver
  460.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: nvidia-driver-470 470.63.01-0ubuntu4
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct  6 23:24:02 2021
  SourcePackage: nvidia-graphics-drivers-470
  UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+subscriptions


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

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

[Juerg Haefliger]

We cannot fix that. We can't simply include binaries from and unknown
origin with unknown licensing. That's a legal time bomb waiting to
explode...

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

Title:
  failed to load firmware renesas_usb_fw.mem

Status in linux-firmware package in Ubuntu:
  Won't Fix
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid

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-firmware/+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 1786013] Autopkgtest regression report (linux-meta-lowlatency/6.5.0.14.14.12)

[Ubuntu SRU Bot]

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

linux-lowlatency/6.5.0-14.14.1 (amd64, arm64)
lxc/1:5.0.1-0ubuntu7 (amd64)
nvidia-graphics-drivers-525/525.147.05-0ubuntu0.23.10.1 (arm64)
systemd/253.5-1ubuntu6.1 (arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2042039] Re: AUDIO POPPING After New Kernel install: 5.15.0-88.98

[Thomas Lindner]

I can confirm this audio popping on two Asus PN50. One with Kernel 5.15.0-87 
the other with 6.2.0-36.
Rolling back to older kernel solved it on both machines.


System:
  Kernel: 6.2.0-35-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 
5.8.4 tk: GTK 3.24.33
wm: muffin dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 
jammy
Machine:
  Type: Mini-pc System: ASUSTeK product: MINIPC PN50 v: 0416 serial: 
  Mobo: ASUSTeK model: PN50 serial:  UEFI: ASUSTeK v: 0416 
date: 08/27/2020
CPU:
  Info: 6-core model: AMD Ryzen 5 4500U with Radeon Graphics bits: 64 type: MCP 
arch: Zen 2 rev: 1
cache: L1: 384 KiB L2: 3 MiB L3: 8 MiB
  Speed (MHz): avg: 1397 high: 1400 min/max: 1400/2375 boost: enabled cores: 1: 
1397 2: 1400
3: 1397 4: 1397 5: 1397 6: 1397 bogomips: 28446
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Renoir vendor: ASUSTeK driver: amdgpu v: kernel pcie: speed: 16 
GT/s lanes: 16
ports: active: HDMI-A-1 empty: DP-1,DP-2,DP-3 bus-ID: 05:00.0 chip-ID: 
1002:1636
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
unloaded: fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1680x1050 s-dpi: 96
  Monitor-1: HDMI-A-0 mapped: HDMI-A-1 model: NEC P221W res: 1680x1050 dpi: 90 
diag: 559mm (22")
  OpenGL: renderer: RENOIR (renoir LLVM 15.0.7 DRM 3.49 6.2.0-35-generic)
v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: 
kernel pcie:
speed: 16 GT/s lanes: 16 bus-ID: 05:00.1 chip-ID: 1002:1637
  Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A 
pcie: speed: 16 GT/s
lanes: 16 bus-ID: 05:00.5 chip-ID: 1022:15e2
  Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: 
kernel pcie:
speed: 16 GT/s lanes: 16 bus-ID: 05:00.6 chip-ID: 1022:15e3
  Sound Server-1: ALSA v: k6.2.0-35-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: 
ASUSTeK driver: r8169
v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: f400 bus-ID: 02:00.0 
chip-ID: 10ec:8168
  IF: enp2s0f0 state: up speed: 1000 Mbps duplex: full mac: 
  IF-ID-1: virbr0 state: down mac: 
Drives:
  Local Storage: total: 931.51 GiB used: 337.34 GiB (36.2%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB 
speed: 31.6 Gb/s
lanes: 4 serial:  temp: 39.9 C
Partition:
  ID-1: / size: 91.11 GiB used: 28.93 GiB (31.8%) fs: ext4 dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 92.5 MiB used: 6 MiB (6.5%) fs: vfat dev: /dev/nvme0n1p1
  ID-3: /home size: 824.06 GiB used: 308.4 GiB (37.4%) fs: ext4 dev: 
/dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: 
/swapfile
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 40.0 C
  Fan Speeds (RPM): N/A

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

Title:
  AUDIO POPPING After New Kernel install: 5.15.0-88.98

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  10.30.23 20:18

  RE: Linux Kernel 5.15.0-88.98

  ISSUE. BUG REPORT: New Kernel Makes Audio "POP".

  After upgrading to the New Kernel, whenever the audio is accessed, there is 
an annoying
  "popping sound", as if the channel is being turned on. This happens before 
any audio plays,
  sometimes after if the channel is shutting down. Audio output I am reporting 
is coming out
  of the 3.5mm TRRS speaker/mic jack to my headphones, etc.

  VERY ANNOYING, I rolled back to the previous kernel.

  I do have Pulse Audio installed, not sure if it might be an issue.
  Will report back if removal or reinstall fixes it.

  - Mic

  System:
Kernel: 5.15.0-87-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: 
Cinnamon 5.8.4
  tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.2 Victoria 
base: Ubuntu 22.04 jammy
  Machine:
Type: Laptop System: Acer product: Aspire E5-576G v: V1.47 serial: 

Mobo: KBL model: Ironman_SK v: V1.47 serial:  
UEFI-[Legacy]: Insyde
  v: 1.47 date: 09/06/2018
  Battery:
ID-1: BAT1 charge: 26.5 Wh (100.0%) condition: 26.5/62.2 Wh (42.7%) volts: 
12.7 min: 11.1
  model: PANASONIC AS16B5J serial:  status: Full
Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 
serial: 
  charge: 55% (should be ignored) status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M187 serial: 

  charge: 50% (should be ignored) status: N/A
  CPU:
Info: quad core model: Intel Core i5-8250U bits: 64 type: MT MCP arch: 
Coffee Lake rev: A cache:
  L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 1471 high: 3156 

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

[Ubuntu SRU Bot]

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

backport-iwlwifi-dkms/9858-0ubuntu3.3 (amd64)
digimend-dkms/10-4 (amd64)
oss4/4.2-build2010-5ubuntu9.1 (amd64)
rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu17~22.04.2 (amd64)
rtl8821ce/5.5.2.1-0ubuntu11~0.22.04.1 (amd64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[You-Sheng Yang]

Hi Andreas Hasenack, do you think I've addressed your concern at the
most extend? Please comment.

-- 
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:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
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:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
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:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  Incomplete
Status in ivsc-driver source package in Mantic:
  Incomplete
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
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [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 and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform. Need both
  firmware and driver change to probe the hardware correctly.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == 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 

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[You-Sheng Yang]

> Since this includes a new upstream code drop, could you summarize the
highlights?

For people are interested in some more readable git history, we have
https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/experimental-
dkms.

For a quick review here, there have been like a dozen engineering code
releases, and they're all one commit code dump without details. For what
we can tell, they cover:

1. camera sensor fixes/additions: hm2170, hm2172, gc5035, ov02e10, ov08a10, 
ov8856, etc.
2. fix build against new kernel releases, inclusive of gpio/V4L2 kernel API 
changes
3. gpio addition to int3472 for camera sensor controls
4. documentation changes
5. a few changes for the V4L2 interface to ensure a right device number could 
be chosen
6. support new hardware platform RPL-P, ADL-N, MTL-P
7. support additional V4L2 image format
8. drop test pattern generator
9. new Lattice MIPI aggregator

> Have you inspected them for backwards incompatible changes?

Yes, we tested all released, MIPI camera equipped platforms, TGL & ADL,
as commented in the SRU justification.

> Like my comment #24 above, is there a way to test this that does not
involve out-of-archive packages? If not, what is the benefit of this
update to mantic users?

The PPAs are for easy of verification. In reality you may simply install
the dkms or prebuilt linux-modules-{ipu6,ivsc,usbio}-generic packages.
General users still need that intel-ipu6 PPA, because it hosts userspace
HAL frameworks that are still being MIRed.

> That doesn't sound very reassuring :) Having said that, you think it's
ready for a stable release update for mantic users? Mantic users will
benefit from this update?

Yes, or they got nothing.

If they're to manually fix IPU6 cameras on their notebook, the same
things are mandatory to them, and the same things are only available to
them as these are what we can get from Intel.

-- 
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:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
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:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
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:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  Incomplete
Status in ivsc-driver source package in Mantic:
  Incomplete
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
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [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 and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform. Need both
  firmware and driver change to probe the hardware correctly.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, 

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

[Ubuntu SRU Bot]

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

r8168/8.048.00-1ubuntu0.20.04.2 (amd64)
systemd/245.4-4ubuntu3.22 (amd64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[You-Sheng Yang]

> The changes in ipu6-drivers are not adding a new firmware as far as I
can tell, could you please clarify?

linux-firmware changes have been released at version
20230919.git3672ccab-0ubuntu2 as shown in comment #5.

> Overall, after this update, what will be the status of MIPI cameras
for mantic users on intel meteor lake?

There are still some more different models under development, but Intel
MIPI IPU6 on Intel Meteor Lake with OV02E and serveral camera sensors we
have enabled before should be working.

-- 
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:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
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:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
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:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  Incomplete
Status in ivsc-driver source package in Mantic:
  Incomplete
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
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [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 and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform. Need both
  firmware and driver change to probe the hardware correctly.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == 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.

  

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[You-Sheng Yang]

> The patches added to the ivsc-driver package do not seem to be about a 
> missing firmware, like the impact section above claims:
> Please clarify.

Updated SRU justification in the description.

> Not sure what you mean with the above. I see the same fixes proposed
for mantic landed in noble, so that's good. Maybe the comment above was
written before the noble packages were updated?

This SRU justification was prepared before Noble is named/released, and
yet since Noble is out, we copy to both series.

** Description changed:

  [SRU Justification]
  
  == ipu6-driver ==
  
  [Impact]
  
  Missing Intel MIPI firmware for Meteor Lake platform.
  
  [Fix]
  
  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019, and
  an additional patch to enable/fix compilation of additional sensor
  modules.
  
  [Test Case]
  
  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.
  
  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.
  
  [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 and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.
  
  == ivsc-driver ==
  
  [Impact]
  
- Missing Intel MIPI firmware for Meteor Lake platform.
+ Missing Intel MIPI firmware for Meteor Lake platform. Need both firmware
+ and driver change to probe the hardware correctly.
  
  [Fix]
  
  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.
  
  [Test Case]
  
  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules. LJCA
  modules should be loaded automatically on MTL platforms as well.
  
  To actually verify the camera framework:
  ```
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6
  $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
  $ sudo apt install linux-oem-22.04d-exp
  $ sudo apt install linux-modules-ipu6-oem-22.04d-exp
  $ sudo apt install linux-modules-ivsc-oem-22.04d-exp
  $ sudo apt install linux-modules-usbio-oem-22.04d-exp
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  And then browse https://webcamtests.com/ for testing.
  
  [Where problems could occur]
  
  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.
  
  [Other Info]
  
  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.
  
  == 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 

[Kernel-packages] [Bug 2038263] Re: Add SoF topology support on Intel RaptorLake DELL SKU 0C11

[Stefan Bader]

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

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

-- 
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:
  Fix Released
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:
  Fix Committed
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
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:
  Fix Released
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 2044165] Re: package linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-36-generic package pre-removal script subprocess ret

[Juerg Haefliger]

Aborting removal of the running kernel
error processing package linux-image-6.2.0-36-generic (--remove):
installed linux-image-6.2.0-36-generic package pre-removal script subprocess 
returned error exit status 1
too many errors, stopping

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

Title:
  package linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 failed to
  install/upgrade: installed linux-image-6.2.0-36-generic package pre-
  removal script subprocess returned error exit status 1

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

Bug description:
  While updating my system, had a window pop up stating it was a bug,
  and sent me to this page.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Nov 21 09:05:42 2023
  ErrorMessage: installed linux-image-6.2.0-36-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2020-08-25 (1182 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.12, unpackaged
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: linux-signed-hwe-6.2
  Title: package linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 failed to 
install/upgrade: installed linux-image-6.2.0-36-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-12-15 (341 days ago)

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


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

[Kernel-packages] [Bug 2044165] Re: package linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-36-generic package pre-removal script subprocess ret

[Juerg Haefliger]

Hm. It wanted to remove the running kernel. Were you asked if you want
to do that?

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

Title:
  package linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 failed to
  install/upgrade: installed linux-image-6.2.0-36-generic package pre-
  removal script subprocess returned error exit status 1

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

Bug description:
  While updating my system, had a window pop up stating it was a bug,
  and sent me to this page.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Nov 21 09:05:42 2023
  ErrorMessage: installed linux-image-6.2.0-36-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2020-08-25 (1182 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.12, unpackaged
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: linux-signed-hwe-6.2
  Title: package linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 failed to 
install/upgrade: installed linux-image-6.2.0-36-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-12-15 (341 days ago)

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


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