[Kernel-packages] [Bug 2017955] Re: Realtek Ethernet 8125 will disconnect randomly from Ethernet

[Richard Schneiderman]

[0.00] microcode: microcode updated early to revision 0x2c, date = 
2023-01-04
[0.00] Linux version 5.19.0-41-generic (buildd@lcy02-amd64-045) 
(x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04.1) 11.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.38) #42~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Apr 18 
17:40:00 UTC 2 (Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic 
root=UUID=4ea06ed3-2864-4051-ac24-61b09e04610d ro quiet splash
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Hygon HygonGenuine
[0.00]   Centaur CentaurHauls
[0.00]   zhaoxin   Shanghai  
[0.00] x86/split lock detection: #AC: crashing the kernel on kernel 
split_locks and warning on user-space split_locks
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User 
registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[9]:  832, xstate_sizes[9]:8
[0.00] x86/fpu: Enabled xstate features 0x207, context size is 840 
bytes, using 'compacted' format.
[0.00] signal: max sigframe size: 3632
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009dfff] usable
[0.00] BIOS-e820: [mem 0x0009e000-0x0009efff] reserved
[0.00] BIOS-e820: [mem 0x0009f000-0x0009] usable
[0.00] BIOS-e820: [mem 0x000a-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x321d1fff] usable
[0.00] BIOS-e820: [mem 0x321d2000-0x352d1fff] reserved
[0.00] BIOS-e820: [mem 0x352d2000-0x3553afff] ACPI data
[0.00] BIOS-e820: [mem 0x3553b000-0x355fafff] ACPI NVS
[0.00] BIOS-e820: [mem 0x355fb000-0x35ffefff] reserved
[0.00] BIOS-e820: [mem 0x35fff000-0x35ff] usable
[0.00] BIOS-e820: [mem 0x3600-0x39ff] reserved
[0.00] BIOS-e820: [mem 0x3aa0-0x3abf] reserved
[0.00] BIOS-e820: [mem 0x3b00-0x403f] reserved
[0.00] BIOS-e820: [mem 0xc000-0xcfff] reserved
[0.00] BIOS-e820: [mem 0xfc00-0xfc00] reserved
[0.00] BIOS-e820: [mem 0xfe00-0xfe010fff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfed0-0xfed00fff] reserved
[0.00] BIOS-e820: [mem 0xfed2-0xfed7] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xff00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x0002bfbf] usable
[0.00] NX (Execute Disable) protection: active
[0.00] e820: update [mem 0x2bd99018-0x2bda6857] usable ==> usable
[0.00] e820: update [mem 0x2bd99018-0x2bda6857] usable ==> usable
[0.00] extended physical RAM map:
[0.00] reserve setup_data: [mem 0x-0x0009dfff] 
usable
[0.00] reserve setup_data: [mem 0x0009e000-0x0009efff] 
reserved
[0.00] reserve setup_data: [mem 0x0009f000-0x0009] 
usable
[0.00] reserve setup_data: [mem 0x000a-0x000f] 
reserved
[0.00] reserve setup_data: [mem 0x0010-0x2bd99017] 
usable
[0.00] reserve setup_data: [mem 0x2bd99018-0x2bda6857] 
usable
[0.00] reserve setup_data: [mem 0x2bda6858-0x321d1fff] 
usable
[0.00] reserve setup_data: [mem 0x321d2000-0x352d1fff] 
reserved
[0.00] reserve setup_data: [mem 0x352d2000-0x3553afff] 
ACPI data
[0.00] reserve setup_data: [mem 0x3553b000-0x355fafff] 
ACPI NVS
[0.00] reserve setup_data: [mem 0x355fb000-0x35ffefff] 
reserved
[0.00] reserve setup_data: [mem 0x35fff000-0x35ff] 
usable
[0.00] reserve setup_data: [mem 0x3600-0x39ff] 
reserved
[0.00] reserve setup_data: [mem 0x3aa0-0x3abf] 
reserved
[0.00] reserve setup_data: [mem 0x3b00-0x403f] 
reserved
[0.00] reserve setup_data: [mem 0xc000-0xcfff] 
reserved
[0.00] reserve setup_data: [mem 0xfc00-0xfc00] 
reserved

[Kernel-packages] [Bug 2018169] [NEW] package linux-headers-6.2.0-1004-raspi 6.2.0-1004.5 failed to install/upgrade: installed linux-headers-6.2.0-1004-raspi package post-installation script subproces

[User]

Public bug reported:

Attempting to upgrade this devices kernel results in failure.

While testing I've fixed this.

It appears the hello-dkms module and package were causing the issue.

Mark as solved.

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-1004-raspi 6.2.0-1004.5
ProcVersionSignature: Ubuntu 5.15.0-1027.29-raspi 5.15.92
Uname: Linux 5.15.0-1027-raspi aarch64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
ApportVersion: 2.26.1-0ubuntu2
Architecture: arm64
CasperMD5CheckResult: unknown
CloudBuildName: server
CloudSerial:
 
Date: Sat Apr 29 03:14:41 2023
ErrorMessage: installed linux-headers-6.2.0-1004-raspi package 
post-installation script subprocess returned error exit status 1
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.11.1-3
RelatedPackageVersions:
 dpkg 1.21.21ubuntu1
 apt  2.4.9
SourcePackage: linux-raspi
Title: package linux-headers-6.2.0-1004-raspi 6.2.0-1004.5 failed to 
install/upgrade: installed linux-headers-6.2.0-1004-raspi package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to lunar on 2021-12-17 (498 days ago)

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


** Tags: apport-package arm64 cloud-image lunar third-party-packages

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

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

Title:
  package linux-headers-6.2.0-1004-raspi 6.2.0-1004.5 failed to
  install/upgrade: installed linux-headers-6.2.0-1004-raspi package
  post-installation script subprocess returned error exit status 1

Status in linux-raspi package in Ubuntu:
  Invalid

Bug description:
  Attempting to upgrade this devices kernel results in failure.

  While testing I've fixed this.

  It appears the hello-dkms module and package were causing the issue.

  Mark as solved.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-1004-raspi 6.2.0-1004.5
  ProcVersionSignature: Ubuntu 5.15.0-1027.29-raspi 5.15.92
  Uname: Linux 5.15.0-1027-raspi aarch64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudBuildName: server
  CloudSerial:
   
  Date: Sat Apr 29 03:14:41 2023
  ErrorMessage: installed linux-headers-6.2.0-1004-raspi package 
post-installation script subprocess returned error exit status 1
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.11.1-3
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.4.9
  SourcePackage: linux-raspi
  Title: package linux-headers-6.2.0-1004-raspi 6.2.0-1004.5 failed to 
install/upgrade: installed linux-headers-6.2.0-1004-raspi package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2021-12-17 (498 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2018169/+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 2017846] Re: System kept waking up after pressing power button

[Jonas Gamao]

** Attachment added: "systemd-logind-log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017846/+attachment/5669710/+files/systemd-logind-log.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/2017846

Title:
  System kept waking up after pressing power button

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Tried it 3 times in the last 15min, each time it keeps waking back up.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yamiyuki  42974 F wireplumber
   /dev/snd/controlC3:  yamiyuki  42974 F wireplumber
   /dev/snd/controlC0:  yamiyuki  42974 F wireplumber
   /dev/snd/seq:yamiyuki  42972 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Apr 27 00:45:37 2023
  InstallationDate: Installed on 2022-01-14 (468 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro 
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x 
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago)
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F5a
  dmi.board.asset.tag: Default string
  dmi.board.name: X570S AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570S AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2022-01-14 (468 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER
  Package: systemd 252.5-2ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro 
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x 
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F5a
  dmi.board.asset.tag: Default string
  dmi.board.name: X570S AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Kernel-packages] [Bug 2017790] Re: Intel Wi-Fi 6 AX201 failing in 23.04

[David Roche]

Windows was installed but it’s removed now. I have seen suggestions to
create a bootable usb to disable the WiFi adapter but I’m not sure if
that would work

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

Title:
  Intel Wi-Fi 6 AX201 failing in 23.04

Status in linux-lowlatency package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 22.04 to 23.04 the intel wifi driver is not
  loading, I am seeing the following in dmesg:

  [  215.024382] Loading of unsigned module is rejected
  [  262.051998] [ cut here ]
  [  262.052001] WARNING: CPU: 2 PID: 6946 at net/netlink/genetlink.c:570 
genl_validate_ops+0x1cc/0x270
  [  262.052007] Modules linked in: cfg80211(O+) rfcomm xt_conntrack 
nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc 
vmw_vsock_vmci_transport vsock vmw_vmci snd_seq_dummy snd_hrtimer overlay cmac 
algif_hash algif_skcipher af_alg bnep dell_rbu typec_displayport 
snd_hda_codec_hdmi snd_ctl_led binfmt_misc snd_hda_codec_realtek 
snd_hda_codec_generic snd_sof_pci_intel_tgl snd_sof_intel_hda_common 
soundwire_intel hid_logitech_hidpp soundwire_generic_allocation nls_iso8859_1 
soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof 
snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match 
snd_soc_acpi soundwire_bus snd_soc_core snd_compress ac97_bus 
x86_pkg_temp_thermal r8153_ecm snd_pcm_dmaengine intel_powerclamp cdc_ether 
coretemp snd_hda_intel usbnet snd_usb_audio kvm_intel snd_intel_dspcfg r8152 
snd_intel_sdw_acpi
  [  262.052038]  mii hid_plantronics hid_logitech_dj snd_usbmidi_lib 
snd_hda_codec kvm snd_hda_core snd_hwdep irqbypass mei_hdcp mei_pxp 
intel_rapl_msr dell_laptop snd_pcm crct10dif_pclmul i915 polyval_clmulni 
snd_seq_midi polyval_generic snd_seq_midi_event ghash_clmulni_intel 
sha512_ssse3 snd_rawmidi uvcvideo btusb videobuf2_vmalloc 
hid_sensor_custom_intel_hinge aesni_intel hid_sensor_gyro_3d 
hid_sensor_accel_3d dell_wmi videobuf2_memops snd_seq crypto_simd 
hid_sensor_trigger btrtl drm_buddy snd_seq_device btbcm videobuf2_v4l2 btintel 
processor_thermal_device_pci_legacy cryptd cmdlinepart 
industrialio_triggered_buffer dell_smbios rapl dcdbas snd_timer ttm 
dell_wmi_sysman btmtk videodev kfifo_buf spi_nor processor_thermal_device 
hid_sensor_iio_common processor_thermal_rfim intel_cstate 
firmware_attributes_class ledtrig_audio drm_display_helper dell_wmi_descriptor 
wmi_bmof industrialio mei_me mtd bluetooth snd videobuf2_common mc cec 
processor_thermal_mbox soundcore rc_core mei ecdh_generic
  [  262.052068]  processor_thermal_rapl iwlwifi_compat(O) drm_kms_helper ecc 
ucsi_acpi joydev i2c_algo_bit intel_rapl_common typec_ucsi syscopyarea 
intel_soc_dts_iosf sysfillrect typec sysimgblt igen6_edac int3403_thermal 
soc_button_array int340x_thermal_zone int3400_thermal intel_hid 
acpi_thermal_rel acpi_pad acpi_tad sparse_keymap hid_multitouch input_leds 
mac_hid serio_raw msr parport_pc ppdev drm lp parport efi_pstore dmi_sysfs 
ip_tables x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid hid_generic nvme nvme_core intel_ish_ipc i2c_hid_acpi 
spi_intel_pci rtsx_pci_sdmmc crc32_pclmul video i2c_i801 i2c_hid intel_lpss_pci 
xhci_pci spi_intel intel_ishtp nvme_common thunderbolt psmouse i2c_smbus 
intel_lpss rtsx_pci idma64 xhci_pci_renesas hid wmi pinctrl_tigerlake
  [  262.052097] CPU: 2 PID: 6946 Comm: modprobe Tainted: GW  O   
6.2.0-1003-lowlatency #3-Ubuntu
  [  262.052098] Hardware name: Dell Inc. Latitude 7420/07MHG4, BIOS 1.24.2 
02/24/2023
  [  262.052099] RIP: 0010:genl_validate_ops+0x1cc/0x270
  [  262.052102] Code: 81 c4 d8 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 
c9 31 ff c3 cc cc cc cc 49 83 7d 50 00 0f 85 b9 fe ff ff 0f 0b eb bd <0f> 0b eb 
b9 0f 0b eb b5 0f 0b eb b1 45 84 ff 75 04 31 c0 eb ad 4d
  [  262.052103] RSP: 0018:a91bc7103a88 EFLAGS: 00010206
  [  262.052105] RAX: 0003 RBX: a91bc7103af0 RCX: 

  [  262.052106] RDX:  RSI:  RDI: 

  [  262.052106] RBP: a91bc7103b88 R08:  R09: 

  [  262.052107] R10:  R11:  R12: 
0001
  [  262.052107] R13: c1824780 R14: a91bc7103a88 R15: 

  [  262.052108] FS:  7fd67c380040() GS:8fcc7f68() 
knlGS:
  [  262.052109] CS:  0010 DS:  ES:  CR0: 80050033
  [  262.052110] CR2: 7fff38c0e848 CR3: 00010a938006 CR4: 
00770ee0
  [  262.052111] PKRU: 5554
  [  262.052112] Call Trace:
  [  262.052113]  
  [  262.052115]  ? __pfx_nl80211_pre_doit+0x10/0x10 [cfg80211]
  [  262.052146]  

[Kernel-packages] [Bug 2018125] Missing required logs.

[Ubuntu Kernel Bot]

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 2018125

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

Title:
  do-release-upgrade fails due to full zfs partition

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I used do-release-upgrade to upgrade from 22.10 x86-64 to 23.10.
  Towards the end of the upgrade, it rebooted, but stuck me in the recovery 
console.
  I enabled networking and opened a root shell.
  1. Networking was not working. I fiddled with this for days, and could not 
get networking working. I tried starting NetworkManager, playing with rfkill, 
and a few other things, but, ultimately, could not get networking working.
  2. The problem that seemed to kill the upgrade was the zfs boot partition 
being too full for the new image, even though the new image was present. After 
a few days I found a way to remove old snapshots and created lots of free space 
on /boot. Linux still doesn't boot.

  Ultimately, if FOSS is supposed to be a good thing, and attract non-
  sysadmins, it should be easy to install/upgrade.

  1. do-release-upgrade should be able to deal with full filesystems,
  whether they're zfs or ext4 or the other front-running file systems,
  giving the user the tools to remove snapshots and/or files to make the
  new upgrade/release work as flawlessly as it can. I should be able to
  convert a zfs partition to ext4, (or vice versa) and get on with my
  real work.

  2. When the user is dumped into the recovery console, give him more
  tools to work with. There should be, at the very least, a way to get
  the network working when you press "enable networking" (not by having
  to download and figure out how to use network-tools, ifconfig, rfkill,
  dhclient, etc.), and deal with and fix ZFS issues.

  I know this isn't going to be fixed by the weekend, so I'm considering
  3 "nuclear" options, in decreasing order of desirability: (1) reformat
  the zfs boot partition as ext4, then copy the (saved) contents of
  /boot into the pristine partition. (2) Reinstall 23.04 from the thumb
  drive. I learned, decades ago, to keep my user partition on a separate
  drive, so it should be safe. What I'll lose is my network and wifi
  settings and printer setups. There are, undoubtedly other things that
  will have to be recovered, but those are the most important. (3) Pay
  through the nose for an Apple. I'd have to learn a new UI and transfer
  my files somehow, and bow down to my kids who have been pushing for me
  to get off this old Linux thing. "You'll have to pry my cold dead
  fingers off my Linux computers..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018125/+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 2018125] Re: do-release-upgrade fails due to full zfs partition

[Chelmite]

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  do-release-upgrade fails due to full zfs partition

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I used do-release-upgrade to upgrade from 22.10 x86-64 to 23.10.
  Towards the end of the upgrade, it rebooted, but stuck me in the recovery 
console.
  I enabled networking and opened a root shell.
  1. Networking was not working. I fiddled with this for days, and could not 
get networking working. I tried starting NetworkManager, playing with rfkill, 
and a few other things, but, ultimately, could not get networking working.
  2. The problem that seemed to kill the upgrade was the zfs boot partition 
being too full for the new image, even though the new image was present. After 
a few days I found a way to remove old snapshots and created lots of free space 
on /boot. Linux still doesn't boot.

  Ultimately, if FOSS is supposed to be a good thing, and attract non-
  sysadmins, it should be easy to install/upgrade.

  1. do-release-upgrade should be able to deal with full filesystems,
  whether they're zfs or ext4 or the other front-running file systems,
  giving the user the tools to remove snapshots and/or files to make the
  new upgrade/release work as flawlessly as it can. I should be able to
  convert a zfs partition to ext4, (or vice versa) and get on with my
  real work.

  2. When the user is dumped into the recovery console, give him more
  tools to work with. There should be, at the very least, a way to get
  the network working when you press "enable networking" (not by having
  to download and figure out how to use network-tools, ifconfig, rfkill,
  dhclient, etc.), and deal with and fix ZFS issues.

  I know this isn't going to be fixed by the weekend, so I'm considering
  3 "nuclear" options, in decreasing order of desirability: (1) reformat
  the zfs boot partition as ext4, then copy the (saved) contents of
  /boot into the pristine partition. (2) Reinstall 23.04 from the thumb
  drive. I learned, decades ago, to keep my user partition on a separate
  drive, so it should be safe. What I'll lose is my network and wifi
  settings and printer setups. There are, undoubtedly other things that
  will have to be recovered, but those are the most important. (3) Pay
  through the nose for an Apple. I'd have to learn a new UI and transfer
  my files somehow, and bow down to my kids who have been pushing for me
  to get off this old Linux thing. "You'll have to pry my cold dead
  fingers off my Linux computers..."

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

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Could not install 'linux-headers-6.2.0-20-generic'

  The upgrade will continue but the 'linux-headers-6.2.0-20-generic'
  package may not be in a working state. Please consider submitting a
  bug report about it.

  installed linux-headers-6.2.0-20-generic package post-installation
  script subprocess returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tvseshagiri   6954 F pulseaudio
   /dev/snd/controlC1:  tvseshagiri   6954 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Sat Apr 29 22:20:38 2023
  ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic 
root=UUID=9bd103d7-5d7c-4388-be11-65d097838992 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: /usr/bin/python3.11, Python 3.11.2, unpackaged
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-04-29 (0 days ago)
  dmi.bios.date: 09/06/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1007
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME H310M-E R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1007:bd09/06/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH310M-ER2.0:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018154/+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 2017790] Re: Intel Wi-Fi 6 AX201 failing in 23.04

[Jeremy]

David, is Windows installed also?

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

Title:
  Intel Wi-Fi 6 AX201 failing in 23.04

Status in linux-lowlatency package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 22.04 to 23.04 the intel wifi driver is not
  loading, I am seeing the following in dmesg:

  [  215.024382] Loading of unsigned module is rejected
  [  262.051998] [ cut here ]
  [  262.052001] WARNING: CPU: 2 PID: 6946 at net/netlink/genetlink.c:570 
genl_validate_ops+0x1cc/0x270
  [  262.052007] Modules linked in: cfg80211(O+) rfcomm xt_conntrack 
nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc 
vmw_vsock_vmci_transport vsock vmw_vmci snd_seq_dummy snd_hrtimer overlay cmac 
algif_hash algif_skcipher af_alg bnep dell_rbu typec_displayport 
snd_hda_codec_hdmi snd_ctl_led binfmt_misc snd_hda_codec_realtek 
snd_hda_codec_generic snd_sof_pci_intel_tgl snd_sof_intel_hda_common 
soundwire_intel hid_logitech_hidpp soundwire_generic_allocation nls_iso8859_1 
soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof 
snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match 
snd_soc_acpi soundwire_bus snd_soc_core snd_compress ac97_bus 
x86_pkg_temp_thermal r8153_ecm snd_pcm_dmaengine intel_powerclamp cdc_ether 
coretemp snd_hda_intel usbnet snd_usb_audio kvm_intel snd_intel_dspcfg r8152 
snd_intel_
 sdw_acpi
  [  262.052038]  mii hid_plantronics hid_logitech_dj snd_usbmidi_lib 
snd_hda_codec kvm snd_hda_core snd_hwdep irqbypass mei_hdcp mei_pxp 
intel_rapl_msr dell_laptop snd_pcm crct10dif_pclmul i915 polyval_clmulni 
snd_seq_midi polyval_generic snd_seq_midi_event ghash_clmulni_intel 
sha512_ssse3 snd_rawmidi uvcvideo btusb videobuf2_vmalloc 
hid_sensor_custom_intel_hinge aesni_intel hid_sensor_gyro_3d 
hid_sensor_accel_3d dell_wmi videobuf2_memops snd_seq crypto_simd 
hid_sensor_trigger btrtl drm_buddy snd_seq_device btbcm videobuf2_v4l2 btintel 
processor_thermal_device_pci_legacy cryptd cmdlinepart 
industrialio_triggered_buffer dell_smbios rapl dcdbas snd_timer ttm 
dell_wmi_sysman btmtk videodev kfifo_buf spi_nor processor_thermal_device 
hid_sensor_iio_common processor_thermal_rfim intel_cstate 
firmware_attributes_class ledtrig_audio drm_display_helper dell_wmi_descriptor 
wmi_bmof industrialio mei_me mtd bluetooth snd videobuf2_common mc cec 
processor_thermal_mbox soundcore rc_core mei ecdh_
 generic
  [  262.052068]  processor_thermal_rapl iwlwifi_compat(O) drm_kms_helper ecc 
ucsi_acpi joydev i2c_algo_bit intel_rapl_common typec_ucsi syscopyarea 
intel_soc_dts_iosf sysfillrect typec sysimgblt igen6_edac int3403_thermal 
soc_button_array int340x_thermal_zone int3400_thermal intel_hid 
acpi_thermal_rel acpi_pad acpi_tad sparse_keymap hid_multitouch input_leds 
mac_hid serio_raw msr parport_pc ppdev drm lp parport efi_pstore dmi_sysfs 
ip_tables x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid hid_generic nvme nvme_core intel_ish_ipc i2c_hid_acpi 
spi_intel_pci rtsx_pci_sdmmc crc32_pclmul video i2c_i801 i2c_hid intel_lpss_pci 
xhci_pci spi_intel intel_ishtp nvme_common thunderbolt psmouse i2c_smbus 
intel_lpss rtsx_pci idma64 xhci_pci_renesas hid wmi pinctrl_tigerlake
  [  262.052097] CPU: 2 PID: 6946 Comm: modprobe Tainted: GW  O   
6.2.0-1003-lowlatency #3-Ubuntu
  [  262.052098] Hardware name: Dell Inc. Latitude 7420/07MHG4, BIOS 1.24.2 
02/24/2023
  [  262.052099] RIP: 0010:genl_validate_ops+0x1cc/0x270
  [  262.052102] Code: 81 c4 d8 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 
c9 31 ff c3 cc cc cc cc 49 83 7d 50 00 0f 85 b9 fe ff ff 0f 0b eb bd <0f> 0b eb 
b9 0f 0b eb b5 0f 0b eb b1 45 84 ff 75 04 31 c0 eb ad 4d
  [  262.052103] RSP: 0018:a91bc7103a88 EFLAGS: 00010206
  [  262.052105] RAX: 0003 RBX: a91bc7103af0 RCX: 

  [  262.052106] RDX:  RSI:  RDI: 

  [  262.052106] RBP: a91bc7103b88 R08:  R09: 

  [  262.052107] R10:  R11:  R12: 
0001
  [  262.052107] R13: c1824780 R14: a91bc7103a88 R15: 

  [  262.052108] FS:  7fd67c380040() GS:8fcc7f68() 
knlGS:
  [  262.052109] CS:  0010 DS:  ES:  CR0: 80050033
  [  262.052110] CR2: 7fff38c0e848 CR3: 00010a938006 CR4: 
00770ee0
  [  262.052111] PKRU: 5554
  [  262.052112] Call Trace:
  [  262.052113]  
  [  262.052115]  ? __pfx_nl80211_pre_doit+0x10/0x10 [cfg80211]
  [  262.052146]  ? __pfx_nl80211_get_wiphy+0x10/0x10 [cfg80211]
  [  262.052171]  ? __pfx_nl80211_post_doit+0x10/0x10 [cfg80211]
  [  

[Kernel-packages] [Bug 2018154] Status changed to Confirmed

[Ubuntu Kernel Bot]

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Could not install 'linux-headers-6.2.0-20-generic'

  The upgrade will continue but the 'linux-headers-6.2.0-20-generic'
  package may not be in a working state. Please consider submitting a
  bug report about it.

  installed linux-headers-6.2.0-20-generic package post-installation
  script subprocess returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tvseshagiri   6954 F pulseaudio
   /dev/snd/controlC1:  tvseshagiri   6954 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Sat Apr 29 22:20:38 2023
  ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic 
root=UUID=9bd103d7-5d7c-4388-be11-65d097838992 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: /usr/bin/python3.11, Python 3.11.2, unpackaged
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-04-29 (0 days ago)
  dmi.bios.date: 09/06/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1007
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME H310M-E R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1007:bd09/06/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH310M-ER2.0:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018154/+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 2017444] Re: Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20

[Jan Saarinen]

** Description changed:

  Computers with Intel Atom CPU will not boot with Kernel 6.2.0-20 OR any
  other Kernel in 6.2 series or Kernel 6.3.0.
  
  This bug affects all Intel Atom CPU computers in all Linux distributions
  making impossible to install or boot to OS with kernel 6.2 or higher.
  
- NOTICE TO UBUNTU KERNEL MAINTAINERS, April 29th:
+ NEW SOLUTION AND NOTICE TO UBUNTU KERNEL MAINTAINERS, April 29th:
  The following persons are in charge of atomisp kernel development:
  
  Hans de Goede  (maintainer:STAGING - ATOMISP DRIVER)
  Mauro Carvalho Chehab  (maintainer:STAGING - ATOMISP 
DRIVER)
  Sakari Ailus  (reviewer:STAGING - ATOMISP 
DRIVER)
  Greg Kroah-Hartman  (supporter:STAGING SUBSYSTEM)
  linux-me...@vger.kernel.org (open list:STAGING - ATOMISP DRIVER)
  linux-stag...@lists.linux.dev (open list:STAGING SUBSYSTEM)
  linux-ker...@vger.kernel.org (open list)
  
- April 29th Hans de Goede adviced me personally( 
https://github.com/linux-surface/linux-surface/issues/1095 ), that 
shisp_2401a0_v21.bin driver is still in development and should be disabled. 
Since this driver is already missing in Ubuntu kernel- there is nothing to 
disable.
- Therefore the only -and best - solution is to disable atomisp modules in 
kernel.
+ April 29th Hans de Goede adviced me personally(
+ https://github.com/linux-surface/linux-surface/issues/1095 ), that
+ atomisp driver is still in development and should be disabled. By
+ disabling driver he meant disabling atomisp modules in kernel.
  
- SOLUTION FOR THIS BUG IS FOUND:
+ OLD SOLUTION FOR THIS BUG:
  
  Copying (installing) file shisp_2401a0_v21.bin from:
  
  https://github.com/intel-aero/meta-intel-aero-base/blob/master/recipes-
  kernel/linux/linux-yocto/shisp_2401a0_v21.bin
  
  to /lib/firmware will solve the bug (partially - it still gives error
  messages - but at least the computer boots).**
  
  (dmesg.log with shisp-file with kernel 6.2.0-06 and 6.3.0-06 as
  attachments 9. and 10.)
  
  (Another solution - which Manjaro kernel maintainer did - was to disable
  atomisp and related modules).
  
  Afterwards Intel Atom CPU computer will be able to boot with kernel 6.2.
  
  MORE INFORMATION IN: https://askubuntu.com/questions/1464926/not-able-
  to-boot-kubuntu-23-04-with-kernel-6-2-and-intel-atom-cpu
  
  The last stable Ubuntu Kernel Intel Atom CPU computer will boot with is
  6.1.25.
  
  The bug is caused by Intel atomisp camera driver module which has driver
  missing: shisp_2401a_v21.bin.
  
  This bug was already in 5.19, as you can see from dmesg.logs. It appears
  that atomisp failes to launch in both 5.19.0-40 and 6.1.25 but still the
  computer boots.
  
  This bug is also reported in Manjaro ( " https://github.com/linux-
  surface/linux-surface/issues/1095 ")and Arch Linux ("
  https://bbs.archlinux.org/viewtopic.php?id=283920 ") so it is not
  limited to Ubuntu Kernels.
  
  This bug has already been reported for Ubuntu 23.04 Beta in Ubuntu
  bugtracking system (" https://www.mail-archive.com/kernel-
  packa...@lists.launchpad.net/msg501664.html ") with Bug number #2015794.
  
  Attachments:
  1. Picture of stuck boot sequence of HP x2 210 G2 with Intel Atom CPU trying 
to boot in to Kubuntu 23.04 with Kernel 6.2.0-20.
  
  2. dmesg.log of the computer with Ubuntu Kernel 6.1.25.
  3. xsession-errors of the computer with Ubuntu Kernel 6.1.25.
  4. dmesg.log of the computer with Ubuntu Kernel 5.19.0-40.
  5. Video of boot sequence with Kernel 6.2.0-20.
  6. uname-a.log of Kernel 6.1.25.
  7. lspci-vvnn.log of Kernel 6.1.25.
  8. version.log of Kernel 5.19.0-40.
  9. dmesg.log with shisp-file with ubuntu kernel 6.2.0-06.**
  10. dmesg.log with shisp-file with ubuntu kernel 6.3.0-06**
  
  P.S. The apport-collect data is from Kernel 5.19.0-40.
  P.S.P.S I had difficulty determining Tags so they are to be changed by you.

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

Title:
  Computer with Intel Atom CPU will  not boot with Kernel 6.2.0-20

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Computers with Intel Atom CPU will not boot with Kernel 6.2.0-20 OR
  any other Kernel in 6.2 series or Kernel 6.3.0.

  This bug affects all Intel Atom CPU computers in all Linux
  distributions making impossible to install or boot to OS with kernel
  6.2 or higher.

  NEW SOLUTION AND NOTICE TO UBUNTU KERNEL MAINTAINERS, April 29th:
  The following persons are in charge of atomisp kernel development:

  Hans de Goede  (maintainer:STAGING - ATOMISP DRIVER)
  Mauro Carvalho Chehab  (maintainer:STAGING - ATOMISP 
DRIVER)
  Sakari Ailus  (reviewer:STAGING - ATOMISP 
DRIVER)
  Greg Kroah-Hartman  (supporter:STAGING SUBSYSTEM)
  linux-me...@vger.kernel.org (open list:STAGING - ATOMISP DRIVER)
  linux-stag...@lists.linux.dev (open list:STAGING SUBSYSTEM)
  

[Kernel-packages] [Bug 2018154] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess

[Seshagiri]

Public bug reported:

Could not install 'linux-headers-6.2.0-20-generic'

The upgrade will continue but the 'linux-headers-6.2.0-20-generic'
package may not be in a working state. Please consider submitting a bug
report about it.

installed linux-headers-6.2.0-20-generic package post-installation
script subprocess returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tvseshagiri   6954 F pulseaudio
 /dev/snd/controlC1:  tvseshagiri   6954 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: unknown
Date: Sat Apr 29 22:20:38 2023
ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
MachineType: System manufacturer System Product Name
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic 
root=UUID=9bd103d7-5d7c-4388-be11-65d097838992 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: /usr/bin/python3.11, Python 3.11.2, unpackaged
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.06-2ubuntu16
SourcePackage: linux
Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to lunar on 2023-04-29 (0 days ago)
dmi.bios.date: 09/06/2019
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1007
dmi.board.asset.tag: Default string
dmi.board.name: PRIME H310M-E R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1007:bd09/06/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH310M-ER2.0:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

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


** Tags: amd64 apport-package lunar

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Could not install 'linux-headers-6.2.0-20-generic'

  The upgrade will continue but the 'linux-headers-6.2.0-20-generic'
  package may not be in a working state. Please consider submitting a
  bug report about it.

  installed linux-headers-6.2.0-20-generic package post-installation
  script subprocess returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tvseshagiri   6954 F pulseaudio
   /dev/snd/controlC1:  tvseshagiri   6954 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Sat Apr 29 22:20:38 2023
  ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic 
root=UUID=9bd103d7-5d7c-4388-be11-65d097838992 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: /usr/bin/python3.11, Python 3.11.2, unpackaged
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package 

[Kernel-packages] [Bug 1980831] Re: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!

[-]

OP from Gitlab here, just updated to Ubuntu 23.04 and am currently
running kernel 6.2.0-20-generic.

I still had the issue until 5.19.0-41-generic.

So far the system has only crashed once, but it was after reboot, all
the screens stopped working, but then the screen connected to the nvidia
gpu came back, everything else connected to amd gpu stayed frozen, and
then nvidia screen stopped working as well.

xsystem boot  6.2.0-20-generic Sat Apr 29 12:06   still running
x:0   :0   Sat Apr 29 11:55 - crash  (00:11)
xseat0login screen Sat Apr 29 11:55 - crash  (00:11)
reboot   system boot  6.2.0-20-generic Sat Apr 29 11:55   still running
reboot   system boot  5.19.0-41-generi Sat Apr 29 10:11 - 11:53  (01:42)
reboot   system boot  5.19.0-41-generi Sat Apr 29 10:05 - 10:06  (00:00)
reboot   system boot  5.19.0-38-generi Sat Apr  8 22:11 - 10:03 (20+11:52)
reboot   system boot  5.19.0-38-generi Sat Apr  8 22:01 - 22:02  (00:00)
reboot   system boot  5.19.0-38-generi Sat Apr  8 21:59 - 22:01  (00:01)
reboot   system boot  5.19.0-38-generi Wed Mar 22 20:56 - 21:56 (17+01:00)

I wasn't able to get any logs that might explain the crash, but I will
keep you posted if this solved the initial issue I'm having.

If issues start happening again, I'll go back to testing bleeding edge
amd drivers on kisak repo.

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

Title:
  GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]]
  *ERROR* Waiting for fences timed out!

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  When working normally, random freezes happen. Everything freezes,
  except the mouse cursor.

  I tried from keyboard to: switch to another window, start a terminal,
  run a command to restart gnome, enabled ctrl+alt+backspace and tried
  it to restart X windows, ctrl+alt+delete, switch to another session
  with ctrl+alt+F1-F9 - nothing works.

  If I'm listening to something, the sound goes on for a while;
  sometimes it stops by itself, other times it keeps going.

  The only way to recover that I've found is to stop the laptop from the
  power button.

  For a while I thought it was due to firefox; I installed the deb
  version and then switched to chrome - same behavior.

  It didn't happen when I was playing Hollow Knight in Steam, or when
  I've used the terminal and nothing else.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  6 14:27:36 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-06-16 (19 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1980831/+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 2017444] Re: Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20

[Jan Saarinen]

** Description changed:

  Computers with Intel Atom CPU will not boot with Kernel 6.2.0-20 OR any
  other Kernel in 6.2 series or Kernel 6.3.0.
  
  This bug affects all Intel Atom CPU computers in all Linux distributions
  making impossible to install or boot to OS with kernel 6.2 or higher.
  
  SOLUTION FOR THIS BUG IS FOUND:
  
  Copying (installing) file shisp_2401a0_v21.bin from:
  
  https://github.com/intel-aero/meta-intel-aero-base/blob/master/recipes-
  kernel/linux/linux-yocto/shisp_2401a0_v21.bin
  
  to /lib/firmware will solve the bug (partially - it still gives error
  messages - but at least the computer boots).**
  
  (dmesg.log with shisp-file with kernel 6.2.0-06 and 6.3.0-06 as
  attachments 9. and 10.)
  
  (Another solution - which Manjaro kernel maintainer did - was to disable
  atomisp and related modules).
  
  Afterwards Intel Atom CPU computer will be able to boot with kernel 6.2.
+ 
+ NOTICE TO UBUNTU KERNEL MAINTAINERS:
+ The following persons are in charge of atomisp kernel development:
+ 
+ Hans de Goede  (maintainer:STAGING - ATOMISP DRIVER)
+ Mauro Carvalho Chehab  (maintainer:STAGING - ATOMISP 
DRIVER)
+ Sakari Ailus  (reviewer:STAGING - ATOMISP 
DRIVER)
+ Greg Kroah-Hartman  (supporter:STAGING SUBSYSTEM)
+ linux-me...@vger.kernel.org (open list:STAGING - ATOMISP DRIVER)
+ linux-stag...@lists.linux.dev (open list:STAGING SUBSYSTEM)
+ linux-ker...@vger.kernel.org (open list)
+ 
+ April 29th Hans de Goede adviced me personally( 
https://github.com/linux-surface/linux-surface/issues/1095 ), that 
shisp_2401a0_v21.bin driver is still in development and should be disabled. 
Since this driver is already missing in Ubuntu kernel- there is nothing to 
disable.
+ Therefore the only -and best - solution is to disable atomisp modules in 
kernel.
  
  MORE INFORMATION IN: https://askubuntu.com/questions/1464926/not-able-
  to-boot-kubuntu-23-04-with-kernel-6-2-and-intel-atom-cpu
  
  The last stable Ubuntu Kernel Intel Atom CPU computer will boot with is
  6.1.25.
  
  The bug is caused by Intel atomisp camera driver module which has driver
  missing: shisp_2401a_v21.bin.
  
  This bug was already in 5.19, as you can see from dmesg.logs. It appears
  that atomisp failes to launch in both 5.19.0-40 and 6.1.25 but still the
  computer boots.
  
  This bug is also reported in Manjaro ( " https://github.com/linux-
  surface/linux-surface/issues/1095 ")and Arch Linux ("
  https://bbs.archlinux.org/viewtopic.php?id=283920 ") so it is not
  limited to Ubuntu Kernels.
  
  This bug has already been reported for Ubuntu 23.04 Beta in Ubuntu
  bugtracking system (" https://www.mail-archive.com/kernel-
  packa...@lists.launchpad.net/msg501664.html ") with Bug number #2015794.
  
  Attachments:
  1. Picture of stuck boot sequence of HP x2 210 G2 with Intel Atom CPU trying 
to boot in to Kubuntu 23.04 with Kernel 6.2.0-20.
  
  2. dmesg.log of the computer with Ubuntu Kernel 6.1.25.
  3. xsession-errors of the computer with Ubuntu Kernel 6.1.25.
  4. dmesg.log of the computer with Ubuntu Kernel 5.19.0-40.
  5. Video of boot sequence with Kernel 6.2.0-20.
  6. uname-a.log of Kernel 6.1.25.
  7. lspci-vvnn.log of Kernel 6.1.25.
  8. version.log of Kernel 5.19.0-40.
  9. dmesg.log with shisp-file with ubuntu kernel 6.2.0-06.**
  10. dmesg.log with shisp-file with ubuntu kernel 6.3.0-06**
  
  P.S. The apport-collect data is from Kernel 5.19.0-40.
  P.S.P.S I had difficulty determining Tags so they are to be changed by you.

** Description changed:

  Computers with Intel Atom CPU will not boot with Kernel 6.2.0-20 OR any
  other Kernel in 6.2 series or Kernel 6.3.0.
  
  This bug affects all Intel Atom CPU computers in all Linux distributions
  making impossible to install or boot to OS with kernel 6.2 or higher.
+ 
+ NOTICE TO UBUNTU KERNEL MAINTAINERS:
+ The following persons are in charge of atomisp kernel development:
+ 
+ Hans de Goede  (maintainer:STAGING - ATOMISP DRIVER)
+ Mauro Carvalho Chehab  (maintainer:STAGING - ATOMISP 
DRIVER)
+ Sakari Ailus  (reviewer:STAGING - ATOMISP 
DRIVER)
+ Greg Kroah-Hartman  (supporter:STAGING SUBSYSTEM)
+ linux-me...@vger.kernel.org (open list:STAGING - ATOMISP DRIVER)
+ linux-stag...@lists.linux.dev (open list:STAGING SUBSYSTEM)
+ linux-ker...@vger.kernel.org (open list)
+ 
+ April 29th Hans de Goede adviced me personally( 
https://github.com/linux-surface/linux-surface/issues/1095 ), that 
shisp_2401a0_v21.bin driver is still in development and should be disabled. 
Since this driver is already missing in Ubuntu kernel- there is nothing to 
disable.
+ Therefore the only -and best - solution is to disable atomisp modules in 
kernel.
+ 
  
  SOLUTION FOR THIS BUG IS FOUND:
  
  Copying (installing) file shisp_2401a0_v21.bin from:
  
  https://github.com/intel-aero/meta-intel-aero-base/blob/master/recipes-
  kernel/linux/linux-yocto/shisp_2401a0_v21.bin
  
  to /lib/firmware will solve the bug (partially - it still gives error
  messages - but at least the 

Re: [Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)

[koba]

@Yubo,
Would you please file another bug and upload the dmesg, lspci and cpuinfo

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

Title:
  No HDMI audio under 5.19.0-35 & -37 (regression from -32)

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

Bug description:
  [Impact]
  For amdgpu/i915, hdmi audio output device has disappeared.

  [Fix]
  The latest fix for the non-contiguous memalloc helper changed the
  allocation method for a non-IOMMU system to use only the fallback
  allocator.  This should have worked, but it caused a problem sometimes
  when too many non-contiguous pages are allocated that can't be treated
  by HD-audio controller.
  
  As a quirk workaround, go back to the original strategy: use
  dma_alloc_noncontiguous() at first, and apply the fallback only when
  it fails, but only for non-IOMMU case

  [Test Case]
  1. boot with kernel applied the patches.
  2. check the cards in /proc/asound/cards.
 Get the hdmi cards.

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xe232 irq 137
   1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xe226 irq 134

  [Where problems could occur]
  Low, this is just workaround and may have a better solution in the future.

  [Misc]
  All patches has been landed on OEM-6.1 and lunar.

  ~~
  CLARIFICATION: Just to avoid any confusion for those coming to this bug 
report; the "Jammy: invalid" status above does *not* mean that this bug doesn't 
affect jammy -- it does, and the kernel team is aware of this. All it reflects 
is that the fix has to go into the kinetic kernel package which will then flow 
into the kernel-hwe package implicitly.

  Currently known affected cards:

  * HD 7700 (comment 8)
  * R9 290 (comment 21)
  * RX 550 (LP: #2012141, and comment 27)
  * RX 570 (mine)
  * RX 580 (LP: #2009276, and comment 28)
  * WX 3200 (comment 29)
  * RX 6600 (LP: #2009542)
  * RX 6700 (LP: #2009275)

  [ Original Description ]

  After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
  the kernel, I found my HDMI audio output device had disappeared.
  Reverting to the -32 release caused it to appear again (hence why I'm
  filing the bug against the kernel rather than pulseaudio). I'm
  attaching the dmesg output from immediately after booting each kernel,
  but after a bit of trimming and diffing I *think* the following lines
  are the salient ones:

  input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12
  input: HDA ATI HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13
  input: HDA ATI HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14
  input: HDA ATI HDMI HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15
  input: HDA ATI HDMI HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16
  input: HDA ATI HDMI HDMI/DP,pcm=11 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17
  snd_hda_intel :2b:00.1: bound :2b:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])

  These lines appear in the dmesg of the -32 kernel, but not in the -35
  kernel's log. Meanwhile, the following lines appear in the -35
  kernel's log but not in the -32:

  hdaudio hdaudioC0D0: no AFG or MFG node found
  snd_hda_intel :2b:00.1: no codecs initialized

  I'll also attach the output of "pactl list" under each kernel (this
  shows the HDMI audio sink showing up under -32, but not -35) just in
  case that helps shed any light on things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2016459] Re: NVRM: RmInitAdapter failed! , failed to copy vbios to system memory

[Anton Kovalyov]

I have the same problem on Xubuntu 23.04, Lenovo G780, graphic card
NVIDIA Corporation GF108M [GeForce GT 635M] (rev a1).

My current workaround to boot with the old kernel: linux-
image-5.19.0-40-generic.

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

Title:
  NVRM: RmInitAdapter failed! , failed to copy vbios to system memory

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

Bug description:
  Hi, just performed a do-release_upgrade -d to try 23.10 on my lenovo T430 
laptop with Nvidia chipset (NVIDIA NVS 5200M).
  Upgrade went smooth, but noticed my external displays where not seen. a 
checkup shows nvidia-settings doesn't show full as usual, and noticed messages 
in recarding NVRM which i had never before.

  ```
  [35057.710742] NVRM: RmInitAdapter failed! (0x30:0x:663)
  [35057.710792] NVRM: rm_init_adapter failed for device bearing minor number 0
  [35060.706390] NVRM: failed to copy vbios to system memory.
  [35060.706501] NVRM: RmInitAdapter failed! (0x30:0x:663)
  [35060.706562] NVRM: rm_init_adapter failed for device bearing minor number 0
  [35063.708929] NVRM: failed to copy vbios to system memory.
  [35063.709041] NVRM: RmInitAdapter failed! (0x30:0x:663)
  [35063.709087] NVRM: rm_init_adapter failed for device bearing minor number 0

  ```

  searching for nvidia
  ```
  2023-04-16T22:15:49.402742+02:00 T430-i7 kernel: [   14.428429] nvidia: 
loading out-of-tree module taints kernel.
  2023-04-16T22:15:49.402743+02:00 T430-i7 kernel: [   14.428443] nvidia: 
module license 'NVIDIA' taints kernel.
  2023-04-16T22:15:49.402757+02:00 T430-i7 kernel: [   14.528477] 
nvidia-nvlink: Nvlink Core is being initialized, major device number 234
  2023-04-16T22:15:49.402845+02:00 T430-i7 kernel: [   14.529212] nvidia 
:01:00.0: enabling device ( -> 0003)
  2023-04-16T22:15:49.402847+02:00 T430-i7 kernel: [   14.529674] nvidia 
:01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=none
  2023-04-16T22:15:49.402857+02:00 T430-i7 kernel: [   14.589081] 
nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  
390.157  Wed Oct 12 09:15:25 UTC 2022
  2023-04-16T22:15:49.402870+02:00 T430-i7 kernel: [   14.619491] [drm] 
[nvidia-drm] [GPU ID 0x0100] Loading driver
  2023-04-16T22:15:49.402901+02:00 T430-i7 kernel: [   14.657436] 
[drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed 
to allocate NvKmsKapiDevice
  2023-04-16T22:15:49.402903+02:00 T430-i7 kernel: [   14.659661] 
[drm:nv_drm_probe_devices [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 
0x0100] Failed to register device
  2023-04-16T22:15:49.402988+02:00 T430-i7 kernel: [   15.433547] nvidia-uvm: 
Loaded the UVM driver in 8 mode, major device number 511
  2023-04-16T22:15:49.402993+02:00 T430-i7 kernel: [   15.536785] audit: 
type=1400 audit(1681676145.574:3): apparmor="STATUS" operation="profile_load" 
profile="unconfined" name="nvidia_modprobe" pid=2406 comm="apparmor_parser"
  2023-04-16T22:15:49.403000+02:00 T430-i7 kernel: [   15.536790] audit: 
type=1400 audit(1681676145.574:4): apparmor="STATUS" operation="profile_load" 
profile="unconfined" name="nvidia_modprobe//kmod" pid=2406 
comm="apparmor_parser"
  2023-04-16T22:15:49.403188+02:00 T430-i7 kernel: [   18.933794] nvidia-uvm: 
Unloaded the UVM driver in 8 mode
  2023-04-16T22:15:49.403194+02:00 T430-i7 kernel: [   18.987254] 
nvidia-modeset: Unloading
  2023-04-16T22:15:49.403195+02:00 T430-i7 kernel: [   19.023265] 
nvidia-nvlink: Unregistered the Nvlink Core, major device number 234
  2023-04-16T22:15:49.403218+02:00 T430-i7 kernel: [   19.328850] 
nvidia-nvlink: Nvlink Core is being initialized, major device number 234
  2023-04-16T22:15:49.654976+02:00 T430-i7 kernel: [   19.608711] nvidia 
:01:00.0: enabling device ( -> 0003)
  2023-04-16T22:15:49.654996+02:00 T430-i7 kernel: [   19.608847] nvidia 
:01:00.0: vgaarb: changed VGA decodes: 
olddecodes=none,decodes=none:owns=none
  2023-04-16T22:15:49.720716+02:00 T430-i7 systemd[1]: Starting 
nvidia-persistenced.service - NVIDIA Persistence Daemon...
  2023-04-16T22:15:49.723994+02:00 T430-i7 nvidia-persistenced: Verbose syslog 
connection opened
  2023-04-16T22:15:49.724337+02:00 T430-i7 nvidia-persistenced: Now running 
with user ID 139 and group ID 155
  2023-04-16T22:15:49.724508+02:00 T430-i7 systemd[1]: Started 
nvidia-persistenced.service - NVIDIA Persistence Daemon.
  2023-04-16T22:15:49.724577+02:00 T430-i7 nvidia-persistenced: Started (3602)
  2023-04-16T22:15:49.724717+02:00 T430-i7 nvidia-persistenced: Received signal 
15
  2023-04-16T22:15:49.724786+02:00 T430-i7 nvidia-persistenced: PID file 
unlocked.
  2023-04-16T22:15:49.724848+02:00 T430-i7 nvidia-persistenced: PID file closed.
  2023-04-16T22:15:49.724908+02:00 T430-i7 systemd[1]: Stopping 

[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)

[Yubo Wang]

My problems remain After upgrading to pre-proposed kernel 5.19.0-42 : Youtube , 
mouse, key input still often paused for some time( 10 seconds or more).  
Youtube, there are 30 seconds buffer, still paused for more than 10 seconds 
very often.
Mouse might disappear for more than 10 seconds very often.
 
Good news are that 2 warnings (hdaudio hdaudioC1D0: no AFG or MFG node found , 
snd_hda_intel :01:00.1: no codecs initializedd) disappeared after upgrade 
to 5.19.0.42.

When -42 start up, 4 warnings still appeared:
[1.043489]blacklist: Problem blacklisting hash (-13)
[1.043489]blacklist: Problem blacklisting hash (-13)
[1.043489]blacklist: Problem blacklisting hash (-13)
[1.043489]blacklist: Problem blacklisting hash (-13)

hdaudio hdaudioC1D0: no AFG or MFG node found ( 5.15.0-70, 5.19.0-40,   
5.19.0-41 has this warning)
snd_hda_intel :01:00.1: no codecs initializedd  ( 5.15.0-70, 5.19.0-40,   
5.19.0-41 has this warning)

Version below 5.15.0-70 works fine and without any warning.

I had the same problems (Youtube , mouse, key input frozing )with
5.19.0.32 as well,

[1.043489]blacklist: Problem blacklisting hash (-13)
[1.043489]blacklist: Problem blacklisting hash (-13)
[1.043489]blacklist: Problem blacklisting hash (-13)
[1.043489]blacklist: Problem blacklisting hash (-13)

but without the following warinings:
hdaudio hdaudioC1D0: no AFG or MFG node found （5.19.0.32 does not have this 
warning)
snd_hda_intel :01:00.1: no codecs initialized （5.19.0.32 does not have this 
warning)

** Attachment added: "log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+attachment/5669606/+files/lspci.log

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

Title:
  No HDMI audio under 5.19.0-35 & -37 (regression from -32)

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

Bug description:
  [Impact]
  For amdgpu/i915, hdmi audio output device has disappeared.

  [Fix]
  The latest fix for the non-contiguous memalloc helper changed the
  allocation method for a non-IOMMU system to use only the fallback
  allocator.  This should have worked, but it caused a problem sometimes
  when too many non-contiguous pages are allocated that can't be treated
  by HD-audio controller.
  
  As a quirk workaround, go back to the original strategy: use
  dma_alloc_noncontiguous() at first, and apply the fallback only when
  it fails, but only for non-IOMMU case

  [Test Case]
  1. boot with kernel applied the patches.
  2. check the cards in /proc/asound/cards.
 Get the hdmi cards.

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xe232 irq 137
   1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xe226 irq 134

  [Where problems could occur]
  Low, this is just workaround and may have a better solution in the future.

  [Misc]
  All patches has been landed on OEM-6.1 and lunar.

  ~~
  CLARIFICATION: Just to avoid any confusion for those coming to this bug 
report; the "Jammy: invalid" status above does *not* mean that this bug doesn't 
affect jammy -- it does, and the kernel team is aware of this. All it reflects 
is that the fix has to go into the kinetic kernel package which will then flow 
into the kernel-hwe package implicitly.

  Currently known affected cards:

  * HD 7700 (comment 8)
  * R9 290 (comment 21)
  * RX 550 (LP: #2012141, and comment 27)
  * RX 570 (mine)
  * RX 580 (LP: #2009276, and comment 28)
  * WX 3200 (comment 29)
  * RX 6600 (LP: #2009542)
  * RX 6700 (LP: #2009275)

  [ Original Description ]

  After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
  the kernel, I found my HDMI audio output device had disappeared.
  Reverting to the -32 release caused it to appear again (hence why I'm
  filing the bug against the kernel rather than pulseaudio). I'm
  attaching the dmesg output from immediately after booting each kernel,
  but after a bit of trimming and diffing I *think* the following lines
  are the salient ones:

  input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12
  input: HDA ATI HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13
  input: HDA ATI HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14
  input: HDA ATI HDMI HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15
  input: HDA ATI HDMI HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16
  input: HDA ATI HDMI HDMI/DP,pcm=11 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17
  snd_hda_intel :2b:00.1: bound :2b:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])

  These lines appear in the 

[Kernel-packages] [Bug 1961470] Re: wakeup from suspend creates error with ata RIP: 0010:ata_eh_handle_port_resume+0x12f/0x140

[ein halb]

I have a very similar issue with AMD Ryzen 7 2700U CPU, Samsung NVME-HD and 
Intel AX210 wifi card:
RIP: 0010:ata_eh_handle_port_resume+0x14b/0x160
...
ata1: failed stop FIS RX (-16)
...
Bluetooth: hci0: Malformed MSFT vendor event: 0x02


lscpu
AMD Ryzen 7 2700U with Radeon Vega Mobile Gfx

lsusb
Bus 001 Device 002: ID 8087:0032 Intel Corp. AX210 Bluetooth

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
Codename:   jammy

uname -a
Linux NB-1 5.19.0-41-generic #42~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Apr 18 
17:40:00 UTC 2 x86_64 x86_64 x86_64 GNU/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/1961470

Title:
  wakeup from suspend creates error with ata RIP:
  0010:ata_eh_handle_port_resume+0x12f/0x140

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Found this crash log after resume from suspend. The system only has a
  nvme SSD, no sata device is connected

  [ 3365.249391] ACPI: EC: interrupt blocked
  [ 3365.296812] ACPI: EC: interrupt unblocked
  [ 3365.338793] [ cut here ]
  [ 3365.338799] WARNING: CPU: 13 PID: 295 at drivers/ata/libata-eh.c:3958 
ata_eh_handle_port_resume+0x12f/0x140
  [ 3365.338824] Modules linked in: tls rfcomm ccm cmac algif_hash 
algif_skcipher af_alg snd_seq_dummy snd_hrtimer snd_ctl_led bnep 
snd_hda_codec_realtek intel_rapl_msr snd_hda_codec_generic intel_rapl_common 
ledtrig_audio snd_hda_codec_hdmi edac_mce_amd snd_hda_intel snd_intel_dspcfg 
snd_soc_dmic snd_acp3x_pdm_dma snd_acp3x_rn snd_intel_sdw_acpi snd_soc_core 
snd_hda_codec snd_compress snd_hda_core ac97_bus snd_pcm_dmaengine snd_hwdep 
kvm_amd amdgpu snd_pcm
  [ 3365.338872] [ cut here ]
  [ 3365.338873]  nls_iso8859_1 kvm mt7921e snd_seq_midi mt76_connac_lib 
uvcvideo snd_seq_midi_event
  [ 3365.338876] WARNING: CPU: 0 PID: 301 at drivers/ata/libata-eh.c:3958 
ata_eh_handle_port_resume+0x12f/0x140
  [ 3365.338883]  crct10dif_pclmul mt76
  [ 3365.338887] Modules linked in: tls rfcomm ccm cmac algif_hash 
algif_skcipher af_alg snd_seq_dummy snd_hrtimer snd_ctl_led bnep 
snd_hda_codec_realtek intel_rapl_msr snd_hda_codec_generic intel_rapl_common 
ledtrig_audio snd_hda_codec_hdmi edac_mce_amd snd_hda_intel snd_intel_dspcfg 
snd_soc_dmic snd_acp3x_pdm_dma snd_acp3x_rn snd_intel_sdw_acpi snd_soc_core
  [ 3365.338927]  btusb
  [ 3365.338930]  snd_hda_codec
  [ 3365.338929]  iommu_v2 videobuf2_vmalloc
  [ 3365.338932]  snd_compress
  [ 3365.338933]  ghash_clmulni_intel
  [ 3365.338934]  snd_hda_core
  [ 3365.338934]  input_leds btrtl
  [ 3365.338937]  ac97_bus
  [ 3365.338939]  snd_rawmidi
  [ 3365.338940]  snd_pcm_dmaengine snd_hwdep
  [ 3365.338943]  hid_sensor_accel_3d hid_sensor_als
  [ 3365.338946]  kvm_amd
  [ 3365.338947]  gpu_sched videobuf2_memops
  [ 3365.338951]  amdgpu
  [ 3365.338951]  aesni_intel
  [ 3365.338953]  snd_pcm
  [ 3365.338952]  btbcm mac80211
  [ 3365.338955]  nls_iso8859_1 kvm
  [ 3365.338958]  drm_ttm_helper
  [ 3365.338960]  mt7921e
  [ 3365.338959]  hid_sensor_trigger btintel
  [ 3365.338962]  snd_seq_midi
  [ 3365.338962]  crypto_simd
  [ 3365.338964]  mt76_connac_lib
  [ 3365.338963]  videobuf2_v4l2
  [ 3365.338967]  uvcvideo
  [ 3365.338965]  industrialio_triggered_buffer snd_seq
  [ 3365.338970]  snd_seq_midi_event
  [ 3365.338972]  cryptd
  [ 3365.338976]  crct10dif_pclmul
  [ 3365.338975]  bluetooth ttm
  [ 3365.338979]  mt76 btusb
  [ 3365.338983]  videobuf2_common
  [ 3365.338987]  iommu_v2
  [ 3365.338987]  kfifo_buf
  [ 3365.338990]  videobuf2_vmalloc
  [ 3365.338989]  hid_sensor_iio_common ecdh_generic
  [ 3365.338992]  ghash_clmulni_intel
  [ 3365.338992]  rapl
  [ 3365.338994]  input_leds
  [ 3365.338993]  serio_raw
  [ 3365.338995]  btrtl
  [ 3365.338994]  efi_pstore
  [ 3365.338997]  snd_rawmidi
  [ 3365.338996]  wmi_bmof
  [ 3365.338999]  hid_sensor_accel_3d
  [ 3365.338997]  hid_multitouch snd_seq_device
  [ 3365.339000]  hid_sensor_als
  [ 3365.339000]  joydev
  [ 3365.339002]  gpu_sched
  [ 3365.339002]  industrialio
  [ 3365.339004]  videobuf2_memops
  [ 3365.339003]  ecc
  [ 3365.339005]  aesni_intel
  [ 3365.339005]  videodev drm_kms_helper
  [ 3365.339007]  btbcm
  [ 3365.339007]  snd_timer
  [ 3365.339009]  mac80211
  [ 3365.339008]  mc
  [ 3365.339010]  drm_ttm_helper
  [ 3365.339009]  cfg80211
  [ 3365.339012]  hid_sensor_trigger
  [ 3365.339011]  cec
  [ 3365.339013]  btintel
  [ 3365.339012]  snd_pci_acp5x
  [ 3365.339015]  crypto_simd
  [ 3365.339014]  rc_core k10temp
  [ 3365.339017]  videobuf2_v4l2
  [ 3365.339017]  i2c_algo_bit
  [ 3365.339018]  industrialio_triggered_buffer
  [ 3365.339018]  snd
  [ 3365.339020]  snd_seq
  [ 3365.339019]  snd_rn_pci_acp3x fb_sys_fops
  [ 3365.339022]  cryptd
  [ 3365.339024]  syscopyarea sysfillrect
  [ 3365.339027]  bluetooth
  [ 3365.339027]  snd_pci_acp3x 

[Kernel-packages] [Bug 2016065] Re: Internal 'Genesys Logic, Inc. Hub' disconnects from ASUS PN50 during boot

[professordes]

This (i.e. hub disconnects on boot, so no usb for keyboard or mouse) is
still an issue with the release version of 23.04.

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

Title:
  Internal 'Genesys Logic, Inc. Hub' disconnects from ASUS PN50 during
  boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu Lunar Lobster (development branch)
  Release:  23.04

  libinput-bin:
    Installed: 1.22.1-1
    Candidate: 1.22.1-1
    Version table:
   *** 1.22.1-1 500
  500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  linux-image-generic:
    Installed: 6.2.0.20.20
    Candidate: 6.2.0.20.20
    Version table:
   *** 6.2.0.20.20 500
  500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  After upgrading to the 23.04 beta from 22.10 the system (an ASUS PN-50
  mini-PC) became unresponsive to any (USB) keyboard or mouse input.

  This is still the case when the Ubuntu recovery option is chosen in
  the boot menu.

  Different USB keyboards and mice/plugging unplugging etc have no
  effect.

  The system boots all the way to the Ubuntu login screen and can be
  accessed via ssh.

  When booted into Windows all is still functioning correctly

  Unclear if this is a libinput problem, or lies elsewhere (kernel?)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: libinput-bin 1.22.1-1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  Date: Thu Apr 13 09:00:56 2023
  DistUpgraded: 2023-04-10 16:30:22,175 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Renoir [1043:87e7]
  InstallationDate: Installed on 2020-11-14 (879 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. MINIPC PN50
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=4837ff80-a59b-47c0-ae9d-811d54bad076 ro quiet splash vt.handoff=7
  SourcePackage: libinput
  UpgradeStatus: Upgraded to lunar on 2023-04-10 (2 days ago)
  dmi.bios.date: 07/06/2022
  dmi.bios.release: 6.24
  dmi.bios.vendor: ASUSTeK COMPUTER INC.
  dmi.bios.version: 0624
  dmi.board.asset.tag: Default string
  dmi.board.name: PN50
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnASUSTeKCOMPUTERINC.:bvr0624:bd07/06/2022:br6.24:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50:pvr0624:rvnASUSTeKCOMPUTERINC.:rnPN50:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku:
  dmi.product.family: Vivo PC
  dmi.product.name: MINIPC PN50
  dmi.product.version: 0624
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016065/+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 2017790] Re: Intel Wi-Fi 6 AX201 failing in 23.04

[David Roche]

@Matthew No luck i'm afraid I removed the module and I'm still getting
the same issue. @Jeremy is there any other steps I can try ?

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

Title:
  Intel Wi-Fi 6 AX201 failing in 23.04

Status in linux-lowlatency package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 22.04 to 23.04 the intel wifi driver is not
  loading, I am seeing the following in dmesg:

  [  215.024382] Loading of unsigned module is rejected
  [  262.051998] [ cut here ]
  [  262.052001] WARNING: CPU: 2 PID: 6946 at net/netlink/genetlink.c:570 
genl_validate_ops+0x1cc/0x270
  [  262.052007] Modules linked in: cfg80211(O+) rfcomm xt_conntrack 
nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables libcrc32c nfnetlink br_netfilter bridge stp llc 
vmw_vsock_vmci_transport vsock vmw_vmci snd_seq_dummy snd_hrtimer overlay cmac 
algif_hash algif_skcipher af_alg bnep dell_rbu typec_displayport 
snd_hda_codec_hdmi snd_ctl_led binfmt_misc snd_hda_codec_realtek 
snd_hda_codec_generic snd_sof_pci_intel_tgl snd_sof_intel_hda_common 
soundwire_intel hid_logitech_hidpp soundwire_generic_allocation nls_iso8859_1 
soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof 
snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match 
snd_soc_acpi soundwire_bus snd_soc_core snd_compress ac97_bus 
x86_pkg_temp_thermal r8153_ecm snd_pcm_dmaengine intel_powerclamp cdc_ether 
coretemp snd_hda_intel usbnet snd_usb_audio kvm_intel snd_intel_dspcfg r8152 
snd_intel_
 sdw_acpi
  [  262.052038]  mii hid_plantronics hid_logitech_dj snd_usbmidi_lib 
snd_hda_codec kvm snd_hda_core snd_hwdep irqbypass mei_hdcp mei_pxp 
intel_rapl_msr dell_laptop snd_pcm crct10dif_pclmul i915 polyval_clmulni 
snd_seq_midi polyval_generic snd_seq_midi_event ghash_clmulni_intel 
sha512_ssse3 snd_rawmidi uvcvideo btusb videobuf2_vmalloc 
hid_sensor_custom_intel_hinge aesni_intel hid_sensor_gyro_3d 
hid_sensor_accel_3d dell_wmi videobuf2_memops snd_seq crypto_simd 
hid_sensor_trigger btrtl drm_buddy snd_seq_device btbcm videobuf2_v4l2 btintel 
processor_thermal_device_pci_legacy cryptd cmdlinepart 
industrialio_triggered_buffer dell_smbios rapl dcdbas snd_timer ttm 
dell_wmi_sysman btmtk videodev kfifo_buf spi_nor processor_thermal_device 
hid_sensor_iio_common processor_thermal_rfim intel_cstate 
firmware_attributes_class ledtrig_audio drm_display_helper dell_wmi_descriptor 
wmi_bmof industrialio mei_me mtd bluetooth snd videobuf2_common mc cec 
processor_thermal_mbox soundcore rc_core mei ecdh_
 generic
  [  262.052068]  processor_thermal_rapl iwlwifi_compat(O) drm_kms_helper ecc 
ucsi_acpi joydev i2c_algo_bit intel_rapl_common typec_ucsi syscopyarea 
intel_soc_dts_iosf sysfillrect typec sysimgblt igen6_edac int3403_thermal 
soc_button_array int340x_thermal_zone int3400_thermal intel_hid 
acpi_thermal_rel acpi_pad acpi_tad sparse_keymap hid_multitouch input_leds 
mac_hid serio_raw msr parport_pc ppdev drm lp parport efi_pstore dmi_sysfs 
ip_tables x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid hid_generic nvme nvme_core intel_ish_ipc i2c_hid_acpi 
spi_intel_pci rtsx_pci_sdmmc crc32_pclmul video i2c_i801 i2c_hid intel_lpss_pci 
xhci_pci spi_intel intel_ishtp nvme_common thunderbolt psmouse i2c_smbus 
intel_lpss rtsx_pci idma64 xhci_pci_renesas hid wmi pinctrl_tigerlake
  [  262.052097] CPU: 2 PID: 6946 Comm: modprobe Tainted: GW  O   
6.2.0-1003-lowlatency #3-Ubuntu
  [  262.052098] Hardware name: Dell Inc. Latitude 7420/07MHG4, BIOS 1.24.2 
02/24/2023
  [  262.052099] RIP: 0010:genl_validate_ops+0x1cc/0x270
  [  262.052102] Code: 81 c4 d8 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 
c9 31 ff c3 cc cc cc cc 49 83 7d 50 00 0f 85 b9 fe ff ff 0f 0b eb bd <0f> 0b eb 
b9 0f 0b eb b5 0f 0b eb b1 45 84 ff 75 04 31 c0 eb ad 4d
  [  262.052103] RSP: 0018:a91bc7103a88 EFLAGS: 00010206
  [  262.052105] RAX: 0003 RBX: a91bc7103af0 RCX: 

  [  262.052106] RDX:  RSI:  RDI: 

  [  262.052106] RBP: a91bc7103b88 R08:  R09: 

  [  262.052107] R10:  R11:  R12: 
0001
  [  262.052107] R13: c1824780 R14: a91bc7103a88 R15: 

  [  262.052108] FS:  7fd67c380040() GS:8fcc7f68() 
knlGS:
  [  262.052109] CS:  0010 DS:  ES:  CR0: 80050033
  [  262.052110] CR2: 7fff38c0e848 CR3: 00010a938006 CR4: 
00770ee0
  [  262.052111] PKRU: 5554
  [  262.052112] Call Trace:
  [  262.052113]  
  [  262.052115]  ? __pfx_nl80211_pre_doit+0x10/0x10 [cfg80211]
  [  262.052146]  ? 

Re: [Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)

[koba]

@Wiktor,
Because the target kernel was landed on jammy,it would fix the issue.
Jammy have a rolling 5.19 kernel channel and you could update it.
As I known, the fix was landed on kinetic first after some progresses,it
would arrive jammy too.
I understand it's not a quick process but you will get it on jammy.
Can't boot issue, please file another bug,thanks

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

Title:
  No HDMI audio under 5.19.0-35 & -37 (regression from -32)

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

Bug description:
  [Impact]
  For amdgpu/i915, hdmi audio output device has disappeared.

  [Fix]
  The latest fix for the non-contiguous memalloc helper changed the
  allocation method for a non-IOMMU system to use only the fallback
  allocator.  This should have worked, but it caused a problem sometimes
  when too many non-contiguous pages are allocated that can't be treated
  by HD-audio controller.
  
  As a quirk workaround, go back to the original strategy: use
  dma_alloc_noncontiguous() at first, and apply the fallback only when
  it fails, but only for non-IOMMU case

  [Test Case]
  1. boot with kernel applied the patches.
  2. check the cards in /proc/asound/cards.
 Get the hdmi cards.

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xe232 irq 137
   1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xe226 irq 134

  [Where problems could occur]
  Low, this is just workaround and may have a better solution in the future.

  [Misc]
  All patches has been landed on OEM-6.1 and lunar.

  ~~
  CLARIFICATION: Just to avoid any confusion for those coming to this bug 
report; the "Jammy: invalid" status above does *not* mean that this bug doesn't 
affect jammy -- it does, and the kernel team is aware of this. All it reflects 
is that the fix has to go into the kinetic kernel package which will then flow 
into the kernel-hwe package implicitly.

  Currently known affected cards:

  * HD 7700 (comment 8)
  * R9 290 (comment 21)
  * RX 550 (LP: #2012141, and comment 27)
  * RX 570 (mine)
  * RX 580 (LP: #2009276, and comment 28)
  * WX 3200 (comment 29)
  * RX 6600 (LP: #2009542)
  * RX 6700 (LP: #2009275)

  [ Original Description ]

  After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
  the kernel, I found my HDMI audio output device had disappeared.
  Reverting to the -32 release caused it to appear again (hence why I'm
  filing the bug against the kernel rather than pulseaudio). I'm
  attaching the dmesg output from immediately after booting each kernel,
  but after a bit of trimming and diffing I *think* the following lines
  are the salient ones:

  input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12
  input: HDA ATI HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13
  input: HDA ATI HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14
  input: HDA ATI HDMI HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15
  input: HDA ATI HDMI HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16
  input: HDA ATI HDMI HDMI/DP,pcm=11 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17
  snd_hda_intel :2b:00.1: bound :2b:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])

  These lines appear in the dmesg of the -32 kernel, but not in the -35
  kernel's log. Meanwhile, the following lines appear in the -35
  kernel's log but not in the -32:

  hdaudio hdaudioC0D0: no AFG or MFG node found
  snd_hda_intel :2b:00.1: no codecs initialized

  I'll also attach the output of "pactl list" under each kernel (this
  shows the HDMI audio sink showing up under -32, but not -35) just in
  case that helps shed any light on things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)

[Wiktor Tomanek]

Matt, yes I agree with you, but it didn't roll out yet, did it? So fix
IS verified but it's not fixed. I wrote what I wrote because Koba asked
me to help with verification. I tried but I can't and I am still mad at
f Ubuntu because I still doesn't have audio.

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

Title:
  No HDMI audio under 5.19.0-35 & -37 (regression from -32)

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

Bug description:
  [Impact]
  For amdgpu/i915, hdmi audio output device has disappeared.

  [Fix]
  The latest fix for the non-contiguous memalloc helper changed the
  allocation method for a non-IOMMU system to use only the fallback
  allocator.  This should have worked, but it caused a problem sometimes
  when too many non-contiguous pages are allocated that can't be treated
  by HD-audio controller.
  
  As a quirk workaround, go back to the original strategy: use
  dma_alloc_noncontiguous() at first, and apply the fallback only when
  it fails, but only for non-IOMMU case

  [Test Case]
  1. boot with kernel applied the patches.
  2. check the cards in /proc/asound/cards.
 Get the hdmi cards.

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xe232 irq 137
   1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xe226 irq 134

  [Where problems could occur]
  Low, this is just workaround and may have a better solution in the future.

  [Misc]
  All patches has been landed on OEM-6.1 and lunar.

  ~~
  CLARIFICATION: Just to avoid any confusion for those coming to this bug 
report; the "Jammy: invalid" status above does *not* mean that this bug doesn't 
affect jammy -- it does, and the kernel team is aware of this. All it reflects 
is that the fix has to go into the kinetic kernel package which will then flow 
into the kernel-hwe package implicitly.

  Currently known affected cards:

  * HD 7700 (comment 8)
  * R9 290 (comment 21)
  * RX 550 (LP: #2012141, and comment 27)
  * RX 570 (mine)
  * RX 580 (LP: #2009276, and comment 28)
  * WX 3200 (comment 29)
  * RX 6600 (LP: #2009542)
  * RX 6700 (LP: #2009275)

  [ Original Description ]

  After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
  the kernel, I found my HDMI audio output device had disappeared.
  Reverting to the -32 release caused it to appear again (hence why I'm
  filing the bug against the kernel rather than pulseaudio). I'm
  attaching the dmesg output from immediately after booting each kernel,
  but after a bit of trimming and diffing I *think* the following lines
  are the salient ones:

  input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12
  input: HDA ATI HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13
  input: HDA ATI HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14
  input: HDA ATI HDMI HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15
  input: HDA ATI HDMI HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16
  input: HDA ATI HDMI HDMI/DP,pcm=11 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17
  snd_hda_intel :2b:00.1: bound :2b:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])

  These lines appear in the dmesg of the -32 kernel, but not in the -35
  kernel's log. Meanwhile, the following lines appear in the -35
  kernel's log but not in the -32:

  hdaudio hdaudioC0D0: no AFG or MFG node found
  snd_hda_intel :2b:00.1: no codecs initialized

  I'll also attach the output of "pactl list" under each kernel (this
  shows the HDMI audio sink showing up under -32, but not -35) just in
  case that helps shed any light on things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)

[Riccardo Beduschi]

After upgrading to kernel 5.19.0-42 hdmi sound work. A (very) little issue: in 
Preference Panel-Audio-Output, not work the audio "test"!
Processor: AMD® Ryzen 5 3600 6-core processor × 12
Graphic: AMD® Radeon rx 580 series
OS Name: Ubuntu 22.04.2 LTS 64-bit
GNOME version: 42.5
Graphic System: Wayland

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

Title:
  No HDMI audio under 5.19.0-35 & -37 (regression from -32)

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

Bug description:
  [Impact]
  For amdgpu/i915, hdmi audio output device has disappeared.

  [Fix]
  The latest fix for the non-contiguous memalloc helper changed the
  allocation method for a non-IOMMU system to use only the fallback
  allocator.  This should have worked, but it caused a problem sometimes
  when too many non-contiguous pages are allocated that can't be treated
  by HD-audio controller.
  
  As a quirk workaround, go back to the original strategy: use
  dma_alloc_noncontiguous() at first, and apply the fallback only when
  it fails, but only for non-IOMMU case

  [Test Case]
  1. boot with kernel applied the patches.
  2. check the cards in /proc/asound/cards.
 Get the hdmi cards.

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xe232 irq 137
   1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xe226 irq 134

  [Where problems could occur]
  Low, this is just workaround and may have a better solution in the future.

  [Misc]
  All patches has been landed on OEM-6.1 and lunar.

  ~~
  CLARIFICATION: Just to avoid any confusion for those coming to this bug 
report; the "Jammy: invalid" status above does *not* mean that this bug doesn't 
affect jammy -- it does, and the kernel team is aware of this. All it reflects 
is that the fix has to go into the kinetic kernel package which will then flow 
into the kernel-hwe package implicitly.

  Currently known affected cards:

  * HD 7700 (comment 8)
  * R9 290 (comment 21)
  * RX 550 (LP: #2012141, and comment 27)
  * RX 570 (mine)
  * RX 580 (LP: #2009276, and comment 28)
  * WX 3200 (comment 29)
  * RX 6600 (LP: #2009542)
  * RX 6700 (LP: #2009275)

  [ Original Description ]

  After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
  the kernel, I found my HDMI audio output device had disappeared.
  Reverting to the -32 release caused it to appear again (hence why I'm
  filing the bug against the kernel rather than pulseaudio). I'm
  attaching the dmesg output from immediately after booting each kernel,
  but after a bit of trimming and diffing I *think* the following lines
  are the salient ones:

  input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12
  input: HDA ATI HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13
  input: HDA ATI HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14
  input: HDA ATI HDMI HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15
  input: HDA ATI HDMI HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16
  input: HDA ATI HDMI HDMI/DP,pcm=11 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17
  snd_hda_intel :2b:00.1: bound :2b:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])

  These lines appear in the dmesg of the -32 kernel, but not in the -35
  kernel's log. Meanwhile, the following lines appear in the -35
  kernel's log but not in the -32:

  hdaudio hdaudioC0D0: no AFG or MFG node found
  snd_hda_intel :2b:00.1: no codecs initialized

  I'll also attach the output of "pactl list" under each kernel (this
  shows the HDMI audio sink showing up under -32, but not -35) just in
  case that helps shed any light on things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2017212] Re: ASUS N56VM fails to load GUI fresh install of Ubuntu 23.04

[Thomas Mørch]

Same problem on Lenovo W540 with Quadro K1100M. Upgraded to 23.04
yesterday (coming from 22.10)

If I boot with an older 5.x kernal it works. So it seems to be an issue
with the new 6.x kernal.

According to this forum post over on nvidias forum
https://forums.developer.nvidia.com/t/390-154-driver-no-longer-works-
with-kernel-6-0/230959, it seems that the nvidia 390 isn't compatible
with kernels above 6.x, and has to be fixed by nvidia?

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

Title:
  ASUS N56VM fails to load GUI fresh install of Ubuntu 23.04

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

Bug description:
  NVRM: failed to copy vbios to system memory.
  NVRM: RmInitAdapter failed!

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 
UTC 2022
   GCC version:
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Apr 21 07:45:45 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1477]
   NVIDIA Corporation GF108M [GeForce GT 620M/630M/635M/640M LE] [10de:0de9] 
(rev a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 620M/630M/635M/640M 
LE] [1043:1477]
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: ASUSTeK COMPUTER INC. N56VM
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=0d37dcc1-3316-40c4-b4d9-7c5f62470833 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VM.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VM.214:bd08/28/2012:br4.6:svnASUSTeKCOMPUTERINC.:pnN56VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: N
  dmi.product.name: N56VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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