date:20230929

This change was made by a bot.

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

Title:
  UBSAN: array-index-out-of-bounds in /build/linux-
  IPoq5q/linux-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Mantic with linux 6.5 an error appears in dmesg:

  [   10.281317] 

  [   10.281323] fbcon: Taking over console
  [   10.281327] UBSAN: array-index-out-of-bounds in 
/build/linux-IPoq5q/linux-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43
  [   10.281334] index 1 is out of range for type 'UCHAR [1]'
  [   10.281338] CPU: 2 PID: 321 Comm: (udev-worker) Not tainted 
6.5.0-5-generic #5-Ubuntu
  [   10.281341] Hardware name: System manufacturer System Product Name/P5Q3, 
BIOS 110206/11/2010
  [   10.281342] Call Trace:
  [   10.281345]  
  [   10.281349]  dump_stack_lvl+0x48/0x70
  [   10.281359]  dump_stack+0x10/0x20
  [   10.281362]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   10.281366]  radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon]
  [   10.281506]  radeon_atombios_get_power_modes+0x205/0x210 [radeon]
  [   10.281596]  radeon_pm_init_dpm+0x8e/0x2f0 [radeon]
  [   10.281709]  radeon_pm_init+0xd0/0x100 [radeon]
  [   10.281821]  rv770_init+0x1fa/0x3d0 [radeon]
  [   10.281933]  radeon_device_init+0x540/0xa90 [radeon]
  [   10.282021]  radeon_driver_load_kms+0xcc/0x2f0 [radeon]
  [   10.282111]  drm_dev_register+0x10e/0x240 [drm]
  [   10.282194]  radeon_pci_probe+0xec/0x180 [radeon]
  [   10.282280]  local_pci_probe+0x47/0xb0
  [   10.282285]  pci_call_probe+0x55/0x190
  [   10.282289]  pci_device_probe+0x84/0x120
  [   10.282293]  really_probe+0x1c7/0x410
  [   10.282297]  __driver_probe_device+0x8c/0x180
  [   10.282300]  driver_probe_device+0x24/0xd0
  [   10.282303]  __driver_attach+0x10b/0x210
  [   10.282306]  ? __pfx___driver_attach+0x10/0x10
  [   10.282309]  bus_for_each_dev+0x8d/0xf0
  [   10.282316]  driver_attach+0x1e/0x30
  [   10.282319]  bus_add_driver+0x127/0x240
  [   10.282327]  driver_register+0x5e/0x130
  [   10.282330]  ? __pfx_radeon_module_init+0x10/0x10 [radeon]
  [   10.282416]  __pci_register_driver+0x62/0x70
  [   10.282419]  radeon_module_init+0x4c/0xff0 [radeon]
  [   10.282504]  do_one_initcall+0x5e/0x340
  [   10.282510]  do_init_module+0x68/0x260
  [   10.282514]  load_module+0xba1/0xcf0
  [   10.282518]  ? vfree+0xff/0x2d0
  [   10.282522]  init_module_from_file+0x96/0x100
  [   10.282526]  ? init_module_from_file+0x96/0x100
  [   10.282530]  idempotent_init_module+0x11c/0x2b0
  [   10.282534]  __x64_sys_finit_module+0x64/0xd0
  [   10.282537]  do_syscall_64+0x5c/0x90
  [   10.282542]  ? syscall_exit_to_user_mode+0x37/0x60
  [   10.282545]  ? do_syscall_64+0x68/0x90
  [   10.282549]  ? do_syscall_64+0x68/0x90
  [   10.282552]  ? do_syscall_64+0x68/0x90
  [   10.282555]  ? do_syscall_64+0x68/0x90
  [   10.282558]  ? sysvec_call_function+0x4b/0xd0
  [   10.282567]  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
  [   10.282574] RIP: 0033:0x7f94cb925c5d
  [   10.282591] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 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 8b 71 13 00 f7 d8 64 89 01 48
  [   10.282594] RSP: 002b:7ffcffbfa7b8 EFLAGS: 0246 ORIG_RAX: 
0139
  [   10.282597] RAX: ffda RBX: 55b39a100500 RCX: 
7f94cb925c5d
  [   10.282599] RDX: 0004 RSI: 7f94cbb3c44a RDI: 
0017
  [   10.282601] RBP: 7f94cbb3c44a R08: 0040 R09: 
fde0
  [   10.282602] R10: fe18 R11: 0246 R12: 
0002
  [   10.282604] R13: 55b39a103ba0 R14:  R15: 
55b39a0fe210
  [   10.282607]  
  [   10.282611] 


  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-5-generic 6.5.0-5.5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene 1346 F wireplumber
   /dev/snd/controlC1:  eugene 1346 F wireplumber
   /dev/snd/seq:eugene 1345 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat Sep 30 00:12:30 2023
  HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61
  InstallationDate: Installed on 2019-04-13 (1630 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  IwConfig:
   lono wireless extensions.

   enp2s0no

[Kernel-packages] [Bug 2037760] [NEW] Create modprobe configuration for the IGX kernel

2023-09-29 Thread Jacob Martin

Public bug reported:

Blacklist the following modules, which are replaced by out-of-tree modules:
blacklist tegradisp_nvkms
blacklist tegradisp_rm
blacklist snd_soc_tegra186_asrc
blacklist snd_soc_tegra186_dspk
blacklist snd_soc_tegra210_admaif
blacklist snd_soc_tegra210_adx
blacklist snd_soc_tegra210_ahub
blacklist snd_soc_tegra210_amx
blacklist snd_soc_tegra210_dmic
blacklist snd_soc_tegra210_i2s
blacklist snd_soc_tegra210_mixer
blacklist snd_soc_tegra210_mvc
blacklist snd_soc_tegra210_ope
blacklist snd_soc_tegra210_sfc
blacklist snd_soc_tegra_audio_graph_card
blacklist tegra-safety
blacklist dwmac_tegra
blacklist host1x
blacklist tegra-drm

RTX A6000 is considered "unsupported" by the OpenRM drivers, but we want to use 
them:
options nvidia NVreg_OpenRmEnableUnsupportedGpus=1

Add these modprobe stanzas to the linux-nvidia-tegra-igx kernel's
/lib/modprobe.d config.

** Affects: linux-nvidia-tegra-igx (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Create modprobe configuration for the IGX kernel

Status in linux-nvidia-tegra-igx package in Ubuntu:
  New

Bug description:
  Blacklist the following modules, which are replaced by out-of-tree modules:
  blacklist tegradisp_nvkms
  blacklist tegradisp_rm
  blacklist snd_soc_tegra186_asrc
  blacklist snd_soc_tegra186_dspk
  blacklist snd_soc_tegra210_admaif
  blacklist snd_soc_tegra210_adx
  blacklist snd_soc_tegra210_ahub
  blacklist snd_soc_tegra210_amx
  blacklist snd_soc_tegra210_dmic
  blacklist snd_soc_tegra210_i2s
  blacklist snd_soc_tegra210_mixer
  blacklist snd_soc_tegra210_mvc
  blacklist snd_soc_tegra210_ope
  blacklist snd_soc_tegra210_sfc
  blacklist snd_soc_tegra_audio_graph_card
  blacklist tegra-safety
  blacklist dwmac_tegra
  blacklist host1x
  blacklist tegra-drm

  RTX A6000 is considered "unsupported" by the OpenRM drivers, but we want to 
use them:
  options nvidia NVreg_OpenRmEnableUnsupportedGpus=1

  Add these modprobe stanzas to the linux-nvidia-tegra-igx kernel's
  /lib/modprobe.d config.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2037760/+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 2031344] Re: apply nvidia igx patches for Aug 8-14

2023-09-29 Thread Jacob Martin

** Changed in: linux-nvidia-tegra-igx (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  apply nvidia igx patches for Aug 8-14

Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  2 patches to apply to IGX kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2031344/+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 2032578] Re: apply nvidia igx patches for Aug 15-21

2023-09-29 Thread Jacob Martin

** Changed in: linux-nvidia-tegra-igx (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  apply nvidia igx patches for Aug 15-21

Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  1 patch for the dates Aug 15-21, 2023

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2032578/+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 2035128] Re: mlxbf-gige: Enable the OOB port in mlxbf_gige_open

2023-09-29 Thread Feysel Mohammed

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

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

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

Title:
  mlxbf-gige: Enable the OOB port in mlxbf_gige_open

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

Bug description:
  SRU Justification:

  [Impact]

  At the moment, the OOB port is enabled in the mlxbf_gige_probe
  function. If the mlxbf_gige_open is not executed, this could cause
  pause frames to increase in the case where there is high backgroud
  traffic. This results in clogging the BMC port as well.

  [Fix]

  * Move enabling the OOB port to mlxbf_gige_open.

  [Test Case]

  * Main test for this bug: Check that the BMC is always pingable while
  pushing a BFB

  Other tests:
  * Check if the gige driver is loaded
  * Check that the oob_net0 interface is up and operational
  * Do the reboot test and powercycle test and check the oob_net0 interface 
again
  * Push BFB multiple times and make sure the OOB is up and running

  [Regression Potential]

  Since are moving code that hasn't moved since BF2, it is important to make 
sure that there is no regression.
  Make sure that the OOB interface is always up and pingable after the reboot 
test, the powercycle test
  and after pushing a BFB.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2035128/+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 2037754] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 2037754

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  zram module is missing on new compilations

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  As stated at
  
https://packages.ubuntu.com/search?suite=jammy=amd64=exactfilename=contents=zram.ko
  the last version oflinux-modules-extra that have zram.ko
  kernel module is 5.15.0-25-generic.

  This is a mispackaging because latest kernel is compiled with zram as
  module:

  # grep ZRAM=m /boot/config-5.15.0-84-generic 
  CONFIG_ZRAM=m

  It's possible to check packaging to include the modules correctly to
  newer linux-modules-extra?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037754/+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 2025640] Re: Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to 535.54.03 video output cuts out

** Also affects: nvidia-graphics-drivers-535-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
   Importance: Critical => High

** Also affects: nvidia-graphics-drivers-535 (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-535 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-535 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Lunar)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Focal)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Lunar)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Lunar)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Lunar)
   Importance: Undecided => High

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Focal)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Jammy)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Lunar)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Focal)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Jammy)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Lunar)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to
  535.54.03 video output cuts out

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-535 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-535-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-535 source package in Jammy:
  In Progress
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  In Progress
Status in nvidia-graphics-drivers-535 source package in Lunar:
  In Progress
Status in nvidia-graphics-drivers-535-server source package in Lunar:
  In Progress

Bug description:
  https://forums.developer.nvidia.com/t/ubuntu-22-04-in-the-middle-of-
  updating-drivers-from-530-41-03-to-535-54-03-video-input-cuts-
  out/258588

  https://forums.linuxmint.com/viewtopic.php?p=2344294

  timeline 10:36 - 10:39
  switch to TTY not helped-no video output, SSH not tested

  After emergency sync, reboot (by sysrq), is all fine.

  Jul  3 10:37:14 Panter nvidia-persistenced: Received signal 15
  Jul  3 10:37:14 Panter systemd[1]: Stopping NVIDIA Persistence Daemon...
  Jul  3 10:37:14 Panter nvidia-persistenced: Socket closed.
  Jul  3 10:37:14 Panter nvidia-persistenced: PID file unlocked.
  Jul  3 10:37:14 Panter nvidia-persistenced: PID file closed.
  Jul  3 10:37:14 Panter nvidia-persistenced: The daemon no longer has 
permission to remove its runtime data directory /var/run/nvidia-persistenced
  Jul  3 10:37:14 Panter nvidia-persistenced: Shutdown (1085)
  Jul  3 10:37:14

[Kernel-packages] [Bug 2037754] [NEW] zram module is missing on new compilations

2023-09-29 Thread Leonardo Silva Amaral

Public bug reported:

Hello!

As stated at
https://packages.ubuntu.com/search?suite=jammy=amd64=exactfilename=contents=zram.ko
the last version oflinux-modules-extra that have zram.ko kernel
module is 5.15.0-25-generic.

This is a mispackaging because latest kernel is compiled with zram as
module:

# grep ZRAM=m /boot/config-5.15.0-84-generic 
CONFIG_ZRAM=m

It's possible to check packaging to include the modules correctly to
newer linux-modules-extra?

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

Title:
  zram module is missing on new compilations

Status in linux package in Ubuntu:
  New

Bug description:
  Hello!

  As stated at
  
https://packages.ubuntu.com/search?suite=jammy=amd64=exactfilename=contents=zram.ko
  the last version oflinux-modules-extra that have zram.ko
  kernel module is 5.15.0-25-generic.

  This is a mispackaging because latest kernel is compiled with zram as
  module:

  # grep ZRAM=m /boot/config-5.15.0-84-generic 
  CONFIG_ZRAM=m

  It's possible to check packaging to include the modules correctly to
  newer linux-modules-extra?

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

** Attachment removed: "compile_module.sh"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000947/+attachment/5705396/+files/compile_module.sh

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

[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

** Attachment added: "compile_module.sh"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000947/+attachment/5705396/+files/compile_module.sh

-- 
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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

@giuliano

Thank you for sharing the link. I found the solution there. Have a great
day!

** Attachment added: "compile_module.sh"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000947/+attachment/5705395/+files/compile_module.sh

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

[Kernel-packages] [Bug 2037741] Re: Improve kernel module signing strength

2023-09-29 Thread Dimitri John Ledkov

** Changed in: linux (Ubuntu)
Milestone: None => later

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

Title:
  Improve kernel module signing strength

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Signatures are smaller, and do not use problematic RSA-PKCS#1.5
  padding.

  (SHA-2 standard) SHA512 is also very problematic, because it has no
  protection against length extension attacks anymore.

  Upgrade to SHA3-512 as used by snap assertions, and is of the same
  length & same security bits as current scheme.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037741/+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 2037741] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 2037741

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Improve kernel module signing strength

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Signatures are smaller, and do not use problematic RSA-PKCS#1.5
  padding.

  (SHA-2 standard) SHA512 is also very problematic, because it has no
  protection against length extension attacks anymore.

  Upgrade to SHA3-512 as used by snap assertions, and is of the same
  length & same security bits as current scheme.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037741/+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 2037741] [NEW] Improve kernel module signing strength

2023-09-29 Thread Dimitri John Ledkov

Public bug reported:

Signatures are smaller, and do not use problematic RSA-PKCS#1.5 padding.

(SHA-2 standard) SHA512 is also very problematic, because it has no
protection against length extension attacks anymore.

Upgrade to SHA3-512 as used by snap assertions, and is of the same
length & same security bits as current scheme.

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

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

Title:
  Improve kernel module signing strength

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Signatures are smaller, and do not use problematic RSA-PKCS#1.5
  padding.

  (SHA-2 standard) SHA512 is also very problematic, because it has no
  protection against length extension attacks anymore.

  Upgrade to SHA3-512 as used by snap assertions, and is of the same
  length & same security bits as current scheme.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037741/+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 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices

2023-09-29 Thread Brian Murray

"Let's get ubuntu-drivers-common uploaded ASAP so that we can test the
fix from a daily build well before release" he said with his release
team hat on.

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

Title:
  b43 driver conflicts with bcmwl driver for some Broadcom devices

Status in broadcom-sta package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Triaged
Status in broadcom-sta source package in Lunar:
  New
Status in linux-firmware source package in Lunar:
  Invalid
Status in ubuntu-drivers-common source package in Lunar:
  Incomplete
Status in broadcom-sta source package in Mantic:
  New
Status in linux-firmware source package in Mantic:
  Invalid
Status in ubuntu-drivers-common source package in Mantic:
  Triaged

Bug description:
  Specifically for Lunar - using a Macbook Air 2012, its wireless driver
  was not enabled even though I ticked the wireless tickbox on the
  installer.

  A quick look at the installer logs reveals various issues

  syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [   43.063747] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [   43.063802] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063862] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063908] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2

  I will attach the installer logs manually since this was captured
  after the installation

  Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was
  installed correctly during the install so this is a regression with
  the 6.2 kernel

  Workaround
  --
  You'll first need to blacklist the b43 driver by adding a blacklist file to 
/etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run 
"update-initramfs -u". Then install the bcmwl-kernel-source package. After a 
reboot your wireless device should be available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 2036271] Re: Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036271/+attachment/5705363/+files/version.log

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

Title:
  Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

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

Bug description:
  My Ubuntu installation fails to boot with the kernel 6.2.0-32-generic
  on a Lenovo Ideapad Flex 5 14ALC05

  The Ubuntu splash screen appear with the loader but the boot process
  is stuck there (with the loader still animating)

  No problem when booting with the kernel 6.2.0-26-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 15 19:22:42 2023
  InstallationDate: Installed on 2021-08-26 (750 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (511 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036271/+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 2036271] Re: Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

** Attachment added: "lspcivvnn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036271/+attachment/5705361/+files/lspcivvnn.log

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

Title:
  Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

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

Bug description:
  My Ubuntu installation fails to boot with the kernel 6.2.0-32-generic
  on a Lenovo Ideapad Flex 5 14ALC05

  The Ubuntu splash screen appear with the loader but the boot process
  is stuck there (with the loader still animating)

  No problem when booting with the kernel 6.2.0-26-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 15 19:22:42 2023
  InstallationDate: Installed on 2021-08-26 (750 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (511 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036271/+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 2036271] Re: Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

** Attachment added: "uname-a.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036271/+attachment/5705362/+files/uname-a.log

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

Title:
  Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

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

Bug description:
  My Ubuntu installation fails to boot with the kernel 6.2.0-32-generic
  on a Lenovo Ideapad Flex 5 14ALC05

  The Ubuntu splash screen appear with the loader but the boot process
  is stuck there (with the loader still animating)

  No problem when booting with the kernel 6.2.0-26-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 15 19:22:42 2023
  InstallationDate: Installed on 2021-08-26 (750 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (511 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036271/+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 2036271] Re: Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

As the kernel version that has the issue does not boot, the commands as per 
https://wiki.ubuntu.com/Kernel/Bugs
were collected with an older kernel!


** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036271/+attachment/5705360/+files/dmesg.log

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

Title:
  Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

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

Bug description:
  My Ubuntu installation fails to boot with the kernel 6.2.0-32-generic
  on a Lenovo Ideapad Flex 5 14ALC05

  The Ubuntu splash screen appear with the loader but the boot process
  is stuck there (with the loader still animating)

  No problem when booting with the kernel 6.2.0-26-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 15 19:22:42 2023
  InstallationDate: Installed on 2021-08-26 (750 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (511 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036271/+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 2036273] Re: 5.15+ GCE Instances are unable to create fb0 with virt mon attached

2023-09-29 Thread Kyler Hornor

The -gcp bisect is still ongoing, but we've met with some of the Google
folks regarding the second part of the issue. The second part of the
issue has been picked up by them, as the FBIOPUT_VSCREENINFO ioctl seems
to have regressed in modern xserver-xorg-core packages, but we're still
awaiting feedback on next steps/timelines as it's upstream of us.

Both of these will need to be resolved for the virt disp to fully work.
If Google does outpace this LP's work and we're able to backport the
changes, the scope of this LP could be worked around by using -generic
in the interim.

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

Title:
  5.15+ GCE Instances are unable to create fb0 with virt mon attached

Status in linux-gcp package in Ubuntu:
  New

Bug description:
  This is a public facing LP issue to address the content in Canonical's
  SF#00366439.

  Summary:

  Post 18.04 ( or 20.04 prior to moving to 5.15 ), efifb fails to stand up fb0. 
It is assigned, but fb0 is never created, nor are there any errors that I 
noted. Here is an example from a focal using linux-gcp
  ---
  5.15.0-1041-gcp #49~20.04.1-Ubuntu SMP
  kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb
  [0.925827] pci :00:05.0: BAR 0: assigned to efifb
  ---

  If you then install the generic HWE kernel and reboot, you can see
  that fb0 is successfully summoned:

  ---
  5.15.0-83-generic #92~20.04.1-Ubuntu SMP
  kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb
  [2.128815] pci :00:05.0: BAR 0: assigned to efifb
  [3.021819] efifb: probing for efifb
  [3.022511] efifb: framebuffer at 0xc000, using 6076k, total 6075k
  [3.023925] efifb: mode is 1920x1080x24, linelength=5760, pages=1
  [3.025382] efifb: scrolling: redraw
  [3.026347] efifb: Truecolor: size=0:8:8:8, shift=0:16:8:0
  ---

  and finally, using linux-gcp-lts on 20.04, it does work (as it's 5.4):
  ---
  5.4.0-1112-gcp #121-Ubuntu SMP
  kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb
  [0.834541] pci :00:05.0: BAR 0: assigned to efifb
  [1.057258] efifb: probing for efifb
  [1.058182] efifb: framebuffer at 0xc000, using 6076k, total 6075k
  [1.059210] efifb: mode is 1920x1080x24, linelength=5760, pages=1
  [1.060203] efifb: scrolling: redraw
  [1.060722] efifb: Truecolor: size=0:8:8:8, shift=0:16:8:0
  ---

  So some linux-gcp backport or config seems to be breaking this.

  Supplementary to this, the framebuffer can not be leveraged by X and
  throws a fatal error around the time shadow is loaded. This part is
  replicable on -generic, as well as on debian using gdm3/X, so this is
  likely an upstream problem. I tried disabling shadow with an X conf,
  but as it uses 24bppp, it forces it.

  
  For the scope of this LP, we need to figure out the -gcp specific breakage. 
I've reached out to google to see if we can get some contacts on the virt mon 
team to push the other aspect forward.

  Replication:
  Launch any ubuntu 20.04+ GCE instance with the "Display Device" option 
enabled. 

  Expected Behavior:
  We should see the above output in dmesg and also observe /dev/fb0 being 
created.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2036273/+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 2037642] Re: [FFe] Raspberry Pi 5 support

This bug was fixed in the package rpi-eeprom - 18.4-1ubuntu1

---
rpi-eeprom (18.4-1ubuntu1) mantic; urgency=medium

  * New upstream release (LP: #2037642)
  * Adds Raspberry Pi 5 support

 -- Dave Jones   Thu, 28 Sep 2023 14:51:50
+0100

** Changed in: rpi-eeprom (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  [FFe] Raspberry Pi 5 support

Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Triaged
Status in linux-raspi package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in pipewire package in Ubuntu:
  Triaged
Status in rpi-eeprom package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Triaged

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

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

2023-09-29 Thread Douglas

Hello Brothers!

Shouldn't Quanta or Acer accurately propose a patch to make your device
work natively on recent kernels?
Or do they do this but the team that maintains the kernel takes a while to
accept the changes?

 []s

Em sex., 29 de set. de 2023 às 09:00, Giuliano Lotta <
2000...@bugs.launchpad.net> escreveu:

> @devyca
>
> Hi, truly speaking, Ubuntu 22.04 uses are NOT supposed to follow #37 ...
>
> they are supposed to use ONLY
>
> https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-Facing-0x0408-0x4035-/blob/main/compile_module.sh
>
> I understand your problem, but cannot follow each particular method users
> are choosing to patch the camera...
> sorry  :-(
>
>
> Giulano
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
>

[Kernel-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

** Merge proposal linked:
   https://code.launchpad.net/~danilogondolfo/netplan/+git/netplan/+merge/452454

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

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

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  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: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+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 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

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

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

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

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

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  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: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+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 2037672] Re: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen

2023-09-29 Thread Mario Limonciello

In this case the kernel is the "messenger" for the page fault.  This is
more likely to be a mesa or application issue than a kernel issue.

Can you please raise a ticket to the upstream mesa bug tracker?

https://gitlab.freedesktop.org/mesa/mesa/

** Also affects: mesa (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/2037672

Title:
  amdgpu: [gfxhub] page fault when switching a video to or from
  fullscreen

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

Bug description:
  Hi,

  Switching a video to or from fullscreen freezes the screen for around
  10 seconds. This happens with Totem as well as VLC so its not related
  to a specific app.

  Additional observations:

  - The issue seems to be connected to the video's bitrate. With low
  bitrate videos I cannot trigger the freeze. However, videos with high
  bandwidth trigger the freeze reliably.

  Specs:
  Ubuntu 23.10 up to date as of 28.09.2023
  AMD Ryzen 7 PRO 6850U
  Kernel 6.5.0-5-generic
  Grub configured with: amdgpu.vm_update_mode=3

  Syslog shows:

  2023-09-28T20:02:29.803955+02:00 kernel: [27003.800898] amdgpu
  :04:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2
  pasid:32771, for process Xwayland pid 2113 thread Xwayland:cs0 pid
  2311)

  2023-09-28T20:02:39.975854+02:00 kernel: [27013.972772]
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but
  soft recovered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037672/+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 2037667] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 2037667

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  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: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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

apport information

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

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

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

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  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: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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

apport information

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

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  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: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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

apport information

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

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  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: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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

apport information

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

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  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: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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

apport information

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

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  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: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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

apport information

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

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  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: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2037667/+attachment/5705353/+files/ProcCpuinfo.txt

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  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: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+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 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

apport information

** Tags added: apport-collected jammy uec-images

** Description changed:

  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual interfaces
  and systemd-networkd is failing to create them starting on kernel
  5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the last
  revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.
  
  How to reproduce the issue:
  
  # Launch a jammy cloud VM:
  
  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy
  
  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot
  
  # Check with "ip link" again that both tun0 and tun1 were created
  
- # Reboot again to go back to the most recent kernel and check with "ip
- link" that both tun0 and tun1 were not created.
+ # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
+  crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
+ 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: [Errno 2] No such file or directory: 'fuser'
+ CRDA: N/A
+ CasperMD5CheckResult: unknown
+ CloudArchitecture: x86_64
+ CloudID: lxd
+ CloudName: lxd
+ CloudPlatform: lxd
+ CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
+ DistroRelease: Ubuntu 22.04
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
+ Lspci: Error: [Errno 2] No such file or directory: 'lspci'
+ Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
+ Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
+ Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
+ Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
+ MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=screen-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 virtio_gpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-84-generic N/A
+  linux-backports-modules-5.15.0-84-generic  N/A
+  linux-firmware N/A
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
+ Tags:  jammy uec-images
+ Uname: Linux 5.15.0-84-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 2/2/2022
+ dmi.bios.release: 0.0
+ dmi.bios.vendor: EDK II
+ dmi.bios.version: unknown
+ dmi.board.name: LXD
+ dmi.board.vendor: Canonical Ltd.
+ dmi.board.version: pc-q35-8.0
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: QEMU
+ dmi.chassis.version: pc-q35-8.0
+ dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
+ dmi.product.name: Standard PC (Q35 + ICH9, 2009)
+ dmi.product.version: pc-q35-8.0
+ dmi.sys.vendor: QEMU

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2037667/+attachment/5705352/+files/CurrentDmesg.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/2037667

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml

[Kernel-packages] [Bug 2036271] Re: Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

An update to this bug.
In the meantime a newer kernel version 6.2.0-33-generic is available, so i've
installed it via "apt update / apt upgrade". Unfortunately it shows the same
behaviour as the 6.2.0.32 version. So it's not possible to boot this notebook
with the newer kernel versions.

Additional info:
For some testings i've added 2 partitions on the notebook and installed kubuntu
22.04.02 and as well from latest image kubuntu 22.04.3. (Only minimal system
and with and without third-party drivers) All installations work fine after
installation, but when i do an apt upgrade the 6.2.0-33-generic kernel will not
boot.

Not sure if this is maybe interesting:
As in my initial installation the 6.2.0-31-generic kernel is working fine, i've
tried to install this kernel on the test installations as well. Normal boot
with the kernel 6.2.0.31 does NOT work! But in recovery mode it reaches the
screen were you can select "resume" to proceed with boot. The last one works
then, only e.g. network is missing.

Btw. I have another but old notebook ( from 2016 ), here everything works fine
with this kernels.

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

Title:
Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

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

Bug description:
My Ubuntu installation fails to boot with the kernel 6.2.0-32-generic
on a Lenovo Ideapad Flex 5 14ALC05

The Ubuntu splash screen appear with the loader but the boot process
is stuck there (with the loader still animating)

No problem when booting with the kernel 6.2.0-26-generic

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 15 19:22:42 2023
InstallationDate: Installed on 2021-08-26 (750 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: Upgraded to jammy on 2022-04-22 (511 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036271/+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-09-29 Thread Giuliano Lotta

@devyca

Hi, truly speaking, Ubuntu 22.04 uses are NOT supposed to follow #37 ...

they are supposed to use ONLY
https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-Facing-0x0408-0x4035-/blob/main/compile_module.sh

I understand your problem, but cannot follow each particular method users are 
choosing to patch the camera...
sorry  :-(


Giulano

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

[Kernel-packages] [Bug 2025987] Re: 5.15.0-76: Qemu live migration causes VMs to crash but works with HWE kernel

2023-09-29 Thread Markus Schade

It looks like this bug is related to leaking of the PKRU bit.
Applying the patch from Proxmox mentioned in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036675
resolves the issue


** Summary changed:

- 5.15.0-76: Qemu live migration causes VMs to crash but works with HWE kernel
+ 5.15.0-76: Qemu live migration regression due to PKRU leakage

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

Title:
  5.15.0-76: Qemu live migration regression due to PKRU leakage

Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  I am trying to live migrate Qemu VMs between Amd Zen3 to Zen2 servers.

  What we expect:
  VMs continue to run after live-migrate

  What happened:
  VMs instantly get stuck after migration with 100% CPU usage.

  All Nodes are running Ubuntu 22.04.
  We have tested Kernel releases back to 5.15.0-70.

  Nodes running Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 :
  Zen2 -> Zen3 migration: OK
  Zen3 -> Zen2 migration: OK

  Nodes running Ubuntu 5.15.0-76.83-generic 5.15.99 :
  Zen2 -> Zen3 migration: OK
  Zen3 -> Zen2 migration: NOT OK

  Mixed Kernel versions:
  Zen2 5.15.0-76.83-generic -> Zen3 5.19.0-43.44~22.04.1-generic -> OK
  Zen3 5.19.0-43.44~22.04.1-generic -> Zen2 5.15.0-76.83-generic -> OK

  Zen2 5.19.0-43.44~22.04.1-generic -> Zen3 5.15.0-76.83-generic -> OK
  Zen3 5.15.0-76.83-generic -> Zen2 5.19.0-43.44~22.04.1-generic -> NOT OK

  We've tested it with fresh started and with live-migrated VMs, getting
  same results.

  Its probably related to
  KVM: SVM: fix tsc scaling cache logic
  
https://linux.googlesource.com/linux/kernel/git/torvalds/linux/+/11d39e8cc43e1c6737af19ca9372e590061b5ad2

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

2023-09-29 Thread Stefan Bader

Skipped "xen/netback: Fix buffer overrun triggered by unusual packet"
since it was already applied as CVE-2023-34319.

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

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

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

Title:
  Focal update: v5.4.252 upstream stable release

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

Bug description:
  SRU Justification

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

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

  ia64/cpu: Switch to arch_cpu_finalize_init()
  m68k/cpu: Switch to arch_cpu_finalize_init()
  mips/cpu: Switch to arch_cpu_finalize_init()
  sh/cpu: Switch to arch_cpu_finalize_init()
  x86/cpufeatures: Add SEV-ES CPU feature
  x86/cpu: Add VM page flush MSR availablility as a CPUID feature
  x86/cpufeatures: Assign dedicated feature word for CPUID_0x801F[EAX]
  tools headers cpufeatures: Sync with the kernel sources
  x86/cpu, kvm: Add support for CPUID_8021_EAX
  xen/netback: Fix buffer overrun triggered by unusual packet
  Linux 5.4.252
  UBUNTU: Upstream stable to v5.4.252

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036240/+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 2020469] Re: Package ppc64el/s390x signing certs

Yes, I could find the 'ubuntu.pem' in the ISO image root folder starting with 
(current) mantic-live-server-s390x.iso 2023-09-28(.5).
Great - and many thanks - highly appreciated!
With that I'm updating the project entry to Fix Released, too.

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Released

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

Title:
  Package ppc64el/s390x signing certs

Status in Ubuntu CD Images:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux-signed package in Ubuntu:
  Fix Committed
Status in s390-tools-signed package in Ubuntu:
  Fix Released

Bug description:
  Package ppc64el/s390x signing certs

  For ease of using signed boot on opal & sipl platforms, package and
  expose the signing certificate in .pem format in the .deb packages and
  on the isos.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/2020469/+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 2037712] [NEW] pi-kernel in UC22 missing mt7601u.ko and rtl8192cu.ko

2023-09-29 Thread Oliver Grawert

Public bug reported:

While included in UC20, the mt7601u.ko and rtl8192cu.ko seem to be
missing in UC22 kernels, please move it back in place, our customers
that run UC20 or tested with UC20 will expect their hardware to keep
working in UC22 installs

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

** Summary changed:

- pi-kernel in UC22 missing mt7601u.ko
+ pi-kernel in UC22 missing mt7601u.ko and rtl8192cu.ko

** Description changed:

- While included in UC20, the mt7601u.ko seems to be missing in UC22
- kernels, please move it back in place, our customers that run UC20 or
- tested with UC20 will expect their hardware to keep working in UC22
- installs
+ While included in UC20, the mt7601u.ko and rtl8192cu.ko seem to be
+ missing in UC22 kernels, please move it back in place, our customers
+ that run UC20 or tested with UC20 will expect their hardware to keep
+ working in UC22 installs

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

Title:
  pi-kernel in UC22 missing mt7601u.ko and rtl8192cu.ko

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  While included in UC20, the mt7601u.ko and rtl8192cu.ko seem to be
  missing in UC22 kernels, please move it back in place, our customers
  that run UC20 or tested with UC20 will expect their hardware to keep
  working in UC22 installs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2037712/+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 1967593] Re: kernel modules going missing after reboot

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  kernel modules going missing after reboot

Status in cloud-initramfs-tools package in Ubuntu:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-lowlatency package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  EDIT: There are no accurate results in the package search, but it is
  for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for
  the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it
  is not kernel specific. It must be a problem with configuration, but
  reinstalling doesnt fix it.

  EDIT2: it turns out this is caused by the cloud-initramfs-copymods
  package mounting over modules locations. Removed it and reinstalled
  kernel modules package (extras didnt seem necessary, but probably
  prudent too).


  This affects several different kernels I've tried in 22.04.

  This post basically sums it up:
  
https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot
  detailed answer: https://unix.stackexchange.com/a/499580/346155

  And this one from upgrading from 20.04 to 22.04:
  
https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade

  Basically, for some reason the kernel modules are being mounted over
  after reboot.

  My image was built on top of a cloud-init image, but removing the recommeded 
package "cloud-initramfs-copymods" that mounts over modules didnt work for me. 
Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules 
did fix my issue for this module. But how many others will not be available?
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2189 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.

   virbr0no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  RfKill:

  Tags:  jammy uec-images
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago)
  UserGroups: libvirt sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2189 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.

   virbr0no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[Kernel-packages] [Bug 1967593] Re: kernel modules going missing after reboot

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

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

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

Title:
  kernel modules going missing after reboot

Status in cloud-initramfs-tools package in Ubuntu:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-lowlatency package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  EDIT: There are no accurate results in the package search, but it is
  for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for
  the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it
  is not kernel specific. It must be a problem with configuration, but
  reinstalling doesnt fix it.

  EDIT2: it turns out this is caused by the cloud-initramfs-copymods
  package mounting over modules locations. Removed it and reinstalled
  kernel modules package (extras didnt seem necessary, but probably
  prudent too).


  This affects several different kernels I've tried in 22.04.

  This post basically sums it up:
  
https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot
  detailed answer: https://unix.stackexchange.com/a/499580/346155

  And this one from upgrading from 20.04 to 22.04:
  
https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade

  Basically, for some reason the kernel modules are being mounted over
  after reboot.

  My image was built on top of a cloud-init image, but removing the recommeded 
package "cloud-initramfs-copymods" that mounts over modules didnt work for me. 
Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules 
did fix my issue for this module. But how many others will not be available?
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2189 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.

   virbr0no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  RfKill:

  Tags:  jammy uec-images
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago)
  UserGroups: libvirt sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2189 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.

   virbr0no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[Kernel-packages] [Bug 1967593] Re: kernel modules going missing after reboot

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

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

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

Title:
  kernel modules going missing after reboot

Status in cloud-initramfs-tools package in Ubuntu:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-lowlatency package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  EDIT: There are no accurate results in the package search, but it is
  for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for
  the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it
  is not kernel specific. It must be a problem with configuration, but
  reinstalling doesnt fix it.

  EDIT2: it turns out this is caused by the cloud-initramfs-copymods
  package mounting over modules locations. Removed it and reinstalled
  kernel modules package (extras didnt seem necessary, but probably
  prudent too).


  This affects several different kernels I've tried in 22.04.

  This post basically sums it up:
  
https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot
  detailed answer: https://unix.stackexchange.com/a/499580/346155

  And this one from upgrading from 20.04 to 22.04:
  
https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade

  Basically, for some reason the kernel modules are being mounted over
  after reboot.

  My image was built on top of a cloud-init image, but removing the recommeded 
package "cloud-initramfs-copymods" that mounts over modules didnt work for me. 
Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules 
did fix my issue for this module. But how many others will not be available?
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2189 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.

   virbr0no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  RfKill:

  Tags:  jammy uec-images
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago)
  UserGroups: libvirt sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2189 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.

   virbr0no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[Kernel-packages] [Bug 2033735] Re: No HDMI in Nvidia on-demand mode

2023-09-29 Thread Francois Thirioux

>From same source:
6.5 rc1 does not boot (hang during boot)
6.5 rc2 does boot but does *not* have hdmi + dGPU working

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

Title:
  No HDMI in Nvidia on-demand mode

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Legion laptop with Nvidia.
  - Nouveau : no hdmi
  - Nvidia 535 dynamic graphics : no HDMI (screen not detected)
  - Nvidia 535 discrete graphics : HDMI is detected

  So I suppose this bug to be linked to Intel GPU.

  All was ok with previous 6.3 kernel.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fthx   3395 F wireplumber
   /dev/snd/controlC1:  fthx   3395 F wireplumber
   /dev/snd/seq:fthx   3390 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-09-15 (723 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230815.git0e048b06-0ubuntu1
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-5-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-03-06 (186 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/10/2023
  dmi.bios.release: 1.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J2CN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 5 Pro 16IAH7H
  dmi.ec.firmware.release: 1.54
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ2CN54WW:bd07/10/2023:br1.54:efr1.54:svnLENOVO:pn82RF:pvrLegion5Pro16IAH7H:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion5Pro16IAH7H:skuLENOVO_MT_82RF_BU_idea_FM_Legion5Pro16IAH7H:
  dmi.product.family: Legion 5 Pro 16IAH7H
  dmi.product.name: 82RF
  dmi.product.sku: LENOVO_MT_82RF_BU_idea_FM_Legion 5 Pro 16IAH7H
  dmi.product.version: Legion 5 Pro 16IAH7H
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033735/+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 2037403] Re: PCI BARs larger than 128GB are disabled

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

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

Title:
  PCI BARs larger than 128GB are disabled

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

Bug description:
  [SRU Justification]

  [Impact]

  Current linux-bluefield kernel reports that PCI BARs larger than 128GB
  are disabled.

  Increase the maximum PCI BAR size from 128GB to 8TB for future
  expansion.

  [Test Plan]

  Use updated kernel with PCI device with PCI BARs larger than 128GB.

  [Where problems could occur]

  No potential problems are expected.

  [Other Info]

  Testing has been provided by the customer. This patch is a cherry-pick
  from the upstream 5.18 kernel. It is intended for linux-bluefield
  kernel re-spin but it may be also suitable for the generic kernel
  (separate submission).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037403/+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 2037077] Re: Fix unstable audio at low levels on Thinkpad P1G4

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

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

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

Title:
  Fix unstable audio at low levels on Thinkpad P1G4

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 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 source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  The audio at low levels is not stable with fluctuating levels.

  [Fix]
  Forcibly assign NID 0x03 to HP while NID 0x02 to SPK.

  [Test]
  Tested on hardware, the audio output is OK at all levels.

  [Where problems could occur]
  It may break audio output on Thinkpad P1G4/5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037077/+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 2037077] Re: Fix unstable audio at low levels on Thinkpad P1G4

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

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

Title:
  Fix unstable audio at low levels on Thinkpad P1G4

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 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 source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  The audio at low levels is not stable with fluctuating levels.

  [Fix]
  Forcibly assign NID 0x03 to HP while NID 0x02 to SPK.

  [Test]
  Tested on hardware, the audio output is OK at all levels.

  [Where problems could occur]
  It may break audio output on Thinkpad P1G4/5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037077/+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 1945989] Re: Check for changes relevant for security certifications

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

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

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

Title:
  Check for changes relevant for security certifications

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  When producing a new version of some kernels, we need to check for
  changes that might affect FIPS or other certs and justify why a commit
  was kept or removed.

  To simplify this process we can add an automated check that will abort
  the kernel preparation and build when such changes exist without a
  justification.

  [Test Plan]

  Check if the kernel preparation fails (cranky close) when one of a
  security certification changes is added.

  [Where problems could occur]

  No kernels should be affected until we enable this check on each one.
  Even when enabled, that only affects the kernel preparation and not
  the resulting kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945989/+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 2033735] Re: No HDMI in Nvidia on-demand mode

2023-09-29 Thread Francois Thirioux

I tested with 6.4.16 from Ubuntu kernel PPA and I get HDMI + dGPU app
launch working.

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

Title:
  No HDMI in Nvidia on-demand mode

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Legion laptop with Nvidia.
  - Nouveau : no hdmi
  - Nvidia 535 dynamic graphics : no HDMI (screen not detected)
  - Nvidia 535 discrete graphics : HDMI is detected

  So I suppose this bug to be linked to Intel GPU.

  All was ok with previous 6.3 kernel.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fthx   3395 F wireplumber
   /dev/snd/controlC1:  fthx   3395 F wireplumber
   /dev/snd/seq:fthx   3390 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-09-15 (723 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230815.git0e048b06-0ubuntu1
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-5-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-03-06 (186 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/10/2023
  dmi.bios.release: 1.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J2CN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 5 Pro 16IAH7H
  dmi.ec.firmware.release: 1.54
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ2CN54WW:bd07/10/2023:br1.54:efr1.54:svnLENOVO:pn82RF:pvrLegion5Pro16IAH7H:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion5Pro16IAH7H:skuLENOVO_MT_82RF_BU_idea_FM_Legion5Pro16IAH7H:
  dmi.product.family: Legion 5 Pro 16IAH7H
  dmi.product.name: 82RF
  dmi.product.sku: LENOVO_MT_82RF_BU_idea_FM_Legion 5 Pro 16IAH7H
  dmi.product.version: Legion 5 Pro 16IAH7H
  dmi.sys.vendor: LENOVO

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

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

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

Title:
  Jammy update: v5.15.125 upstream stable release

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

Bug description:
  SRU Justification

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

     v5.15.125 upstream stable release

  Note: Most of this patchset had already been applied to Jammy.

     from git://git.kernel.org/

  ia64/cpu: Switch to arch_cpu_finalize_init()
  m68k/cpu: Switch to arch_cpu_finalize_init()
  mips/cpu: Switch to arch_cpu_finalize_init()
  sh/cpu: Switch to arch_cpu_finalize_init()
  xen/netback: Fix buffer overrun triggered by unusual packet
  Linux 5.15.125
  UBUNTU: Upstream stable to v5.15.125

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036843/+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 2037005] Re: Lunar update: upstream stable patchset 2023-09-21

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

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

Title:
  Lunar update: upstream stable patchset 2023-09-21

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2023-09-21

  Ported from the following upstream stable releases:
  v6.1.41, v6.4.6
  v6.1.42, v6.4.7
  v6.1.43, v6.4.8

     from git://git.kernel.org/

  UBUNTU: Upstream stable to v6.1.41, v6.4.6
  io_uring: treat -EAGAIN for REQ_F_NOWAIT as final for io-wq
  ALSA: hda/realtek - remove 3k pull low procedure
  ALSA: hda/realtek: Add quirk for Clevo NS70AU
  ALSA: hda/realtek: Enable Mute LED on HP Laptop 15s-eq2xxx
  maple_tree: set the node limit when creating a new root node
  maple_tree: fix node allocation testing on 32 bit
  keys: Fix linking a duplicate key to a keyring's assoc_array
  perf probe: Add test for regression introduced by switch to 
die_get_decl_file()
  btrfs: fix warning when putting transaction with qgroups enabled after abort
  fuse: revalidate: don't invalidate if interrupted
  fuse: Apply flags2 only when userspace set the FUSE_INIT_EXT
  btrfs: set_page_extent_mapped after read_folio in btrfs_cont_expand
  btrfs: zoned: fix memory leak after finding block group with super blocks
  fuse: ioctl: translate ENOSYS in outarg
  btrfs: fix race between balance and cancel/pause
  selftests: tc: set timeout to 15 minutes
  selftests: tc: add 'ct' action kconfig dep
  regmap: Drop initial version of maximum transfer length fixes
  of: Preserve "of-display" device name for compatibility
  regmap: Account for register length in SMBus I/O limits
  arm64/fpsimd: Ensure SME storage is allocated after SVE VL changes
  can: mcp251xfd: __mcp251xfd_chip_set_mode(): increase poll timeout
  can: bcm: Fix UAF in bcm_proc_show()
  can: gs_usb: gs_can_open(): improve error handling
  selftests: tc: add ConnTrack procfs kconfig
  dma-buf/dma-resv: Stop leaking on krealloc() failure
  drm/amdgpu/vkms: relax timer deactivation by hrtimer_try_to_cancel
  drm/amdgpu/pm: make gfxclock consistent for sienna cichlid
  drm/amdgpu/pm: make mclk consistent for smu 13.0.7
  drm/client: Fix memory leak in drm_client_target_cloned
  drm/client: Fix memory leak in drm_client_modeset_probe
  drm/amd/display: only accept async flips for fast updates
  drm/amd/display: Disable MPC split by default on special asic
  drm/amd/display: check TG is non-null before checking if enabled
  drm/amd/display: Keep PHY active for DP displays on DCN31
  ASoC: fsl_sai: Disable bit clock with transmitter
  ASoC: fsl_sai: Revert "ASoC: fsl_sai: Enable MCTL_MCLK_EN bit for master mode"
  ASoC: tegra: Fix ADX byte map
  ASoC: rt5640: Fix sleep in atomic context
  ASoC: cs42l51: fix driver to properly autoload with automatic module loading
  ASoC: codecs: wcd938x: fix missing clsh ctrl error handling
  ASoC: codecs: wcd-mbhc-v2: fix resource leaks on component remove
  ASoC: qdsp6: audioreach: fix topology probe deferral
  ASoC: tegra: Fix AMX byte map
  ASoC: codecs: wcd938x: fix resource leaks on component remove
  ASoC: codecs: wcd938x: fix missing mbhc init error handling
  ASoC: codecs: wcd934x: fix resource leaks on component remove
  ASoC: codecs: wcd938x: fix codec initialisation race
  ASoC: codecs: wcd938x: fix soundwire initialisation race
  ext4: correct inline offset when handling xattrs in inode body
  drm/radeon: Fix integer overflow in radeon_cs_parser_init
  ALSA: emu10k1: roll up loops in DSP setup code for Audigy
  quota: Properly disable quotas when add_dquot_ref() fails
  quota: fix warning in dqgrab()
  HID: add quirk for 03f0:464a HP Elite Presenter Mouse
  ovl: check type and offset of struct vfsmount in ovl_entry
  udf: Fix uninitialized array access for some pathnames
  fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev
  MIPS: dec: prom: Address -Warray-bounds warning
  FS: JFS: Fix null-ptr-deref Read in txBegin
  FS: JFS: Check for read-only mounted filesystem in txBegin
  ACPI: video: Add backlight=native DMI quirk for Dell Studio 1569
  rcu-tasks: Avoid pr_info() with spin lock in cblist_init_generic()
  rcu: Mark additional concurrent load from ->cpu_no_qs.b.exp
  sched/fair: Don't balance task to

[Kernel-packages] [Bug 2037593] Re: Jammy update: v5.15.126 upstream stable release

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

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

Title:
  Jammy update: v5.15.126 upstream stable release

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

Bug description:
  SRU Justification

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

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

  io_uring: gate iowait schedule on having pending requests
  perf: Fix function pointer case
  net/mlx5: Free irqs only on shutdown callback
  arm64: errata: Add workaround for TSB flush failures
  arm64: errata: Add detection for TRBE write to out-of-range
  UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_ and 
ARM64_WORKAROUND_TSB_FLUSH_FAILURE
  iommu/arm-smmu-v3: Work around MMU-600 erratum 1076982
  iommu/arm-smmu-v3: Document MMU-700 erratum 2812531
  iommu/arm-smmu-v3: Add explicit feature for nesting
  iommu/arm-smmu-v3: Document nesting-related errata
  arm64: dts: imx8mn-var-som: add missing pull-up for onboard PHY reset pinmux
  word-at-a-time: use the same return type for has_zero regardless of endianness
  KVM: s390: fix sthyi error handling
  wifi: cfg80211: Fix return value in scan logic
  net/mlx5: DR, fix memory leak in mlx5dr_cmd_create_reformat_ctx
  net/mlx5e: fix return value check in mlx5e_ipsec_remove_trailer()
  bpf: Add length check for SK_DIAG_BPF_STORAGE_REQ_MAP_FD parsing
  rtnetlink: let rtnl_bridge_setlink checks IFLA_BRIDGE_MODE length
  net: dsa: fix value check in bcm_sf2_sw_probe()
  perf test uprobe_from_different_cu: Skip if there is no gcc
  net: sched: cls_u32: Fix match key mis-addressing
  mISDN: hfcpci: Fix potential deadlock on >lock
  qed: Fix kernel-doc warnings
  qed: Fix scheduling in a tasklet while getting stats
  net: annotate data-races around sk->sk_max_pacing_rate
  net: add missing READ_ONCE(sk->sk_rcvlowat) annotation
  net: add missing READ_ONCE(sk->sk_sndbuf) annotation
  net: add missing READ_ONCE(sk->sk_rcvbuf) annotation
  net: add missing data-race annotations around sk->sk_peek_off
  net: add missing data-race annotation for sk_ll_usec
  net/sched: taprio: Limit TCA_TAPRIO_ATTR_SCHED_CYCLE_TIME to INT_MAX.
  bpf, cpumap: Handle skb as well when clean up ptr_ring
  bpf: sockmap: Remove preempt_disable in sock_map_sk_acquire
  net: ll_temac: Switch to use dev_err_probe() helper
  net: ll_temac: fix error checking of irq_of_parse_and_map()
  net: korina: handle clk prepare error in korina_probe()
  net: netsec: Ignore 'phy-mode' on SynQuacer in DT mode
  net: dcb: choose correct policy to parse DCB_ATTR_BCN
  s390/qeth: Don't call dev_close/dev_open (DOWN/UP)
  ip6mr: Fix skb_under_panic in ip6mr_cache_report()
  vxlan: Fix nexthop hash size
  net/mlx5: fs_core: Make find_closest_ft more generic
  net/mlx5: fs_core: Skip the FTs in the same FS_TYPE_PRIO_CHAINS fs_prio
  prestera: fix fallback to previous version on same major version
  tcp_metrics: fix addr_same() helper
  tcp_metrics: annotate data-races around tm->tcpm_stamp
  tcp_metrics: annotate data-races around tm->tcpm_lock
  tcp_metrics: annotate data-races around tm->tcpm_vals[]
  tcp_metrics: annotate data-races around tm->tcpm_net
  tcp_metrics: fix data-race in tcpm_suck_dst() vs fastopen
  scsi: zfcp: Defer fc_rport blocking until after ADISC response
  scsi: storvsc: Limit max_sectors for virtual Fibre Channel devices
  libceph: fix potential hang in ceph_osdc_notify()
  USB: zaurus: Add ID for A-300/B-500/C-700
  ceph: defer stopping mdsc delayed_work
  firmware: arm_scmi: Drop OF node reference in the transport channel setup
  exfat: use kvmalloc_array/kvfree instead of kmalloc_array/kfree
  exfat: release s_lock before calling dir_emit()
  mtd: spinand: toshiba: Fix ecc_get_status
  mtd: rawnand: meson: fix OOB available bytes for ECC
  arm64: dts: stratix10: fix incorrect I2C property for SCL signal
  wifi: mt76: mt7615: do not advertise 5 GHz on first phy of MT7615D (DBDC)
  rbd: prevent busy loop when requesting exclusive lock
  bpf: Disable preemption in bpf_event_output
  open: make RESOLVE_CACHED correctly test for O_TMPFILE
  drm/ttm: check null pointer before accessing when swapping
  bpf, cpumap: Make sure kthread is running before map update returns
  file: reinstate f_pos locking optimization for regular files
  fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_load_attr_list()
  fs/sysv: Null check to prevent

[Kernel-packages] [Bug 2037704] [NEW] Desktop won't get to gdm after graphics driver update

2023-09-29 Thread Oliver Smith

Public bug reported:


After a graphics driver update my desktop would not progress past the boot 
splash screen and hangs on a blinking cursor.

Ubuntu recovery mode options and dpkg rebuilds did not resolve the
issue.

I ended up being able to get to the desktop session by using "nomodeset"
but only had access to one monitor.

After consulting with the desktop team the issue was an incomplete
kernel module rebuild and was resolved with the following command:

`sudo apt install --reinstall nvidia-dkms-535`

However this is not intuitive to users as a solution and needs to be
further investigated in terms of finding a more robust update path for
NVIDIA machines to avoid this situation occurring. Looking online it
seems like a common problem, with a variety of non-relevant proposed
solutions on Ask Ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-535 535.113.01-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 29 09:48:42 2023
InstallationDate: Installed on 2023-03-06 (206 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
SourcePackage: nvidia-graphics-drivers-535
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-535 (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug jammy

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

Title:
  Desktop won't get to gdm after graphics driver update

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete

Bug description:
  
  After a graphics driver update my desktop would not progress past the boot 
splash screen and hangs on a blinking cursor.

  Ubuntu recovery mode options and dpkg rebuilds did not resolve the
  issue.

  I ended up being able to get to the desktop session by using
  "nomodeset" but only had access to one monitor.

  After consulting with the desktop team the issue was an incomplete
  kernel module rebuild and was resolved with the following command:

  `sudo apt install --reinstall nvidia-dkms-535`

  However this is not intuitive to users as a solution and needs to be
  further investigated in terms of finding a more robust update path for
  NVIDIA machines to avoid this situation occurring. Looking online it
  seems like a common problem, with a variety of non-relevant proposed
  solutions on Ask Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nvidia-driver-535 535.113.01-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 09:48:42 2023
  InstallationDate: Installed on 2023-03-06 (206 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: nvidia-graphics-drivers-535
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2037704/+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

Hi

@giuliano

I followed the steps from #37, and they worked initially. However, after
a recent update, my kernel changed to 6.2.0-33, and now it no longer
functions properly. When I attempted to retrace the steps from #37, I
encountered error #99, even though I had deleted all the files created
during each execution of the commands.

I have an Acer Aspire A515-57G laptop with the camera identified as
'0408:4033 Quanta Computer, Inc. ACER HD User Facing,' running 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

[Kernel-packages] [Bug 2031333] Re: Need to get fine-grained control for FAN(TFN) Participant.

2023-09-29 Thread Stefan Bader

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

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

Title:
  Need to get fine-grained control for FAN(TFN) Participant.

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

Bug description:
  This is a public version of the following bugs:
  https://bugs.launchpad.net/bugs/1987597
  https://bugs.launchpad.net/bugs/2027754

  

  [Feature Description]
  We need Fine-grained Control of TFN participant for enabling active 2 policy 
in Linux/chrome.

  Currently, The kernel has provided __FPS table and cur__state to
  adjust the fan level as per  _FPS table .

  But there is no option to read  *_FIF (Fan Information) and _FST (Fan
  Status).*

  Once the fine-grained control is enabled, we should be able to the set
  the control value from 0-100 through Arg0 of _FSL (Fan Set Level).

  *_FST (Fan Status)*  should report current running RPM and control
  value of the FAN(TFN).

   please refer ACPI spec for more detail.

  [https://uefi.org/specs/ACPI/6.4/11_Thermal_Management/fan-
  device.html]

  [HW/SW Information]
  Hardware: Alder Lake

  Target Release: 22.04
  Target Kernel: 5.15

  
  Merged for 5.18-rc1

  f1197343f077 ACPI: fan: Add additional attributes for fine grain control
  bea2d9868ef5 ACPI: fan: Properly handle fine grain control
  d445571fa369 ACPI: fan: Optimize struct acpi_fan_fif
  00ae053a0533 ACPI: fan: Separate file for attributes creation

  Platform-independent

  [Business Justification]
  Function enabling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031333/+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 1975650] Re: Nvidia kernel driver stops loading after kernel update (needs manual reinstallation)

2023-09-29 Thread Daniel van Vugt

** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Nvidia kernel driver stops loading after kernel update (needs manual
  reinstallation)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New

Bug description:
  I often have to forcibly power down my PC because of this bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well,
  the most recent time I did that, when the computer restarted, the
  resolution is stuck on 1024x768 even though I am on a 1920x1080
  monitor. I restarted my PC again and it is still stuck on the low
  resolution.

  This Ask Ubuntu answer (https://askubuntu.com/a/1167437/1589552) did
  allow me to force my resolution to 1920x1080, but a few things still
  seemed off:

  - The display settings page in the Gnome settings app still showed my display 
as "unknown display" and did not have any options for changing the resolution.
  - A WebGL-based application I use for work was very slow compared to normal.

  I reverted the change to my Grub config and now I'm back to 1024x768.

  I have an Nvidia GTX 1060 connected to a 1920x1080 monitor via HDMI.
  Let me know of any other information I can provide that would be
  helpful. Also let me know if there is a workaround other than
  reinstalling the OS.

  Edit: I have a Windows dual boot on this PC, with Windows installed on
  a separate SSD. I booted into Windows and everything seems completely
  fine. This provides further evidence that this is a software issue,
  not a hardware one.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 24 20:14:55 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 
1060 3GB] [1462:3287]
  InstallationDate: Installed on 2022-04-23 (31 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic 
root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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/1975650/+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 1800562] Re: Remove obsolete "nousb" option in kdump command-line for newer kernels

2023-09-29 Thread Ubuntu Foundations Team Bug Bot

The attachment "lp1800562_eoan.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

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

Title:
  Remove obsolete "nousb" option in kdump command-line for newer kernels

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in kdump-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Won't Fix
Status in kdump-tools source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  Confirmed
Status in kdump-tools source package in Eoan:
  New
Status in makedumpfile source package in Eoan:
  Won't Fix
Status in kdump-tools source package in Focal:
  New
Status in makedumpfile source package in Focal:
  Confirmed
Status in kdump-tools source package in Groovy:
  New
Status in makedumpfile source package in Groovy:
  Won't Fix

Bug description:
  [Impact]
  * Kdump command-line include an obsolete "nousb" parameter by default, which 
can cause a misimpression: users will think they are not booting with USB, but 
they are.

  * Since kernel v4.5, the correct parameter to disable USB subsystem
  initialization is "usbcore.nousb" always (instead of "nousb" in case
  the subsystem is built-in). This was changed by commit 097a9ea0e48
  ("usb: make "nousb" a clear module parameter").

  * USB may be pretty essential in case for example kdump users need to
  decrypt a disk under LUKS, and there's only an USB keyboard connected
  to the system. Given the option is innocuous since Bionic, we should
  just drop it to prevent confusion.

  
  [Test Case]

  1) Deploy a Disco VM e.g. with uvt-kvm
  2) Install the kdump-tools package
  3) Run `kdump-config test`and check for the 'nousb' parameter:

  $ kdump-config test
  ...
  kexec command to be used:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" 
/var/lib/kdump/vmlinuz

  
  [Regression Potential]

  The regression potential is extremely low, since the "nousb" parameter
  is not used since Bionic although is there. Any bugs we would have by
  changing this are still valid by not removing the option - the
  semantics with or without "nosub" is the same since from Bionic.

  NOTICE we won't change Xenial, it can use kernel 4.4 which indeed
  disables USB by taking the "nousb" parameter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+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 1879755] Re: cp --reflink support

** Changed in: zfs
   Status: Unknown => Fix Released

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

Title:
  cp --reflink support

Status in Native ZFS for Linux:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Won't Fix

Bug description:
  With the recent efforts of promoting ZFS in Ubuntu, it might be a good
  idea to add support for 'cp --reflink=always' such that proven
  workflows for Btrfs can be easily transferred to ZFS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1879755/+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 1899249] Re: OpenZFS writing stalls, under load

** Changed in: zfs
   Status: Unknown => New

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

Title:
  OpenZFS writing stalls, under load

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  Using a QNAP 4-drive USB enclosure, with a set of SSDs, on a Raspberry
  Pi 8GB. ZFS deduplication, and LZJB compression is enabled.

  This issue seems to occur, intermittently, after some time (happens
  with both SMB access, via Samba, and when interacting with the system,
  via SSH), and never previously occurred, until a few months ago, and I
  sometimes have to force a reboot of the system (at the cost of some
  data loss), in order to use it again.

  The "dmesg" log reports:

  [25375.911590] z_wr_iss_h  D0  2161  2 0x0028
  [25375.911606] Call trace:
  [25375.911627]  __switch_to+0x104/0x170
  [25375.911639]  __schedule+0x30c/0x7c0
  [25375.911647]  schedule+0x3c/0xb8
  [25375.911655]  io_schedule+0x20/0x58
  [25375.911668]  rq_qos_wait+0x100/0x178
  [25375.911677]  wbt_wait+0xb4/0xf0
  [25375.911687]  __rq_qos_throttle+0x38/0x50
  [25375.911700]  blk_mq_make_request+0x128/0x610
  [25375.911712]  generic_make_request+0xb4/0x2d8
  [25375.911722]  submit_bio+0x48/0x218
  [25375.911960]  vdev_disk_io_start+0x670/0x9f8 [zfs]
  [25375.912181]  zio_vdev_io_start+0xdc/0x2b8 [zfs]
  [25375.912400]  zio_nowait+0xd4/0x170 [zfs]
  [25375.912617]  vdev_mirror_io_start+0xa8/0x1b0 [zfs]
  [25375.912839]  zio_vdev_io_start+0x248/0x2b8 [zfs]
  [25375.913057]  zio_execute+0xac/0x110 [zfs]
  [25375.913096]  taskq_thread+0x2f8/0x570 [spl]
  [25375.913108]  kthread+0xfc/0x128
  [25375.913119]  ret_from_fork+0x10/0x1c
  [25375.913149] INFO: task txg_sync:2333 blocked for more than 120 seconds.
  [25375.919916]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.926848] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.934835] txg_syncD0  2333  2 0x0028
  [25375.934850] Call trace:
  [25375.934869]  __switch_to+0x104/0x170
  [25375.934879]  __schedule+0x30c/0x7c0
  [25375.934887]  schedule+0x3c/0xb8
  [25375.934899]  schedule_timeout+0x9c/0x190
  [25375.934908]  io_schedule_timeout+0x28/0x48
  [25375.934946]  __cv_timedwait_common+0x1a8/0x1f8 [spl]
  [25375.934982]  __cv_timedwait_io+0x3c/0x50 [spl]
  [25375.935205]  zio_wait+0x130/0x2a0 [zfs]
  [25375.935423]  dsl_pool_sync+0x3fc/0x498 [zfs]
  [25375.935650]  spa_sync+0x538/0xe68 [zfs]
  [25375.935867]  txg_sync_thread+0x2c0/0x468 [zfs]
  [25375.935911]  thread_generic_wrapper+0x74/0xa0 [spl]
  [25375.935924]  kthread+0xfc/0x128
  [25375.935935]  ret_from_fork+0x10/0x1c
  [25375.936017] INFO: task zbackup:75339 blocked for more than 120 seconds.
  [25375.942780]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.949710] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.957702] zbackup D0 75339   5499 0x
  [25375.957716] Call trace:
  [25375.957732]  __switch_to+0x104/0x170
  [25375.957742]  __schedule+0x30c/0x7c0
  [25375.957750]  schedule+0x3c/0xb8
  [25375.957789]  cv_wait_common+0x188/0x1b0 [spl]
  [25375.957823]  __cv_wait+0x30/0x40 [spl]
  [25375.958045]  zil_commit_impl+0x234/0xd30 [zfs]
  [25375.958263]  zil_commit+0x48/0x70 [zfs]
  [25375.958481]  zfs_create+0x544/0x7d0 [zfs]
  [25375.958698]  zpl_create+0xb8/0x178 [zfs]
  [25375.958711]  lookup_open+0x4ec/0x6a8
  [25375.958721]  do_last+0x260/0x8c0
  [25375.958730]  path_openat+0x84/0x258
  [25375.958739]  do_filp_open+0x84/0x108
  [25375.958752]  do_sys_open+0x180/0x2b0
  [25375.958763]  __arm64_sys_openat+0x2c/0x38
  [25375.958773]  el0_svc_common.constprop.0+0x80/0x218
  [25375.958781]  el0_svc_handler+0x34/0xa0
  [25375.958791]  el0_svc+0x10/0x2cc
  [25375.958801] INFO: task zbackup:95187 blocked for more than 120 seconds.
  [25375.965564]   Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
  [25375.972492] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25375.980479] zbackup D0 95187   5499 0x
  [25375.980493] Call trace:
  [25375.980514]  __switch_to+0x104/0x170
  [25375.980525]  __schedule+0x30c/0x7c0
  [25375.980536]  schedule+0x3c/0xb8
  [25375.980578]  cv_wait_common+0x188/0x1b0 [spl]
  [25375.980612]  __cv_wait+0x30/0x40 [spl]
  [25375.980834]  zil_commit_impl+0x234/0xd30 [zfs]
  [25375.981052]  zil_commit+0x48/0x70 [zfs]
  [25375.981280]  zfs_write+0xa3c/0xb90 [zfs]
  [25375.981498]  zpl_write_common_iovec+0xac/0x120 [zfs]
  [25375.981726]  zpl_iter_write+0xe4/0x150 [zfs]
  [25375.981766]  new_sync_write+0x100/0x1a8
  [25375.981776]  __vfs_write+0x74/0x90
  [25375.981784]  vfs_write+0xe4/0x1c8
  [25375.981794]  ksys_write+0x78/0x100
  [25375.981803]  __arm64_sys_write+0x24/0x30
  [25375.981813]

[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

** Changed in: zfs
   Status: New => Fix Released

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux-raspi source package in Impish:
  Fix Released
Status in ubuntu-release-upgrader source package in Impish:
  Won't Fix
Status in zfs-linux source package in Impish:
  Fix Released

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1906476/+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 1913342] Re: zfs.8 man page snapshot listing instructions are confusing

** Changed in: zfs
   Status: Unknown => Fix Released

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

Title:
  zfs.8 man page snapshot listing instructions are confusing

Status in Native ZFS for Linux:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  The zfs.8 man page describes in 3 places how to include snapshots in
  "zfs list":

  1) Snapshots are displayed if the listsnaps property is on (the default is 
off).
  2) Snapshots are displayed if the listsnaps property is on.  The default is 
off.  See zpool(8) for more information on pool properties.
  3) For example, specifying -t snapshot displays only snapshots.

  The first of these has twice now (I'm just learning zfs) sent me down
  a rabbit hole, looking for a zfs dataset property "listsnaps".  There
  is no such property (of datasets).

  I'm on version 0.8.3 of zfsutils-linux that has this man page, but
  when I look at https://zfsonlinux.org/manpages/0.8.6/man8/zfs.8.html
  it seems that the above is still true in 0.8.6

  Suggestion, to help us newbies reduce our learning time to list
  snapshots:

  Change both of the first 2 of the above 3 places in zfs.8 to:
  "
  "zfs list" displays snapshots only if either the "listsnapshots" property of 
the underlying zpool is on, or if the "zfs list -t snapshot" option is 
specified.

  Extra Credit:

  Just now it seems to me that the following command does _NOT_ list
  snapshots, on a dataset that has some snapshots ... so the zfs.8
  documentation that the "zfs list -t type" can be a "comma-separated
  list of types to display" seems incorrect:

  zfs list -t filesystem,snapshot myzfsdataset

  Whether this "Extra Credit" discrepancy is a bug in the documentation,
  or in the zfs command code, or newbie operator error, I'll leave as an
  exercise to the reader .

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: zfsutils-linux 0.8.3-1ubuntu12.5
  ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78
  Uname: Linux 5.4.0-64-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Jan 26 13:41:16 2021
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1913342/+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 1912188] Re: Load growing continously

** Changed in: zfs-ubuntu
   Status: New => Fix Released

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

Title:
  Load growing continously

Status in zfs-ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently load started growing with no end. After a while random
  processes become zombies.

   11:32:22 up 26 min,  1 user,  load average: 196.16, 186.30, 138.60

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-generic 5.8.0.36.40+21.04.38
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tompos 2361 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Jan 18 11:30:11 2021
  InstallationDate: Installed on 2020-12-31 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-36-generic 
root=UUID=086c6507-b389-4208-a8bc-d0b99071b5cd ro rootflags=subvol=@
  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.8.0-36-generic N/A
   linux-backports-modules-5.8.0-36-generic  N/A
   linux-firmware1.194
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-01-02 (15 days ago)
  dmi.bios.date: 10/22/2020
  dmi.bios.release: 14.1
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.14.01
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.4E.00
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 20.78
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.14.01:bd10/22/2020:br14.1:efr20.78:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.4E.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 5DT80EC#BH4
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu56
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tompos 2721 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2020-12-31 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP EliteBook x360 1030 G3
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-33-generic 
root=UUID=086c6507-b389-4208-a8bc-d0b99071b5cd ro rootflags=subvol=@
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  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.8.0-33-generic N/A
   linux-backports-modules-5.8.0-33-generic  N/A
   linux-firmware1.194
  Tags:  hirsute
  Uname: Linux 5.8.0-33-generic x86_64
  UpgradeStatus: Upgraded to hirsute on 2021-01-02 (28 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/22/2020
  dmi.bios.release: 14.1
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.14.01
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.4E.00
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 20.78
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.14.01:bd10/22/2020:br14.1:efr20.78:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.4E.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 5DT80EC#BH4
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs-ubuntu/+bug/1912188/+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 1814983] Re: zfs poor sustained read performance from ssd pool

** Changed in: zfs
   Status: Unknown => Fix Released

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

Title:
  zfs poor sustained read performance from ssd pool

Status in Native ZFS for Linux:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Invalid

Bug description:
  Hello,

  I'm seeing substantially slower read performance from an ssd pool than
  I expected.

  I have two pools on this computer; one ('fst') is four sata ssds, the
  other ('srv') is nine spinning metal drives.

  With a long-running ripgrep process on the fst pool, performance
  started out really good and grew to astonishingly good (iirc ~30kiops,
  as measured by zpool iostat -v 1). However after a few hours the
  performance has dropped to 30-40 iops. top reports an arc_reclaim and
  many arc_prune processes to be consuming most of the CPU time.

  I've included a screenshot of top, some output from zpool iostat -v 1,
  and arc_summary, with "===" to indicate the start of the next
  command's output:

  ===
  top (memory in gigabytes):

  top - 16:27:53 up 70 days, 16:03,  3 users,  load average: 35.67, 35.81, 35.58
  Tasks: 809 total,  19 running, 612 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.0 us, 58.1 sy,  0.0 ni, 39.2 id,  2.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  GiB Mem :  125.805 total,0.620 free,   96.942 used,   28.243 buff/cache
  GiB Swap:5.694 total,5.688 free,0.006 used.   27.840 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   1523 root  20   00.0m   0.0m   0.0m R 100.0  0.0 290:52.26 
arc_reclaim 
   4484 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:18.79 arc_prune 
  
   6225 root  20   00.0m   0.0m   0.0m R  56.2  0.0   1:11.92 arc_prune 
  
   7601 root  20   00.0m   0.0m   0.0m S  56.2  0.0   2:50.25 arc_prune 
  
  30891 root  20   00.0m   0.0m   0.0m S  56.2  0.0   1:33.08 arc_prune 
  
   3057 root  20   00.0m   0.0m   0.0m S  55.9  0.0   9:00.95 arc_prune 
  
   3259 root  20   00.0m   0.0m   0.0m R  55.9  0.0   3:16.84 arc_prune 
  
  24008 root  20   00.0m   0.0m   0.0m S  55.9  0.0   1:55.71 arc_prune 
  
   1285 root  20   00.0m   0.0m   0.0m R  55.6  0.0   3:20.52 arc_prune 
  
   5345 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:15.99 arc_prune 
  
  30121 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:35.50 arc_prune 
  
  31192 root  20   00.0m   0.0m   0.0m S  55.6  0.0   6:17.16 arc_prune 
  
  32287 root  20   00.0m   0.0m   0.0m S  55.6  0.0   1:28.02 arc_prune 
  
  32625 root  20   00.0m   0.0m   0.0m R  55.6  0.0   1:27.34 arc_prune 
  
  22572 root  20   00.0m   0.0m   0.0m S  55.3  0.0  10:02.92 arc_prune 
  
  31989 root  20   00.0m   0.0m   0.0m R  55.3  0.0   1:28.03 arc_prune 
  
   3353 root  20   00.0m   0.0m   0.0m R  54.9  0.0   8:58.81 arc_prune 
  
  10252 root  20   00.0m   0.0m   0.0m R  54.9  0.0   2:36.37 arc_prune 
  
   1522 root  20   00.0m   0.0m   0.0m S  53.9  0.0 158:42.45 arc_prune 
  
   3694 root  20   00.0m   0.0m   0.0m R  53.9  0.0   1:20.79 arc_prune 
  
  13394 root  20   00.0m   0.0m   0.0m R  53.9  0.0  10:35.78 arc_prune 
  
  24592 root  20   00.0m   0.0m   0.0m R  53.9  0.0   1:54.19 arc_prune 
  
  25859 root  20   00.0m   0.0m   0.0m S  53.9  0.0   1:51.71 arc_prune 
  
   8194 root  20   00.0m   0.0m   0.0m S  53.6  0.0   0:54.51 arc_prune 
  
  18472 root  20   00.0m   0.0m   0.0m R  53.6  0.0   2:08.73 arc_prune 
  
  29525 root  20   00.0m   0.0m   0.0m R  53.6  0.0   1:35.81 arc_prune 
  
  32291 root  20   00.0m   0.0m   0.0m S  53.6  0.0   1:28.00 arc_prune 
  
   3156 root  20   00.0m   0.0m   0.0m R  53.3  0.0   3:17.68 arc_prune

[Kernel-packages] [Bug 1800562] Re: Remove obsolete "nousb" option in kdump command-line for newer kernels

2023-09-29 Thread dann frazier

** Also affects: kdump-tools (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: kdump-tools (Ubuntu)

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

Title:
  Remove obsolete "nousb" option in kdump command-line for newer kernels

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in kdump-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Won't Fix
Status in kdump-tools source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  Confirmed
Status in kdump-tools source package in Eoan:
  New
Status in makedumpfile source package in Eoan:
  Won't Fix
Status in kdump-tools source package in Focal:
  New
Status in makedumpfile source package in Focal:
  Confirmed
Status in kdump-tools source package in Groovy:
  New
Status in makedumpfile source package in Groovy:
  Won't Fix

Bug description:
  [Impact]
  * Kdump command-line include an obsolete "nousb" parameter by default, which 
can cause a misimpression: users will think they are not booting with USB, but 
they are.

  * Since kernel v4.5, the correct parameter to disable USB subsystem
  initialization is "usbcore.nousb" always (instead of "nousb" in case
  the subsystem is built-in). This was changed by commit 097a9ea0e48
  ("usb: make "nousb" a clear module parameter").

  * USB may be pretty essential in case for example kdump users need to
  decrypt a disk under LUKS, and there's only an USB keyboard connected
  to the system. Given the option is innocuous since Bionic, we should
  just drop it to prevent confusion.

  
  [Test Case]

  1) Deploy a Disco VM e.g. with uvt-kvm
  2) Install the kdump-tools package
  3) Run `kdump-config test`and check for the 'nousb' parameter:

  $ kdump-config test
  ...
  kexec command to be used:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" 
/var/lib/kdump/vmlinuz

  
  [Regression Potential]

  The regression potential is extremely low, since the "nousb" parameter
  is not used since Bionic although is there. Any bugs we would have by
  changing this are still valid by not removing the option - the
  semantics with or without "nosub" is the same since from Bionic.

  NOTICE we won't change Xenial, it can use kernel 4.4 which indeed
  disables USB by taking the "nousb" parameter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+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 2020469] Re: Package ppc64el/s390x signing certs

2023-09-29 Thread Steve Langasek

https://git.launchpad.net/~ubuntu-cdimage/debian-
cd/+git/ubuntu/commit/?id=3b282009dc2eda1d450b88699d338b001ad43651

Result confirmed in https://cdimage.ubuntu.com/ubuntu-server/daily-
live/20230928.5/mantic-live-server-s390x.list.

** Changed in: ubuntu-cdimage
   Status: New => Fix Released

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

Title:
  Package ppc64el/s390x signing certs

Status in Ubuntu CD Images:
  Fix Released
Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux-signed package in Ubuntu:
  Fix Committed
Status in s390-tools-signed package in Ubuntu:
  Fix Released

Bug description:
  Package ppc64el/s390x signing certs

  For ease of using signed boot on opal & sipl platforms, package and
  expose the signing certificate in .pem format in the .deb packages and
  on the isos.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/2020469/+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 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices

2023-09-29 Thread Dimitri John Ledkov

I think the fix is https://github.com/tseliot/ubuntu-drivers-
common/pull/90/files

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

Title:
  b43 driver conflicts with bcmwl driver for some Broadcom devices

Status in broadcom-sta package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Triaged
Status in broadcom-sta source package in Lunar:
  New
Status in linux-firmware source package in Lunar:
  Invalid
Status in ubuntu-drivers-common source package in Lunar:
  Incomplete
Status in broadcom-sta source package in Mantic:
  New
Status in linux-firmware source package in Mantic:
  Invalid
Status in ubuntu-drivers-common source package in Mantic:
  Triaged

Bug description:
  Specifically for Lunar - using a Macbook Air 2012, its wireless driver
  was not enabled even though I ticked the wireless tickbox on the
  installer.

  A quick look at the installer logs reveals various issues

  syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [   43.063747] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [   43.063802] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063862] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063908] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2

  I will attach the installer logs manually since this was captured
  after the installation

  Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was
  installed correctly during the install so this is a regression with
  the 6.2 kernel

  Workaround
  --
  You'll first need to blacklist the b43 driver by adding a blacklist file to 
/etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run 
"update-initramfs -u". Then install the bcmwl-kernel-source package. After a 
reboot your wireless device should be available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 2021571] Re: cat /sys/fs/cgroup/blkio/blkio.time_recursive took 1second to complete

2023-09-29 Thread Kevin Brierly

It examines the blkio device tree and sums data as far as i know.
Removed devices do not get deleted from the blkio statistics tree and
are just marked as offline somehow.

In our case racadm lclog created and destroyed usb devices to pull data
and the blkio tree reached over 65000 leafs. It takes time to process a
tree that large. WE believe our issue was caused by accumulation over
time of the usb device leafs from racadm lclog. WE had it running in a
cron which has now been stopped.

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

Title:
  cat /sys/fs/cgroup/blkio/blkio.time_recursive  took 1second to
  complete

Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  Issue:

  ```console
  # time cat /sys/fs/cgroup/blkio/blkio.time_recursive
  8:16 354721435

  real0m1.297s
  user0m0.000s
  sys 0m1.297s
  ```

  As could be seen from above result, cat blkio took about 1 second to complete 
which
  is much longer than a normal case.

  Kernel Version:

  Linux compute08 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  
  Would be appreciated to know any operations to identify the issue, Thank you 
very much for the help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+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 2036281] Re: activate bpf LSM by default

2023-09-29 Thread why2jjj

quick google search comes up with:

https://falco.org/docs/event-sources/kernel/
https://medium.com/@lumontec/some-freshness-with-linux-security-modules-and-ebpf-676ac363a135
https://blog.aquasec.com/linux-security-with-tracee-and-ebpf
https://www.infoq.com/presentations/facebook-google-bpf-linux-kernel/
https://kubearmor.io

It's the generic hypothetical solutions that drives innovation to sw
engineering.

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

Title:
  activate bpf LSM by default

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  in Fedora/RHEL if I want to see if the bpf LSM is active/available in
  the kernel I can go here:

  [root@virtualrocky]# cat /sys/kernel/security/lsm
  lockdown,capability,yama,selinux,bpf[root@virtualrocky]#

  but if I do the same thing in Ubuntu 22.0.4 bpf is NOT there:

  root@virtual-ubuntu2204:/# cat /sys/kernel/security/lsm
  lockdown,capability,landlock,yama,apparmorroot@virtual-ubuntu2204:/#

  Please add bpf LSM to the CONFIG_LSM

  See discourse for background info

  https://discourse.ubuntu.com/t/ask-us-anything-about-ubuntu-
  kernels/27664/127?u=why2jjj

  root@virtual-ubuntu2204:/opt/# cat /proc/version_signature 
  Ubuntu 5.15.0-82.91-generic 5.15.111

  THANK YOU!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jfreyensee   2526 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-29 (17 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  MachineType: Parallels Software International Inc. Parallels Virtual Platform
  NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-82-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-82-generic N/A
   linux-backports-modules-5.15.0-82-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.18
  RfKill:
   
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-82-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/03/2023
  dmi.bios.release: 18.3
  dmi.bios.vendor: Parallels Software International Inc.
  dmi.bios.version: 18.3.2 (53621)
  dmi.board.name: Parallels Virtual Platform
  dmi.board.vendor: Parallels Software International Inc.
  dmi.board.version: None
  dmi.chassis.type: 2
  dmi.chassis.vendor: Parallels Software International Inc.
  dmi.ec.firmware.release: 18.3
  dmi.modalias: 
dmi:bvnParallelsSoftwareInternationalInc.:bvr18.3.2(53621):bd07/03/2023:br18.3:efr18.3:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct2:cvr:skuUndefined:
  dmi.product.family: Parallels VM
  dmi.product.name: Parallels Virtual Platform
  dmi.product.sku: Undefined
  dmi.product.version: None
  dmi.sys.vendor: Parallels Software International Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036281/+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 2037316] Re: SEV_SNP failure to init

2023-09-29 Thread Tim Gardner

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

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

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

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

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

Title:
  SEV_SNP failure to init

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-gcp package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Jammy:
  Invalid
Status in linux-gcp source package in Jammy:
  Fix Committed
Status in linux-aws source package in Lunar:
  Fix Committed
Status in linux-gcp source package in Lunar:
  Fix Committed
Status in linux-aws source package in Mantic:
  Fix Committed
Status in linux-gcp source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  * Kernel fails to boot on SEV-SNP instances when compiled with GCC
  12.3.0

  [Fix]

  *
  https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/

  [Test Case]

  * Compile tested
  * Boot tested
  * Tested by Google

  [Where things could go wrong]

  * Patches relatively isolated and maintain similar checking
  functionality, just earlier in boot. Likely a low chance of
  regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2037316/+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 2037650] Re: dkms-autopkgtest: avoid catching packages with -no-dkms in their name

** Patch added: "debdiff for focal"
   
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2037650/+attachment/5705147/+files/dkms_2.8.1-5ubuntu3.debdiff

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

Title:
  dkms-autopkgtest: avoid catching packages with -no-dkms in their name

Status in dkms package in Ubuntu:
  New
Status in dkms source package in Focal:
  New
Status in dkms source package in Jammy:
  New
Status in dkms source package in Lunar:
  New

Bug description:
  [Impact]

  The current version of dkms-autopkgtest in 20.04 and later selects
  binary packages with names ending with "-dkms" for its automatic DKMS
  test. This also includes packages such as nvidia-headless-535-no-dkms,
  which are not real dkms packages, and should not be tested
  automatically by autopkgtest.

  [Test Case]

  Run autopkgtest in Focal, or later, for nvidia-graphics-drivers-535,
  and the test will fail because of nvidia-headless-535-no-dkms not
  being an actual dkms package.

  https://kernel.ubuntu.com/adt-matrix/lunar-linux-meta.html

  [Where problems could occur]

  The main issue that we can experience is if the scripts dealt with
  other packages with "-no-dkms" in their name, which, for some reason,
  actually are DKMS packages, in which case, their testing would be
  skipped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2037650/+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 2037650] Re: dkms-autopkgtest: avoid catching packages with -no-dkms in their name

** Patch added: "debdiff for lunar"
   
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2037650/+attachment/5705149/+files/dkms_3.0.10-7ubuntu2.2.debdiff

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

Title:
  dkms-autopkgtest: avoid catching packages with -no-dkms in their name

Status in dkms package in Ubuntu:
  New
Status in dkms source package in Focal:
  New
Status in dkms source package in Jammy:
  New
Status in dkms source package in Lunar:
  New

Bug description:
  [Impact]

  The current version of dkms-autopkgtest in 20.04 and later selects
  binary packages with names ending with "-dkms" for its automatic DKMS
  test. This also includes packages such as nvidia-headless-535-no-dkms,
  which are not real dkms packages, and should not be tested
  automatically by autopkgtest.

  [Test Case]

  Run autopkgtest in Focal, or later, for nvidia-graphics-drivers-535,
  and the test will fail because of nvidia-headless-535-no-dkms not
  being an actual dkms package.

  https://kernel.ubuntu.com/adt-matrix/lunar-linux-meta.html

  [Where problems could occur]

  The main issue that we can experience is if the scripts dealt with
  other packages with "-no-dkms" in their name, which, for some reason,
  actually are DKMS packages, in which case, their testing would be
  skipped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2037650/+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 2037650] Re: dkms-autopkgtest: avoid catching packages with -no-dkms in their name

** Patch added: "debdiff for jammy"
   
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2037650/+attachment/5705148/+files/dkms_2.8.7-2ubuntu2.3.debdiff

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

Title:
  dkms-autopkgtest: avoid catching packages with -no-dkms in their name

Status in dkms package in Ubuntu:
  New
Status in dkms source package in Focal:
  New
Status in dkms source package in Jammy:
  New
Status in dkms source package in Lunar:
  New

Bug description:
  [Impact]

  The current version of dkms-autopkgtest in 20.04 and later selects
  binary packages with names ending with "-dkms" for its automatic DKMS
  test. This also includes packages such as nvidia-headless-535-no-dkms,
  which are not real dkms packages, and should not be tested
  automatically by autopkgtest.

  [Test Case]

  Run autopkgtest in Focal, or later, for nvidia-graphics-drivers-535,
  and the test will fail because of nvidia-headless-535-no-dkms not
  being an actual dkms package.

  https://kernel.ubuntu.com/adt-matrix/lunar-linux-meta.html

  [Where problems could occur]

  The main issue that we can experience is if the scripts dealt with
  other packages with "-no-dkms" in their name, which, for some reason,
  actually are DKMS packages, in which case, their testing would be
  skipped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2037650/+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 2037650] Re: dkms-autopkgtest: avoid catching packages with -no-dkms in their name

** Patch added: "debdiff for mantic"
   
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2037650/+attachment/5705150/+files/dkms_3.0.11-1ubuntu11.debdiff

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

Title:
  dkms-autopkgtest: avoid catching packages with -no-dkms in their name

Status in dkms package in Ubuntu:
  New
Status in dkms source package in Focal:
  New
Status in dkms source package in Jammy:
  New
Status in dkms source package in Lunar:
  New

Bug description:
  [Impact]

  The current version of dkms-autopkgtest in 20.04 and later selects
  binary packages with names ending with "-dkms" for its automatic DKMS
  test. This also includes packages such as nvidia-headless-535-no-dkms,
  which are not real dkms packages, and should not be tested
  automatically by autopkgtest.

  [Test Case]

  Run autopkgtest in Focal, or later, for nvidia-graphics-drivers-535,
  and the test will fail because of nvidia-headless-535-no-dkms not
  being an actual dkms package.

  https://kernel.ubuntu.com/adt-matrix/lunar-linux-meta.html

  [Where problems could occur]

  The main issue that we can experience is if the scripts dealt with
  other packages with "-no-dkms" in their name, which, for some reason,
  actually are DKMS packages, in which case, their testing would be
  skipped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2037650/+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 2037642] Re: [FFe] Raspberry Pi 5 support

2023-09-29 Thread Graham Inggs

FFe for linux-firmware-raspi in LP: #2037634

FFe for gpiozero in LP: #2037637


** No longer affects: linux-firmware-raspi (Ubuntu)

** Changed in: libcamera (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: linux-meta-raspi (Ubuntu)
   Status: Confirmed => Triaged

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

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: pipewire (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: rpi-eeprom (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: ubuntu-settings (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  [FFe] Raspberry Pi 5 support

Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Triaged
Status in linux-raspi package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in pipewire package in Ubuntu:
  Triaged
Status in rpi-eeprom package in Ubuntu:
  Triaged
Status in ubuntu-settings package in Ubuntu:
  Triaged

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 2037650] Re: dkms-autopkgtest: avoid catching packages with -no-dkms in their name

2023-09-29 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  dkms-autopkgtest: avoid catching packages with -no-dkms in their name

Status in dkms package in Ubuntu:
  New
Status in dkms source package in Focal:
  New
Status in dkms source package in Jammy:
  New
Status in dkms source package in Lunar:
  New

Bug description:
  [Impact]

  The current version of dkms-autopkgtest in 20.04 and later selects
  binary packages with names ending with "-dkms" for its automatic DKMS
  test. This also includes packages such as nvidia-headless-535-no-dkms,
  which are not real dkms packages, and should not be tested
  automatically by autopkgtest.

  [Test Case]

  Run autopkgtest in Focal, or later, for nvidia-graphics-drivers-535,
  and the test will fail because of nvidia-headless-535-no-dkms not
  being an actual dkms package.

  https://kernel.ubuntu.com/adt-matrix/lunar-linux-meta.html

  [Where problems could occur]

  The main issue that we can experience is if the scripts dealt with
  other packages with "-no-dkms" in their name, which, for some reason,
  actually are DKMS packages, in which case, their testing would be
  skipped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2037650/+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 2037667] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 2037667

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip
  link" that both tun0 and tun1 were not created.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+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 2037672] Re: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen

2023-09-29 Thread Johon Doee

Cannot deliver additional logs at the moment, though I think they might
not be necessary. Setting the bug to confirmed as stated by the Kernel
Bot.

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

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

Title:
  amdgpu: [gfxhub] page fault when switching a video to or from
  fullscreen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Switching a video to or from fullscreen freezes the screen for around
  10 seconds. This happens with Totem as well as VLC so its not related
  to a specific app.

  Additional observations:

  - The issue seems to be connected to the video's bitrate. With low
  bitrate videos I cannot trigger the freeze. However, videos with high
  bandwidth trigger the freeze reliably.

  Specs:
  Ubuntu 23.10 up to date as of 28.09.2023
  AMD Ryzen 7 PRO 6850U
  Kernel 6.5.0-5-generic
  Grub configured with: amdgpu.vm_update_mode=3

  Syslog shows:

  2023-09-28T20:02:29.803955+02:00 kernel: [27003.800898] amdgpu
  :04:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2
  pasid:32771, for process Xwayland pid 2113 thread Xwayland:cs0 pid
  2311)

  2023-09-28T20:02:39.975854+02:00 kernel: [27013.972772]
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but
  soft recovered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037672/+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 2037672] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 2037672

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  amdgpu: [gfxhub] page fault when switching a video to or from
  fullscreen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Switching a video to or from fullscreen freezes the screen for around
  10 seconds. This happens with Totem as well as VLC so its not related
  to a specific app.

  Additional observations:

  - The issue seems to be connected to the video's bitrate. With low
  bitrate videos I cannot trigger the freeze. However, videos with high
  bandwidth trigger the freeze reliably.

  Specs:
  Ubuntu 23.10 up to date as of 28.09.2023
  AMD Ryzen 7 PRO 6850U
  Kernel 6.5.0-5-generic
  Grub configured with: amdgpu.vm_update_mode=3

  Syslog shows:

  2023-09-28T20:02:29.803955+02:00 kernel: [27003.800898] amdgpu
  :04:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2
  pasid:32771, for process Xwayland pid 2113 thread Xwayland:cs0 pid
  2311)

  2023-09-28T20:02:39.975854+02:00 kernel: [27013.972772]
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but
  soft recovered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037672/+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 2037672] [NEW] amdgpu: [gfxhub] page fault when switching a video to or from fullscreen

2023-09-29 Thread Johon Doee

Public bug reported:

Hi,

Switching a video to or from fullscreen freezes the screen for around 10
seconds. This happens with Totem as well as VLC so its not related to a
specific app.

Additional observations:

- The issue seems to be connected to the video's bitrate. With low
bitrate videos I cannot trigger the freeze. However, videos with high
bandwidth trigger the freeze reliably.

Specs:
Ubuntu 23.10 up to date as of 28.09.2023
AMD Ryzen 7 PRO 6850U
Kernel 6.5.0-5-generic
Grub configured with: amdgpu.vm_update_mode=3

Syslog shows:

2023-09-28T20:02:29.803955+02:00 kernel: [27003.800898] amdgpu
:04:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2
pasid:32771, for process Xwayland pid 2113 thread Xwayland:cs0 pid 2311)

2023-09-28T20:02:39.975854+02:00 kernel: [27013.972772]
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but
soft recovered

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


** Tags: amdgpu fault freeze page ring

** Attachment added: "syslog.txt"
   https://bugs.launchpad.net/bugs/2037672/+attachment/5705176/+files/syslog.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/2037672

Title:
  amdgpu: [gfxhub] page fault when switching a video to or from
  fullscreen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Switching a video to or from fullscreen freezes the screen for around
  10 seconds. This happens with Totem as well as VLC so its not related
  to a specific app.

  Additional observations:

  - The issue seems to be connected to the video's bitrate. With low
  bitrate videos I cannot trigger the freeze. However, videos with high
  bandwidth trigger the freeze reliably.

  Specs:
  Ubuntu 23.10 up to date as of 28.09.2023
  AMD Ryzen 7 PRO 6850U
  Kernel 6.5.0-5-generic
  Grub configured with: amdgpu.vm_update_mode=3

  Syslog shows:

  2023-09-28T20:02:29.803955+02:00 kernel: [27003.800898] amdgpu
  :04:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2
  pasid:32771, for process Xwayland pid 2113 thread Xwayland:cs0 pid
  2311)

  2023-09-28T20:02:39.975854+02:00 kernel: [27013.972772]
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but
  soft recovered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037672/+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 2037667] [NEW] Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

Public bug reported:

We noticed that some of Netplan's integration tests started to fail on
Jammy. These tests will try to create ip6gre and vti6 virtual interfaces
and systemd-networkd is failing to create them starting on kernel
5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the last
revision where it works. So, some change between 5.15.0-82.91 and
5.15.0-83.92 is causing this regression.

How to reproduce the issue:

# Launch a jammy cloud VM:

lxc launch images:ubuntu/jammy/cloud jammy --vm
lxc shell jammy

# Create a netplan file that creates 2 tunnels:
 
cat > /etc/netplan/10-tun.yaml 2' && reboot

# Check with "ip link" again that both tun0 and tun1 were created

# Reboot again to go back to the most recent kernel and check with "ip
link" that both tun0 and tun1 were not created.

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

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

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

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip
  link" that both tun0 and tun1 were not created.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+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 2037688] [NEW] Pull-request to address TPM bypass issue

2023-09-29 Thread Brad Figg

Public bug reported:

NVIDIA: [Config]: Ensure the TPM is available before IMA initializes

Set the following configs:

  CONFIG_SPI_TEGRA210_QUAD=y
  CONFIG_TCG_TIS_SPI=y

On Grace systems, the IMA driver emits the following log:

  ima: No TPM chip found, activating TPM-bypass!

This occurs because the IMA driver initializes before we are able to detect
the TPM. This will always be the case when the drivers required to
communicate with the TPM, spi_tegra210_quad and tpm_tis_spi, are built as
modules.

Having these drivers as built-ins ensures that the TPM is available before
the IMA driver initializes.

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

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

Title:
  Pull-request to address TPM bypass issue

Status in linux-nvidia-6.2 package in Ubuntu:
  New

Bug description:
  NVIDIA: [Config]: Ensure the TPM is available before IMA
  initializes

  Set the following configs:

CONFIG_SPI_TEGRA210_QUAD=y
CONFIG_TCG_TIS_SPI=y

  On Grace systems, the IMA driver emits the following log:

ima: No TPM chip found, activating TPM-bypass!

  This occurs because the IMA driver initializes before we are able to 
detect
  the TPM. This will always be the case when the drivers required to
  communicate with the TPM, spi_tegra210_quad and tpm_tis_spi, are built as
  modules.

  Having these drivers as built-ins ensures that the TPM is available before
  the IMA driver initializes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2037688/+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 2006042] Re: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram

2023-09-29 Thread fernando

Hi!

Same here. I'm using ASUS UX533FD (Asus zenbook 15) with ubuntu 22.04.3
(LTS). Same pattern seen, but it happen (approx) each 3 times that I
suspend my laptop. Is really annoying.

Anyone found a workaround for this issue?

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

Title:
  [Asus ZenBook UX430UAR] Laptop often freezes after waking up from
  suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  After waking up from suspend to RAM, my computer actually wakes up but
  can sometimes then hang on a black screen (no prompt, nothing
  displayed, screen is active).

  This issue happens quite frequently but seems rather random. I think
  certain circumstances lower the frequency (I'll elaborate in the
  report).

  First of all, I'm not exactly sure when it started but I would say
  first notable frequent occurrences were around summer 2021 (yes, I'm
  late, sorry for that).

  When this happens, Algr+SysRQ+[usb] is unresponsive.

  -- EDIT --
  EDIT: This is actually not true. The laptop will eventually reboot by itself, 
and when this happens quickly enough after I have hit SysRq keys, it can be 
mistakenly taken for a working SysRq request.

  Or at least that's what I used to believe as it used to be true as I always 
tried from the laptop integrated keyboard. Until I connected an USB-C 
mechanical keyboard, from which I'm *sometimes* able to use the magic keys (not 
always, and with a lot of lag, but still).
  -- EDIT --

  If magic keys are unresponsive, I need to hard reset/long press power.
  There is nothing unusual before that in syslog nor kern.log, at least
  not that I know of. Except the ^@^@^@ characters when I had to hard
  reset the computer.

  If I leave the laptop like that for a while, it eventually reboots by
  itself and stays on the FDE passphrase prompt (which is not nice as
  the screen can then stay on for a very long like that if I did not
  notice).

  I'm running KDE/Plasma desktop, and this issue has happened regardless
  of the display manager. I used to run Xorg but now I'm on wayland
  flavor (mostly to alleviate firefox rendering/compositing issues).

  This also seems unrelated to external screen being connected or not,
  as it happened in the past regardless of that parameter. Although, it
  *seems* frequency has lowered a bit since I changed the way I wake up
  my laptop.

  Higher frequency (almost every day):
  - no external screen or external screen connected to HDMI port
  - waking up from integrated keyboard power button short press

  Lower frequency (one to multiple times a week, but somewhat irregular, since 
~ 2 months ago):
  - external screen connected to USB-C port
  - mechanical keyboard connected to USB-C port of screen
  - waking up from the mechanical keyboard

  It also seems to happen more frequently if I wake up the computer, do
  some very fast task and send it to sleep in under a few minutes. It's
  not guaranteed to happen, but seems to highly increase the
  probability.

  Also, this might be related so I'm adding that bit:

  I had to disable shutting the screen Off in energy saving settings, as
  enabling that option would trigger a similar behavior after a break
  long enough for that setting to trigger. I would come back on a laptop
  having self-rebooted and waiting for my input on the FDE passphrase
  prompt.

  During ACPI options testing, I noticed that setting might cause the
  sleep order to get cancelled. From that, I suspect in that case the
  laptop would go to sleep, then wake up immediately, which could have
  been triggering the bug as I described previously that rapid state
  changes would increase probability. Then as I described earlier, if I
  do nothing when this happens, the computer eventually reboots.

  This is only speculation as I'm usually not here to observe the
  behavior (this mostly happened during lunch breaks, which are long
  enough for all of these steps to happen).

  I disabled screen turn-off energy saving option a long while ago and
  have taken the habit of manually suspending to RAM when I intend on
  going away from the computer for more than a few minutes.

  As I described above, I've tried a few changes to check for behavior but that 
was a few months ago and I don't clearly remember all scenario. What I remember 
is that changing any of these did not resolve my issue and some even prevented 
my computer to even suspend to RAM properly (waking up immediately after). 
Among the options I tried is:
  - booting with a previous kernel, but then it's been happening for so long 
this would obviously not work (just for the sake of completion)
  - booting on latest mainstream kernel (tested 
linux-image-unsigned-6.0.9-060009-generic, this was the latest version when I

[Kernel-packages] [Bug 2020469] Re: Package ppc64el/s390x signing certs

Corresponding Jira item  is 'In Progress'.

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

Title:
  Package ppc64el/s390x signing certs

Status in Ubuntu CD Images:
  Fix Released
Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux-signed package in Ubuntu:
  Fix Committed
Status in s390-tools-signed package in Ubuntu:
  Fix Released

Bug description:
  Package ppc64el/s390x signing certs

  For ease of using signed boot on opal & sipl platforms, package and
  expose the signing certificate in .pem format in the .deb packages and
  on the isos.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/2020469/+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 2003674] Re: [23.10 FEAT] KVM: Enable Secure Execution Crypto Passthrough - kernel part

Updated to 'Fix Committed' since code is in mantic-proposed.

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

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

Title:
  [23.10 FEAT] KVM: Enable Secure Execution Crypto Passthrough - kernel
  part

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Feature Description:

  Enable KVM and QEMU for AP passthrough to Secure Execution guests.
  This includes setup, configuration and teardown of AP related
  resources.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003674/+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 2029390] Re: [23.10 FEAT] [SEC2352] pkey: support EP11 API ordinal 6 for secure guests

Updated to 'Fix Committed' since code is in mantic-proposed.

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

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

Title:
  [23.10 FEAT] [SEC2352] pkey: support EP11 API ordinal 6 for secure
  guests

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Secure Execution guests must use the EP11 API ordinal 6 to create (generate, 
unwrap, derive) secure keys which encodes a NULL PIN (no session) as a string 
of zero-bytes.
  Therefore, the pkey module must be updated to check whether the Linux system 
is running as a secure guest and if so modify secure key creating requests 
(key(pair) gen, unwrap) to use ordinal 6 API.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2029390/+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 2030924] Re: [SRU][Ubuntu 22.04.1] Unable to interpret the frequency values in cpuinfo_min_freq and cpuino_max_freq sysfs files.

2023-09-29 Thread Shubhakar Gowda P S

Hi,

Verified with lunar linux/6.2.0-34.34 kernel and got expected results.

** Tags removed: verification-needed-lunar-linux
** Tags added: verification-done-lunar-linux

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

Title:
  [SRU][Ubuntu 22.04.1] Unable to interpret the frequency values in
  cpuinfo_min_freq and cpuino_max_freq sysfs files.

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

Bug description:
  [Impact]

  On DELL EMC PowerEdge system when Ubuntu 22.04.1 OS is Installed,
  Unable to Interpret the values in cpuinfo_max_freq and
  cpuinfo_min_freq sysfs files as per the Intel specs document.

  Steps to Reproduce:

  1. Install one CPU that supports DBS "Demand-Based Power Management".
  2. Install Ubuntu 22.04.1 OS.
  2. Enable "Logical Processor" under CPU Information menu from F2 setup.
  3. Save changes and reboot to Ubuntu 22.04.1 OS.
  4. Right click on "Computer" and select "File system" and check for the 
following CPU directories.

     /sys/devices/system/cpu/cpu0/cpufreq/cpu0
     /sys/devices/system/cpu/cpu0/cpufreq/cpu1

  5. View the Max Frequency and Min Frequency under CPU0 and CPU1 directory.
  6. The Max and Min Frequency did not match as per the Intel specs datasheet.

  Actual results:

   /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 680
   /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 80
   /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 390

   Expected results: As per Intel datasheet specification.

   /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 5300 MHz
   /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 800 MHz
   /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 3000 MHz

  [Fix]
  cpufreq: intel_pstate: Fix scaling for hybrid-capable systems with disabled 
E-cores
  
https://github.com/torvalds/linux/commit/0fcfc9e51990246a9813475716746ff5eb98c6aa
 [github.com]

  [Test Plan]

  Same as steps to reproduce

  [ Where problems could occur ]

  This issue is seen on Intel based system under development which supports DBS 
"Demand-Based Power Management", then install Ubuntu-22.04 and boot into OS then
  check for the frequency values under /sys/devices/system/cpu/cpu0/cpufreq/cpu0
  Regression risk = Low to medium

  [ Other Info ]

  Jammy
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/cpuinfo_freq

  lunar
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/cpuinfo_freq_lunar_2

  Mantic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/cpuinfo_freq_mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030924/+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 2028937] Re: [23.10 FEAT] [SEC2341] pkey: support generation of keys of type PKEY_TYPE_EP11_AES

Updated to 'Fix Committed' since code is in mantic-proposed.

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

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

Title:
  [23.10 FEAT] [SEC2341] pkey: support generation of keys of type
  PKEY_TYPE_EP11_AES

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Add support to the pkey kernel module to generate keys of key type
  PKEY_TYPE_EP11_AES.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2028937/+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 2022361] Re: Please enable Renesas RZ platform serial installer