[Kernel-packages] [Bug 2041495] Re: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0

2023-12-02 Thread Yuri Khan
I am a user of an SSD that identifies as HS-SSD-FUTURE 2048G, powered by
the MAXIO MAP1602 controller that is affected by the same zero CRTO bug.

I have installed linux-image-6.5.0-1009-oem (6.5.0-1009.10) and rebooted
a few times. Every boot, the SSD is initialized correctly.

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

Title:
  Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0:
  Device not ready: aborting installation, CSTS=0x0

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
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 Justification]

  BugLink: https://bugs.launchpad.net/bugs/2041495

  [Impact]

  NVME module left unready, therefore not recognized by the installation 
process, and/or after installation with following error messages:
  ```
  kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0
  kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A
  kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI
  kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, 
CSTS=0x0
  ```

  [Fix]

  Proposed fix in
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/nvme/host/core.c?h=v6.5=6cc834ba62998c65c42d0c63499bdd35067151ec
  "nvme: avoid bogus CRTO values", in Linus' tree v6.6 already, as well
  as stable kernels v6.1.55 and v6.5.5.

  [Test Case]

  Apply to kernel and boot with the nvme module installed. Now the device 
should be probed with success.
  ```
  kernel: [1.731760] nvme nvme0: pci function 1:e1:00.0
  kernel: [1.731778] pcieport 1:e0:06.0: can't derive routing for PCI 
INT A
  kernel: [1.731780] nvme 1:e1:00.0: PCI INT A: no GSI
  kernel: [1.731919] nvme nvme0: bad crto:0 cap:800203028033fff
  kernel: [1.735550] nvme nvme0: Shutdown timeout set to 10 seconds
  kernel: [1.753865] nvme nvme0: allocated 64 MiB host memory buffer.
  kernel: [1.794966] nvme nvme0: 16/0/0 default/read/poll queues
  kernel: [2.136735]  nvme0n1: p1 p2 p3
  ```

  [Where problems could occur]

  This patch tries to set an appropriate CRTO (Controller Ready
  Timeouts) that may be reported incorrectly by some devices. There
  should be little (a bit longer CRTO) to no effect on devices
  performing normally before hands.

  [Other Info]

  While this has been in Linus' tree, Mantic/Lunar/oem-6.5 and oem-6.1
  will be nominated.

  == original bug report ==

  NVME module left unready, therefore not recognized by the installation
  process, and/or after installation with following error messages:

  kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0
  kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A
  kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI
  kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, 
CSTS=0x0

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2041495/+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 2045382] Re: AMD Lexa PRO graphic card can't work

2023-12-02 Thread Mario Limonciello
try amdgpu.aspm=0.  If this helps it's because of missing stable
backport patches.

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

Title:
  AMD Lexa PRO graphic card can't work

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

Bug description:
  [Summary]

  When I racked the one dell device, and do the trail run, I found that
  the checkbox process is stuck when it got the graphic information. I
  want to debug with the monitor, plug the DP cable to AMD card. After
  doing the power cycle, it entered to the BIOS, observe through the
  screen that the kernel has been started, but it immediately turned
  into a black screen. Fortunately, it can ssh-able, it can work
  normally by using the onboard graphic card.

  After checking, AMD graphic card is broken after upgrading to
  5.15.0-89-generic, it still have same issue  in "5.15.0-91-generic"
  kernel version, but everything is good in the "5.15.0-88-generic"
  kernel version.

  [Information]

  Problematic DUT CID: 202101-28622
  Platform name: Caribou
  Launchpad Tag: fossa-cubone-rkl
  Project name: Optiplex 5090
  Used GM image: 
dell-bto-focal-fossa-release-X120-20210625-7_fossa-cubone-rkl_A02.iso
  GPU: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 
540/540X/550/550X / RX 540X/550/550X] [1002:699f]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-91.101~20.04.1-generic 5.15.131
  Uname: Linux 5.15.0-91-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Dec  1 14:39:55 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-release+X120
  InstallationDate: Installed on 2023-11-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2045382/+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 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build

2023-12-02 Thread Mike Ferreira
It blew 1fallen's machine out of the water.

Before doing anything, backup your bpool and rpool via rsync so you have
a fall back point.

Start a thread on UbuntuForums > Installations and Updates. I will talk
you through a work-around to uninstall zfs-dkms and everything else I
did to get around it. It's too long a process for this bug report, There
was lessons learned by both I and 1fallen, where both ours crashed and
we had to recover from that.

Like I said. Get good backups now, While it's still broken, but still
bootable.

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

Title:
  zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build
  kernel module.

  Genrated Crash report, but couldn't send it on it's own.

  Error it kept throwing was:
  >>>
  Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ...
  Loading new zfs-2.1.5 DKMS files...
  Building for 6.2.0-36-generic 6.2.0-37-generic
  Building initial module for 6.2.0-36-generic
  configure: error: 
*** None of the expected "iops->get_acl()" interfaces were detected.
*** This may be because your kernel version is newer than what is
*** supported, or you are using a patched custom kernel with
*** incompatible modifications.
***
*** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2
*** Compatible Kernels: 3.10 - 5.19

  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/zfs-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64)
  Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information.
  dpkg: error processing package zfs-dkms (--configure):
   installed zfs-dkms package post-installation script subprocess returned 
error exit status 10
  >>>

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2
  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 zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Nov 25 21:00:27 2023
  InstallationDate: Installed on 2021-09-23 (793 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+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 2008157] Re: [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot

2023-12-02 Thread Frantisek K.
Bug is still here...

Ubuntu 22.04 jammy

Broadcom MegaRAID 9580-8i8e

Linux version 6.2.0-37-generic (buildd@bos03-amd64-055) (x86_64-linux-
gnu-gcc-11 (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils
for Ubuntu) 2.38) #38~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov  2
18:01:13 UTC 2 (Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16)

...
[3.869311] megasas: 07.719.03.00-rc1
[3.869764] megaraid_sas :43:00.0: BAR:0x0  BAR's 
base_addr(phys):0x028080f0  mapped virt_addr:0x65c51147
[3.869770] megaraid_sas :43:00.0: FW now in Ready state
[3.869775] megaraid_sas :43:00.0: 63 bit DMA mask and 63 bit consistent 
mask
[3.869973] megaraid_sas :43:00.0: firmware supports msix: (128)
[3.872925] megaraid_sas :43:00.0: requested/available msix 72/72 
poll_queue 0
[3.872928] 

[3.872951] UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-6.2-I50pf3/linux-hwe-6.2-6.2.0/arch/x86/include/asm/topology.h:72:28
[3.872979] index -1 is out of range for type 'cpumask *[1024]'
[3.872995] CPU: 33 PID: 538 Comm: systemd-udevd Not tainted 
6.2.0-37-generic #38~22.04.1-Ubuntu
[3.872999] Hardware name: Supermicro Super Server/H12SSL-i, BIOS 2.5 
09/08/2022
[3.873001] Call Trace:
[3.873004]  
[3.873007]  dump_stack_lvl+0x48/0x70
[3.873015]  dump_stack+0x10/0x20
[3.873018]  __ubsan_handle_out_of_bounds+0xa2/0x100
[3.873024]  ? __pfx_default_calc_sets+0x10/0x10
[3.873030]  megasas_alloc_irq_vectors+0x215/0x220 [megaraid_sas]
[3.873043]  megasas_init_fw+0x617/0x1320 [megaraid_sas]
[3.873057]  megasas_probe_one+0x18d/0x5a0 [megaraid_sas]
[3.873069]  local_pci_probe+0x4b/0xb0
[3.873075]  pci_call_probe+0x55/0x190
[3.873080]  pci_device_probe+0x84/0x120
[3.873084]  ? srso_return_thunk+0x5/0x10
[3.873090]  really_probe+0x1ed/0x450
[3.873095]  __driver_probe_device+0x8a/0x190
[3.873099]  driver_probe_device+0x23/0xd0
[3.873102]  __driver_attach+0x10f/0x220
[3.873106]  ? __pfx___driver_attach+0x10/0x10
[3.873109]  bus_for_each_dev+0x83/0xe0
[3.873114]  driver_attach+0x1e/0x30
[3.873116]  bus_add_driver+0x152/0x250
[3.873119]  ? srso_return_thunk+0x5/0x10
[3.873124]  driver_register+0x83/0x160
[3.873127]  __pci_register_driver+0x68/0x80
[3.873131]  megasas_init+0xdb/0xff0 [megaraid_sas]
[3.873143]  ? __pfx_init_module+0x10/0x10 [megaraid_sas]
[3.873153]  do_one_initcall+0x49/0x240
[3.873159]  ? srso_return_thunk+0x5/0x10
[3.873162]  ? kmalloc_trace+0x2a/0xb0
[3.873168]  do_init_module+0x52/0x240
[3.873173]  load_module+0xb96/0xd60
[3.873177]  ? security_kernel_post_read_file+0x5c/0x80
[3.873183]  ? srso_return_thunk+0x5/0x10
[3.873186]  ? kernel_read_file+0x25c/0x2b0
[3.873194]  __do_sys_finit_module+0xcc/0x150
[3.873197]  ? srso_return_thunk+0x5/0x10
[3.873200]  ? __do_sys_finit_module+0xcc/0x150
[3.873209]  __x64_sys_finit_module+0x18/0x30
[3.873213]  do_syscall_64+0x5c/0x90
[3.873217]  ? srso_return_thunk+0x5/0x10
[3.873221]  ? syscall_exit_to_user_mode+0x38/0x60
[3.873225]  ? srso_return_thunk+0x5/0x10
[3.873229]  ? do_syscall_64+0x69/0x90
[3.873232]  ? syscall_exit_to_user_mode+0x38/0x60
[3.873235]  ? srso_return_thunk+0x5/0x10
[3.873239]  ? do_syscall_64+0x69/0x90
[3.873242]  ? srso_return_thunk+0x5/0x10
[3.873245]  ? irqentry_exit+0x43/0x50
[3.873249]  ? srso_return_thunk+0x5/0x10
[3.873252]  ? exc_page_fault+0x92/0x1b0
[3.873256]  entry_SYSCALL_64_after_hwframe+0x73/0xdd
[3.873260] RIP: 0033:0x7f0618b5da7d
[3.873264] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 83 a3 0f 00 f7 d8 64 89 01 48
[3.873266] RSP: 002b:7ffc9db735e8 EFLAGS: 0246 ORIG_RAX: 
0139
[3.873270] RAX: ffda RBX: 5615ff4f7740 RCX: 7f0618b5da7d
[3.873272] RDX:  RSI: 7f0618cf4441 RDI: 0005
[3.873274] RBP: 0002 R08:  R09: 7ffc9db73720
[3.873276] R10: 0005 R11: 0246 R12: 7f0618cf4441
[3.873278] R13: 5615ff4f76a0 R14: 5615ff526e60 R15: 5615ff513f20
[3.873285]  
[3.873287] 

[3.873325] megaraid_sas :43:00.0: current msix/online cpus  : 
(72/64)
[3.873327] megaraid_sas :43:00.0: RDPQ mode : (enabled)
[3.873332] megaraid_sas :43:00.0: Current firmware supports maximum 
commands: 5101   LDIO threshold: 0

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

Title:
  [SRU][Ubuntu 

[Kernel-packages] [Bug 2045483] [NEW] package linux-image-5.15.0-88-generic 5.15.0-88.98 failed to install/upgrade: installed linux-image-5.15.0-88-generic package pre-removal script subprocess return

2023-12-02 Thread william boshinski
Public bug reported:

was trying to clan up the /boot

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-88-generic 5.15.0-88.98
ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126
Uname: Linux 5.15.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  wboshinski   4285 F pulseaudio
CasperMD5CheckResult: unknown
Date: Sat Dec  2 19:31:31 2023
ErrorMessage: installed linux-image-5.15.0-88-generic package pre-removal 
script subprocess returned error exit status 1
HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
InstallationDate: Installed on 2020-02-22 (1379 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
IwConfig:
 lono wireless extensions.
 
 enp0s31f6  no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 10d7:b012 Actions general adapter
 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. PowerEdge T30
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-88-generic 
root=/dev/mapper/hostname--vg-root ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-5.15.0-88-generic 5.15.0-88.98 failed to 
install/upgrade: installed linux-image-5.15.0-88-generic package pre-removal 
script subprocess returned error exit status 1
UpgradeStatus: Upgraded to jammy on 2022-08-23 (466 days ago)
dmi.bios.date: 05/21/2019
dmi.bios.release: 1.1
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.0
dmi.board.name: 07T4MC
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd05/21/2019:br1.1:svnDellInc.:pnPowerEdgeT30:pvr:rvnDellInc.:rn07T4MC:rvrA12:cvnDellInc.:ct6:cvr:sku07C5:
dmi.product.name: PowerEdge T30
dmi.product.sku: 07C5
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package jammy need-duplicate-check

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

Title:
  package linux-image-5.15.0-88-generic 5.15.0-88.98 failed to
  install/upgrade: installed linux-image-5.15.0-88-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  was trying to clan up the /boot

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-88-generic 5.15.0-88.98
  ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wboshinski   4285 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat Dec  2 19:31:31 2023
  ErrorMessage: installed linux-image-5.15.0-88-generic package pre-removal 
script subprocess returned error exit status 1
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2020-02-22 (1379 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 10d7:b012 Actions general adapter
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge T30
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-88-generic 
root=/dev/mapper/hostname--vg-root ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-5.15.0-88-generic 5.15.0-88.98 failed to 
install/upgrade: installed linux-image-5.15.0-88-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-08-23 (466 days ago)
  dmi.bios.date: 05/21/2019
  dmi.bios.release: 1.1
  

[Kernel-packages] [Bug 2045482] [NEW] USB-C to HDMI Sound Not Functioning

2023-12-02 Thread Alex
Public bug reported:

Hello there,

I have Ubuntu 23.10 installed on a Dell XPS 13 9300 with a USB-C to HDMI
adapter attached to a Samsung television. When I try to set the output
sound to the Samsung Television, no sound output is heard. However, when
setting to the internal speakers there is sound output. The cable and
adapter are fine as I have tested the USB-C to HDMI adapter cable with
another device and sound output is confirmed. I have not had this issue
with previous iterations of Ubuntu such as 23.04 & 22.04 LTS.


Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-13-generic 6.5.0-13.13
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  joe8491 F wireplumber
 /dev/snd/seq:joe8485 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec  2 16:07:39 2023
InstallationDate: Installed on 2023-10-12 (51 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-13-generic 
root=UUID=41952781-0b82-430a-a2af-114815de54ab ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-13-generic N/A
 linux-backports-modules-6.5.0-13-generic  N/A
 linux-firmware20230919.git3672ccab-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2023
dmi.bios.release: 1.20
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.20.0
dmi.board.name: 0Y4GNJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.0:bd08/08/2023:br1.20:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0Y4GNJ:rvrA01:cvnDellInc.:ct10:cvr:sku096D:
dmi.product.family: XPS
dmi.product.name: XPS 13 9300
dmi.product.sku: 096D
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug mantic wayland-session

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/2045482/+attachment/5725954/+files/lspci-vnvn.log

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

Title:
  USB-C to HDMI Sound Not Functioning

Status in linux package in Ubuntu:
  New

Bug description:
  Hello there,

  I have Ubuntu 23.10 installed on a Dell XPS 13 9300 with a USB-C to
  HDMI adapter attached to a Samsung television. When I try to set the
  output sound to the Samsung Television, no sound output is heard.
  However, when setting to the internal speakers there is sound output.
  The cable and adapter are fine as I have tested the USB-C to HDMI
  adapter cable with another device and sound output is confirmed. I
  have not had this issue with previous iterations of Ubuntu such as
  23.04 & 22.04 LTS.

  
  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-13-generic 6.5.0-13.13
  ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
  Uname: Linux 6.5.0-13-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe8491 F wireplumber
   /dev/snd/seq:joe8485 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  2 16:07:39 2023
  InstallationDate: Installed on 2023-10-12 (51 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-13-generic 
root=UUID=41952781-0b82-430a-a2af-114815de54ab ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-13-generic N/A
   linux-backports-modules-6.5.0-13-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2023
  dmi.bios.release: 1.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.0
  dmi.board.name: 0Y4GNJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.0:bd08/08/2023:br1.20:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0Y4GNJ:rvrA01:cvnDellInc.:ct10:cvr:sku096D:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:

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

2023-12-02 Thread Derk Willem te Bokkel
no change with kernel 6.6.0-14

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

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

Status in linux package in Ubuntu:
  New

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

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

[Kernel-packages] [Bug 2038998] Re: [amdgpu] Screen corruption, distorted geometry and misplaced triangles

2023-12-02 Thread Niklas Schmelzle
The graphic glitch just happened on my system (Ubuntu 23.10, Lenovo
ThinkPad T14 Gen 2a with AMD Ryzen™ 5 PRO 5650U with Radeon™ Graphics ×
12) again. I have `COGL_DEBUG=disable-batching` set in /etc/environment.
Furthermore all extensions are deactivated (however, not deleted).
System was also rebooted.

Interestingly, this time it did not occur to an XWayland window. I
configured chrome to run wayland directly (which decreased the frequency
of the error occuring, at least it seemed like it).

Here dmesg:

[70061.823842] amdgpu :07:00.0: amdgpu: [gfxhub0] no-retry page fault 
(src_id:0 ring:24 vmid:1 pasid:32771, for process chrome pid 5084 thread 
chrome:cs0 pid 5121)
[70061.823858] amdgpu :07:00.0: amdgpu:   in page starting at address 
0x000c5de7b000 from IH client 0x1b (UTCL2)
[70061.823865] amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00100430
[70061.823869] amdgpu :07:00.0: amdgpu:  Faulty UTCL2 client ID: IA 
(0x2)
[70061.823873] amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 0x0
[70061.823877] amdgpu :07:00.0: amdgpu:  WALKER_ERROR: 0x0
[70061.823880] amdgpu :07:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
[70061.823883] amdgpu :07:00.0: amdgpu:  MAPPING_ERROR: 0x0
[70061.823886] amdgpu :07:00.0: amdgpu:  RW: 0x0


I might try to set the kernel parameter next. For clarification: I would add 
amdgpu.mcb=0 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and then run 
'sudo update-grub' (or update-grub2?). Afterwards I can just reboot?

BTW, just to rule other influences out: I do hibernate my system from
time to time. This should not have any influence, or?

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

Title:
  [amdgpu] Screen corruption, distorted geometry and misplaced triangles

Status in GNOME Shell:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
  Ryzen 7 PRO 5850U
  with Radeon (RX Vega 8?) integrated graphics
  16 GB RAM

  Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
  2023 from a daily-live/current .iso generated on October 4, 2023.

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

  Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
  day, was going through setting up and testing the usual programs.

  Installed Steam through apt from the 'mantic' repositories. Installed
  Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
  compatible titles.

  Screen corruption (white and grey streaks) present in-game when GNOME
  UI elements appeared on-screen (e.g., volume, brightness, and keyboard
  backlight indicators) and omnipresent after closing either game.

  Artifacts remain on screen until log-out or reboot. Artifacts were not
  present beforehand.

  Artifacts only appeared in Wayland session; not X11/Xorg.

  I previously had been running the same games on Ubuntu 22.04 LTS
  (GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
  computer without issue (kernel 6.2).

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 01:17:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A00068US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  

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

2023-12-02 Thread Marc Dietrich
*** This bug is a duplicate of bug 2037214 ***
https://bugs.launchpad.net/bugs/2037214

** This bug has been marked a duplicate of bug 2037214
   evict_inodes inode xxx, i_count = 1, was skipped!

-- 
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   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-09-30 (9 days ago)
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F5a
  dmi.board.asset.tag: Default string
  dmi.board.name: X570S AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  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.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570S AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038837/+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 2045467] [NEW] qprint emits dos-style \r \n

2023-12-02 Thread Bernard Moreton
Public bug reported:

$ echo r.fässlin...@somewhere.com | qprint -e | od -c
000   r   .   f   =   C   3   =   A   4   s   s   l   i   n   g   e
020   r   @   s   o   m   e   w   h   e   r   e   .   c   o   m  \r
040  \n
041

The "\r" confuses any addition of prefix "<=?UTF-8?Q?" and suffix "=>"
when creating a quoted-printable email encoding, so that the suffix
appears at the start of the string.

Piping to "tr -d '\r'" resolves the issue, but shouldn't be necessary.


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

$ qprint --version
qprint 1.1
Last revised: 16th December 2014

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

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

Title:
  qprint emits dos-style \r \n

Status in linux package in Ubuntu:
  New

Bug description:
  $ echo r.fässlin...@somewhere.com | qprint -e | od -c
  000   r   .   f   =   C   3   =   A   4   s   s   l   i   n   g   e
  020   r   @   s   o   m   e   w   h   e   r   e   .   c   o   m  \r
  040  \n
  041

  The "\r" confuses any addition of prefix "<=?UTF-8?Q?" and suffix "=>"
  when creating a quoted-printable email encoding, so that the suffix
  appears at the start of the string.

  Piping to "tr -d '\r'" resolves the issue, but shouldn't be necessary.

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

  $ qprint --version
  qprint 1.1
  Last revised: 16th December 2014

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045467/+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 2045072] Re: [Samsung Galaxy Book2 750XED] Screen goes black

2023-12-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [Samsung Galaxy Book2 750XED] Screen goes black

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had to set nomode parameter to avoid the screen become dark and then
  change the line of the file /etc/default/grub

  from "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  to "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0
  intel_idle.max_cstate=2"

  then add to the file /etc/systemd/logind.conf

  the instructions:

  HandleLidSwitch=ignore
  HandleLidSwitchExternalPower=ignore
  HandleLidSwitchDocked=ignore

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 28 22:00:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Alder Lake-UP3 GT2 [Iris Xe 
Graphics] [144d:c1c6]
  InstallationDate: Installed on 2023-11-13 (15 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=681212a7-b32a-4fbf-a9a1-b51bef0216f7 ro quiet splash i915.enable_dc=0 
intel_idle.max_cstate=2 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2023
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P13CFG.039.230726.HQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP750XED-KC2IT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SAMSUNG_SW_REVISION_12345+0.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP13CFG.039.230726.HQ:bd07/26/2023:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn750XED:pvrP13CFG:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP750XED-KC2IT:rvrSAMSUNG_SW_REVISION_12345+0.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-ADLP-PCFG:
  dmi.product.family: Galaxy Book2
  dmi.product.name: 750XED
  dmi.product.sku: SCAI-A5A5-A5A5-ADLP-PCFG
  dmi.product.version: P13CFG
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045072/+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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

2023-12-02 Thread Moncif Bounif
Tested with the compile file used by Devika on post #110 
working like a charm
My laptop is Acer AN515-58
Linux distribution: Ubuntu 22.04.3 LTS

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/20/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ignis_ADH
  dmi.board.vendor: ADL
  dmi.board.version: V1.06
  

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

2023-12-02 Thread Artur Pak
hi @Andreas,
a) OK, I've changed version the to 1.2.9-1ubuntu3.1 and attaching the debdiff.
(I just thought it had to be changed since Noble's version was bumped, but 
happy to keep it)

b) The error was resolved by running with the sudo. Installing the package on 
other systems without this sound card works OK without errors.
Pardon, I haven't addressed that earlier.

** Patch added: "alsa-ucm-conf_1.2.9-1ubuntu3.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+attachment/5725820/+files/alsa-ucm-conf_1.2.9-1ubuntu3.1.debdiff

-- 
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:
  In Progress
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Incomplete
Status in alsa-ucm-conf source package in Lunar:
  Incomplete
Status in alsa-ucm-conf source package in Mantic:
  Incomplete
Status in alsa-ucm-conf source package in Noble:
  Fix Released

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