[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec
Just a heads-up that SGX has been deprecated by Intel: https://edc.intel.com/content/www/us/en/design/ipla/software- development-platforms/client/platforms/alder-lake-desktop/12th- generation-intel-core-processors-datasheet-volume-1-of-2/004/deprecated- technologies/ === The processor has deprecated the following technologies and they are no longer supported: Intel® Memory Protection Extensions (Intel® MPX) Branch Monitoring Counters Hardware Lock Elision (HLE), part of Intel® TSX-NI Intel® Software Guard Extensions (Intel® SGX) Intel® TSX-NI Power Aware Interrupt Routing (PAIR) === I think we shouldn't put too much weight on SGX support in making this decision. 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Focal: In Progress Status in systemd source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in systemd source package in Jammy: Invalid Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias:
[Kernel-packages] [Bug 1837326] Re: platform eisa.0: EISA: Cannot allocate resource for mainboard
Still present in 22.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/1837326 Title: platform eisa.0: EISA: Cannot allocate resource for mainboard Status in linux package in Ubuntu: Confirmed Bug description: dmesg: [0.889531] platform eisa.0: EISA: Cannot allocate resource for mainboard [0.889533] platform eisa.0: Cannot allocate resource for EISA slot 1 [0.889535] platform eisa.0: Cannot allocate resource for EISA slot 2 [0.889536] platform eisa.0: Cannot allocate resource for EISA slot 3 [0.889537] platform eisa.0: Cannot allocate resource for EISA slot 4 [0.889539] platform eisa.0: Cannot allocate resource for EISA slot 5 [0.889540] platform eisa.0: Cannot allocate resource for EISA slot 6 [0.889541] platform eisa.0: Cannot allocate resource for EISA slot 7 [0.889542] platform eisa.0: Cannot allocate resource for EISA slot 8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 3028 F pulseaudio /dev/snd/pcmC0D0p: caravena 3028 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jul 21 12:16:07 2019 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (230 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2018-12-02 (230 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837326/+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 1990835] Re: Update the 515 (UDA) NVIDIA drivers in Bionic, Focal, Jammy
This bug was fixed in the package nvidia-graphics-drivers-515 -
515.76-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-515 (515.76-0ubuntu0.20.04.1) focal; urgency=medium
* debian/nvidia_supported:
- Actually add support for the open kernel driver (fixes FTBFS)
(LP: #1988836).
* debian/templates/control.in,
debian/rules.defs:
- Keep arm64 off for now.
* debian/rules:
- Sync up with the jammy and kinetic branches so that the open
kernel driver sources are not removed on clean.
* debian
* New upstream release (LP: #1990835):
- Turing and later: fixed possible excessive GPU power draw on an
idle X11 or Wayland desktop when driving high resolutions or
refresh rates.
- Fixed a bug that caused the Xorg server to crash if an NvFBC
capture session is started while video memory is full.
nvidia-graphics-drivers-515 (515.65.01-0ubuntu0.20.04.2) focal;
urgency=medium
* debian/copyright,
debian/additional_card_ids_open,
debian/rules{.defs},
debian/templates/control.in,
debian/templates/dkms_nvidia_open.conf.in,
debian/templates/nvidia-dkms-flavour-open.*.in:
- Add support for the open kernel module (LP: #1988836).
* debian/nvidia_supported:
- Add support for the open kernel driver using the --open argument.
-- Alberto Milone Wed, 28 Sep 2022
12:35:52 +
** Changed in: nvidia-graphics-drivers-515 (Ubuntu Bionic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu.
https://bugs.launchpad.net/bugs/1990835
Title:
Update the 515 (UDA) NVIDIA drivers in Bionic, Focal, Jammy
Status in nvidia-graphics-drivers-515 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-515 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
Fix Released
Bug description:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates
Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu
The QA team that executed the tests will be in charge of attaching the
artifacts and console output of the appropriate run to the bug. nVidia
maintainers team members will not mark ‘verification-done’ until this
has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.
[Discussion]
[Changelog]
== 515.76 (UDA) ==
* New upstream release:
- Turing and later: fixed possible excessive GPU power draw on an
idle X11 or Wayland desktop when driving high resolutions or
refresh rates.
- Fixed a bug that caused the Xorg server to crash if an NvFBC
capture session is started while video memory is full.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1990835/+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 1990835] Re: Update the 515 (UDA) NVIDIA drivers in Bionic, Focal, Jammy
This bug was fixed in the package nvidia-graphics-drivers-515 - 515.76-0ubuntu0.22.04.1 --- nvidia-graphics-drivers-515 (515.76-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream release (LP: #1990835): - Turing and later: fixed possible excessive GPU power draw on an idle X11 or Wayland desktop when driving high resolutions or refresh rates. - Fixed a bug that caused the Xorg server to crash if an NvFBC capture session is started while video memory is full. * debian/templates/dkms_nvidia.conf.in: - Drop buildfix_kernel_6.0.patch. -- Alberto Milone Wed, 28 Sep 2022 12:33:06 + ** Changed in: nvidia-graphics-drivers-515 (Ubuntu Jammy) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-515 (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu. https://bugs.launchpad.net/bugs/1990835 Title: Update the 515 (UDA) NVIDIA drivers in Bionic, Focal, Jammy Status in nvidia-graphics-drivers-515 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 515.76 (UDA) == * New upstream release: - Turing and later: fixed possible excessive GPU power draw on an idle X11 or Wayland desktop when driving high resolutions or refresh rates. - Fixed a bug that caused the Xorg server to crash if an NvFBC capture session is started while video memory is full. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1990835/+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 1988429] Re: support linux-oem-6.0
This bug was fixed in the package nvidia-graphics-drivers-515 - 515.76-0ubuntu0.22.04.1 --- nvidia-graphics-drivers-515 (515.76-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream release (LP: #1990835): - Turing and later: fixed possible excessive GPU power draw on an idle X11 or Wayland desktop when driving high resolutions or refresh rates. - Fixed a bug that caused the Xorg server to crash if an NvFBC capture session is started while video memory is full. * debian/templates/dkms_nvidia.conf.in: - Drop buildfix_kernel_6.0.patch. -- Alberto Milone Wed, 28 Sep 2022 12:33:06 + ** Changed in: nvidia-graphics-drivers-515 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1988429 Title: support linux-oem-6.0 Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510 source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Bug description: [Impact] Building nvidia dkms against linux 6.0 fails. The compat code needs updates to support 6.0. [Test case] Check that it builds after fixes applied. [What could go wrong] The compat code changes affect only builds on 6.0, so there's no chance of it breaking build for other kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1988429/+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 1988836] Re: Enable the open NVIDIA kernel modules
This bug was fixed in the package nvidia-graphics-drivers-515 -
515.76-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-515 (515.76-0ubuntu0.20.04.1) focal; urgency=medium
* debian/nvidia_supported:
- Actually add support for the open kernel driver (fixes FTBFS)
(LP: #1988836).
* debian/templates/control.in,
debian/rules.defs:
- Keep arm64 off for now.
* debian/rules:
- Sync up with the jammy and kinetic branches so that the open
kernel driver sources are not removed on clean.
* debian
* New upstream release (LP: #1990835):
- Turing and later: fixed possible excessive GPU power draw on an
idle X11 or Wayland desktop when driving high resolutions or
refresh rates.
- Fixed a bug that caused the Xorg server to crash if an NvFBC
capture session is started while video memory is full.
nvidia-graphics-drivers-515 (515.65.01-0ubuntu0.20.04.2) focal;
urgency=medium
* debian/copyright,
debian/additional_card_ids_open,
debian/rules{.defs},
debian/templates/control.in,
debian/templates/dkms_nvidia_open.conf.in,
debian/templates/nvidia-dkms-flavour-open.*.in:
- Add support for the open kernel module (LP: #1988836).
* debian/nvidia_supported:
- Add support for the open kernel driver using the --open argument.
-- Alberto Milone Wed, 28 Sep 2022
12:35:52 +
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1988836
Title:
Enable the open NVIDIA kernel modules
Status in linux-restricted-modules package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-515 package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in linux-restricted-modules source package in Focal:
In Progress
Status in nvidia-graphics-drivers-515 source package in Focal:
Fix Released
Status in ubuntu-drivers-common source package in Focal:
In Progress
Status in linux-restricted-modules source package in Jammy:
In Progress
Status in nvidia-graphics-drivers-515 source package in Jammy:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
In Progress
Bug description:
[ Impact ]
* The 515 series introduced open kernel modules for the NVIDIA driver. They
come with an open source licence, and should be provided as an option for
datacenter GPUs:
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/
Currently, this is only production-ready (and enabled) on
datacenter GPUs.
* We should enable signed modules for the 515-open drivers, giving
users the option to try the drivers.
* The ubuntu-drivers tool should set a lower priority for the -open
flavour, so that we do not end up recommending it over the plain 515
flavour.
[ Test Plan ]
* [ubuntu-drivers-common]:
"sudo ubuntu-drivers install (to make sure the driver is not installed by
default)"
* [nvidia driver]
"sudo ubuntu-drivers install nvidia:515-open" to make sure that the
driver can be installed manually.
Please make sure that this installs the correct linux-restricted-
modules.
Note: support for GeForce and Workstation GPUs is alpha-quality,
and is disabled by default. This means that desktop testing is not
needed at the moment.
[ Where problems could occur ]
* This adds a new driver combination, which is not meant to be default, and
is only enabled for a limited amount of devices (datacenter GPUs).
* We need to be sure that the driver is not recommended over the other
drivers.
[ Other Info ]
-
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1988836] Re: Enable the open NVIDIA kernel modules
This bug was fixed in the package nvidia-graphics-drivers-515 - 515.76-0ubuntu0.22.04.1 --- nvidia-graphics-drivers-515 (515.76-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream release (LP: #1990835): - Turing and later: fixed possible excessive GPU power draw on an idle X11 or Wayland desktop when driving high resolutions or refresh rates. - Fixed a bug that caused the Xorg server to crash if an NvFBC capture session is started while video memory is full. * debian/templates/dkms_nvidia.conf.in: - Drop buildfix_kernel_6.0.patch. -- Alberto Milone Wed, 28 Sep 2022 12:33:06 + ** Changed in: nvidia-graphics-drivers-515 (Ubuntu Jammy) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-515 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: In Progress Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Can also confirm this bug. I'm using a GTX 1050 Ti. Tested (and working) workarounds are: - use 'nomodeset' boot option - downgrade to linux-image-5.15.0-48-generic - use nouveau driver I tried the following NVIDIA drivers, but they all have this problem (with 5.15.0-50-generic): - nvidia-driver-515 - nvidia-driver-510 - nvidia-driver-470 -- 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1970819] Re: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi
Solved downloading .sfi file for my network adapter and put in /usr/lib/firmware/intel. https://raw.githubusercontent.com/pop-os/linux- firmware/master/intel/ibt-19-0-0.sfi -- 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/1970819 Title: 5.15 pc-kernel uc22 snap fails to load bluetooth Intel firmware file intel/ibt-17-16-1.sfi Status in linux package in Ubuntu: Fix Committed Status in snapd package in Ubuntu: Confirmed Status in Fedora: New Bug description: When testing the beta image for uc22 on an Intel NUC, I noticed that bluetooth was not working. This NUC has worked for bluetooth tests on uc18, 20, and even on jammy. However on uc22, we see this in dmesg: [ 11.954649] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 11.962817] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-17-16-1.sfi (-2) [ 11.966951] Bluetooth: hci0: Failed to read MSFT supported features (-56) Here's the full dmesg with grep -i blue: https://pastebin.canonical.com/p/99KvzHY4n9/ On Jammy, for comparison, the firmware gets loaded and bluetoothctl can see nearby devices: [5.650860] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.653214] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi [7.059104] Bluetooth: hci0: Waiting for firmware download to complete [7.059838] Bluetooth: hci0: Firmware loaded in 1373648 usecs [7.059903] Bluetooth: hci0: Waiting for device to boot [7.073886] Bluetooth: hci0: Device booted in 13691 usecs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970819/+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 1964093] Re: nfsver=3, udp not working anymore
Thanks much, -- 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/1964093 Title: nfsver=3,udp not working anymore Status in linux package in Ubuntu: Confirmed Bug description: Package: nfs-kernel-server Architecture: amd64 Version: 1:2.6.1-1~exp1ubuntu1 nfsversion 3 with proto udp seems not to be supported by the nfs- kernel-server anymore. In Ubuntu 18.04 (nfs-kernel-server 1:1.3.4-2.1ubuntu5) it was still possible. I could mount with either tcp or udp: 1. tcp mount -o nfsvers=3 192.168.0.1:/srv/nfs/testshare /mnt mount|grep mnt: 192.168.0.1:/srv/nfs/testshare on /mnt type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1) 2. udp mount -o nfsvers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt mount|grep mnt: 192.168.0.1:/srv/nfs/testshare on /mnt type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1) Now in Ubuntu 22.04 I get the message: mount.nfs: an incorrect mount option was specified I tried to enable upd in /etc/nfs.conf in section [nfsd]: [nfsd] # debug=0 # threads=8 # host= # port=0 # grace-time=90 # lease-time=90 # udp=n udp=y # tcp=y # vers2=n # vers3=y But there was no effect. nfs3 with udp is needed by several busybox mount binaries in initrds of Knoppix and other live distributions used via PXE boot. Best regards Jörg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964093/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Confirmed for me as well. -- 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Can also confirm this bug using linux-image-5.1.5.50-generic and nvidia- driver-515 and an Nvidia gtx 1070. All was working under linux-image-5.1.5.48 -- 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1991833] Re: VRF Kernel Module Does Not Exist
Well I didn't realize I could just install them with linux-modules- extra-$(uname -r) package. I was able to do this and get the needed kernel module. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1991833 Title: VRF Kernel Module Does Not Exist Status in linux-aws package in Ubuntu: New Bug description: On a standard Ubuntu 22.04 LTS image, the vrf module exists and can be loaded. The AMI image ami-08c40ec9ead489470 in AWS us-east-1 (and all other regions that I have tested) does not have this kernel module built therefore I cannot create vrf network devices. Usually I could run `ip link add vrf-mgmt type vrf table 10` and create the VRF device, but instead get an error `Error: Unknown device type.`. Trying to load the module: # modprobe vrf modprobe: FATAL: Module vrf not found in directory /lib/modules/5.15.0-1020-aws # Boot config # grep VRF /boot/config-5.15.0-1020-aws CONFIG_NET_VRF=m ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-aws-headers-5.15.0-1020 5.15.0-1020.24 ProcVersionSignature: Ubuntu 5.15.0-1020.24-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 5 18:41:11 2022 Ec2AMI: ami-08c40ec9ead489470 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1a Ec2InstanceType: t3.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1991833/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Can confirm the bug, with linux-image-5.1.5.50-generic and nvidia- driver-515. -- 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all
Hello there, is there anything I can do to help fix this issue please? -- 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/1981433 Title: [Asus Zenbook UX3402ZA] Sound doesn't work at all Status in linux package in Ubuntu: Confirmed Bug description: Sound/speakers don't work at all on Asus Zenbook 14 OLED and other similar models with Realtek ALC294. No solution works. Audio is not muted, tried adding snd-hda arguments - no dice. This has been reported numerous times, when will a fix finally be rolled out?! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1730 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 12 13:57:05 2022 InstallationDate: Installed on 2022-07-12 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+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 1992320] Re: boot hangs with 5.19.0.19.19
*** This bug is a duplicate of bug 1991704 *** https://bugs.launchpad.net/bugs/1991704 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992320 Title: boot hangs with 5.19.0.19.19 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to the 5.19.0.19.19 kernel (from 5.19.0-15.15) my machine hangs when transitioning to plymouth. To boot successfully I either have to use grub to select the older 5.19.0-15.15 kernel OR boot into recovery mode and then choose to resume boot. This occurs both with my laptop docked via a Thinkpad Thunderbolt 3 dock or when undocked. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic 5.19.0.19.19 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 10 16:25:52 2022 InstallationDate: Installed on 2021-08-03 (433 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) MachineType: LENOVO 20XWCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/vgubuntu-root ro quiet splash intel_iommu=igfx_off PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-08-27 (44 days ago) dmi.bios.date: 08/29/2022 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET80W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET80W(1.56):bd08/29/2022:br1.56:efr1.33:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992320/+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 1980805] Re: Backport packages for 20.04.5 HWE stack
** Changed in: llvm-toolchain-13 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to mesa-amber in Ubuntu. https://bugs.launchpad.net/bugs/1980805 Title: Backport packages for 20.04.5 HWE stack Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-13 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in mesa-amber package in Ubuntu: Invalid Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-13 source package in Focal: Fix Committed Status in mesa source package in Focal: New Status in mesa-amber source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.5 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] libdrm: pci-id updates, some minor api updates mesa: a new major release, but we'll pull the final stable release of 22.0.x series, so there shouldn't be any regressions left at that point mesa-amber: forked from mesa 21.3.x, this LTS branch keeps old DRI drivers that were removed from main mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1980805/+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 1991691] Re: cannot change mount namespace
I can confirm that 5.19.0-21-generic in kinetic-proposed does indeed fix this issue for me. -- 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/1991691 Title: cannot change mount namespace Status in Linux: New Status in linux package in Ubuntu: Fix Committed Status in snapd package in Ubuntu: Incomplete Bug description: Multiple snaps are either broken or "only" display permission denied messages. slack snap is not starting at all with: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied firefox snap does start, but also logs errors: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat /var/lib/snapd/hostfs/usr/share/doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat /var/lib/snapd/hostfs/usr/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat /usr/local/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat /var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Oct 4 17:29:01 2022 InstallationDate: Installed on 2017-09-26 (1834 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1991691/+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 1979352] Re: system frozen after sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upower (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/1979352 Title: system frozen after sleep Status in Ubuntu MATE: Confirmed Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly but, at that time it was only apparent when I was using video ripping software on separate laptops and only when the machines became idle once the ripping program had finished. I don't think this bug was ever fixed and so I'm returning to it because I left my laptop in sleep mode over meal time to come back to a frozen system. I was not using the video ripping program this time, just surfing the Net. No other program was open. I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has happened when using an old Dell 1530 laptop. I do not believe I am unique in having this bug as someone has a similar bug when they have minimised Google Chrome and their system had went to sleep. I was also using Chrome this time but, as I have already said I was having this happen using another program and not using Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 1979352] Re: system frozen after sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (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/1979352 Title: system frozen after sleep Status in Ubuntu MATE: Confirmed Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly but, at that time it was only apparent when I was using video ripping software on separate laptops and only when the machines became idle once the ripping program had finished. I don't think this bug was ever fixed and so I'm returning to it because I left my laptop in sleep mode over meal time to come back to a frozen system. I was not using the video ripping program this time, just surfing the Net. No other program was open. I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has happened when using an old Dell 1530 laptop. I do not believe I am unique in having this bug as someone has a similar bug when they have minimised Google Chrome and their system had went to sleep. I was also using Chrome this time but, as I have already said I was having this happen using another program and not using Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 1979352] Re: system frozen after sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: acpid (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/1979352 Title: system frozen after sleep Status in Ubuntu MATE: Confirmed Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly but, at that time it was only apparent when I was using video ripping software on separate laptops and only when the machines became idle once the ripping program had finished. I don't think this bug was ever fixed and so I'm returning to it because I left my laptop in sleep mode over meal time to come back to a frozen system. I was not using the video ripping program this time, just surfing the Net. No other program was open. I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has happened when using an old Dell 1530 laptop. I do not believe I am unique in having this bug as someone has a similar bug when they have minimised Google Chrome and their system had went to sleep. I was also using Chrome this time but, as I have already said I was having this happen using another program and not using Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 1979352] Re: system frozen after sleep
Maybe related to this https://github.com/mate-desktop/mate- desktop/issues/519 ** Bug watch added: github.com/mate-desktop/mate-desktop/issues #519 https://github.com/mate-desktop/mate-desktop/issues/519 -- 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/1979352 Title: system frozen after sleep Status in Ubuntu MATE: Confirmed Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly but, at that time it was only apparent when I was using video ripping software on separate laptops and only when the machines became idle once the ripping program had finished. I don't think this bug was ever fixed and so I'm returning to it because I left my laptop in sleep mode over meal time to come back to a frozen system. I was not using the video ripping program this time, just surfing the Net. No other program was open. I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has happened when using an old Dell 1530 laptop. I do not believe I am unique in having this bug as someone has a similar bug when they have minimised Google Chrome and their system had went to sleep. I was also using Chrome this time but, as I have already said I was having this happen using another program and not using Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 1987699] Re: azure: CIFS Backport Updates to 5.15 Kernel
Patches submitted: https://lists.ubuntu.com/archives/kernel- team/2022-October/134000.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1987699 Title: azure: CIFS Backport Updates to 5.15 Kernel Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] Microsoft has requested updating CIFS to the 5.15 backport as published in 'git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport'. [Test Plan] Microsoft tested [Where things could go wrong] CIFS network connections could misbehave [Other Info] SF: #00343105 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1987699/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144
Here's a bit more information about the service failure: -- Logs begin at Sun 2022-09-25 00:05:05 UTC, end at Thu 2022-09-29 12:03:20 UTC. -- Sep 29 12:02:57 autopkgtest-lxd-fexenj systemd-remount-fs[74]: mount: /: can't find LABEL=cloudimg-rootfs. Sep 29 12:02:57 autopkgtest-lxd-fexenj systemd-remount-fs[59]: /bin/mount for / exited with exit status 1. Sep 29 12:02:57 autopkgtest-lxd-fexenj systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE Sep 29 12:02:57 autopkgtest-lxd-fexenj systemd[1]: systemd-remount-fs.service: Failed with result 'exit-code'. Sep 29 12:02:57 autopkgtest-lxd-fexenj systemd[1]: Failed to start Remount Root and Kernel File Systems. FAIL This makes me think it's bug 1576341 again. According to the git history, that patch was not carried in Ubuntu past 2019. I will try to find out if we ever attempted to upstream the change. ** Tags removed: foundations-triage-discuss ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/1991285 Title: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/5.4.0-128.144 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1992823] [NEW] package nvidia-dkms-515 515.65.01-0ubuntu0.22.04.1 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-515 script post-installation devolvió el
Public bug reported: i can't detect my 2 monitors ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-515 515.65.01-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Oct 13 17:24:41 2022 ErrorMessage: el subproceso instalado paquete nvidia-dkms-515 script post-installation devolvió el código de salida de error 10 InstallationDate: Installed on 2021-12-05 (311 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: nvidia-graphics-drivers-515 Title: package nvidia-dkms-515 515.65.01-0ubuntu0.22.04.1 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-515 script post-installation devolvió el código de salida de error 10 UpgradeStatus: Upgraded to jammy on 2022-09-18 (24 days ago) ** Affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu. https://bugs.launchpad.net/bugs/1992823 Title: package nvidia-dkms-515 515.65.01-0ubuntu0.22.04.1 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-515 script post-installation devolvió el código de salida de error 10 Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: i can't detect my 2 monitors ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-515 515.65.01-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Oct 13 17:24:41 2022 ErrorMessage: el subproceso instalado paquete nvidia-dkms-515 script post-installation devolvió el código de salida de error 10 InstallationDate: Installed on 2021-12-05 (311 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: nvidia-graphics-drivers-515 Title: package nvidia-dkms-515 515.65.01-0ubuntu0.22.04.1 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-515 script post-installation devolvió el código de salida de error 10 UpgradeStatus: Upgraded to jammy on 2022-09-18 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1992823/+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 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date
** Tags removed: foundations-triage-discuss ** Tags added: foundations-todo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/1992513 Title: apt will not install nvidia-driver-470-server if nvidia- driver-450-server is installed and out of date Status in apt package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Status in nvidia-graphics-drivers-470-server package in Ubuntu: New Bug description: apt/jammy apt will refuse to install nvidia-driver-470-server if nvidia-driver-450-server is installed *and* out of date. I can reproduce this by disabling all but the jammy release pocket, installing the old n-d-450-s from there, and then enabling updates and trying to install n-v-470-s (where a new n-d-450-s is available): # libnvidia-gl-450-server has an update available root@dannf-apt-jammy:/var/cache# apt install --dry-run libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libnvidia-common-450-server : Conflicts: libnvidia-common libnvidia-common-470-server : Conflicts: libnvidia-common E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992513/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-515 (Ubuntu Jammy) 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-515 (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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-510 (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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-510 (Ubuntu Jammy) 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
I can confirm the bug. My system uses the Nvidia 1050ti chipset. I can only boot the kernel if I set nomodeset parameter in the boot options or using the older 5.15.0-48 kernel -- 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1964093] Re: nfsver=3, udp not working anymore
yes, I confirm. You cannot mount nfs3 shares over udp served by your SPARCstation with 22.04 as client running the standard kernel due to the option CONFIG_NFS_DISABLE_UDP_SUPPORT=y. I don't know what would be necessary to add nfs3-udp to the kernel. Maybe changing CONFIG_NFS_DISABLE_UDP_SUPPORT=n and recompiling will work, but there could also be options necessary to be changed, too. -- 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/1964093 Title: nfsver=3,udp not working anymore Status in linux package in Ubuntu: Confirmed Bug description: Package: nfs-kernel-server Architecture: amd64 Version: 1:2.6.1-1~exp1ubuntu1 nfsversion 3 with proto udp seems not to be supported by the nfs- kernel-server anymore. In Ubuntu 18.04 (nfs-kernel-server 1:1.3.4-2.1ubuntu5) it was still possible. I could mount with either tcp or udp: 1. tcp mount -o nfsvers=3 192.168.0.1:/srv/nfs/testshare /mnt mount|grep mnt: 192.168.0.1:/srv/nfs/testshare on /mnt type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1) 2. udp mount -o nfsvers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt mount|grep mnt: 192.168.0.1:/srv/nfs/testshare on /mnt type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1) Now in Ubuntu 22.04 I get the message: mount.nfs: an incorrect mount option was specified I tried to enable upd in /etc/nfs.conf in section [nfsd]: [nfsd] # debug=0 # threads=8 # host= # port=0 # grace-time=90 # lease-time=90 # udp=n udp=y # tcp=y # vers2=n # vers3=y But there was no effect. nfs3 with udp is needed by several busybox mount binaries in initrds of Knoppix and other live distributions used via PXE boot. Best regards Jörg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964093/+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 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
** Changed in: hwe-next Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1988797 Title: pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non- Fatal), type=Transaction Layer, (Requester ID) Status in HWE Next: Confirmed Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Confirmed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: My kernel log periodically bursts with: [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.593393] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.598564] pcieport :00:1b.0:[20] UnsupReq (First) [10405.603829] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.614959] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.620296] pcieport :00:1b.0:[20] UnsupReq (First) [10405.625554] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.636495] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.641867] pcieport :00:1b.0:[20] UnsupReq (First) [10405.647169] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.658369] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.663803] pcieport :00:1b.0:[20] UnsupReq (First) [10405.669263] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.680699] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.686267] pcieport :00:1b.0:[20] UnsupReq (First) [10405.691759] pcieport :00:1b.0: AER: TLP Header: 3400 0152 This has happened even since I got the machine. It also happened with 5.15. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2477 F wireplumber /dev/snd/seq:dan2474 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 6 13:52:35 2022 InstallationDate: Installed on 2022-07-20 (47 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: Intel(R) Client Systems NUC12DCMi7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias:
[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1988797 Title: pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non- Fatal), type=Transaction Layer, (Requester ID) Status in HWE Next: Confirmed Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Confirmed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: My kernel log periodically bursts with: [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.593393] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.598564] pcieport :00:1b.0:[20] UnsupReq (First) [10405.603829] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.614959] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.620296] pcieport :00:1b.0:[20] UnsupReq (First) [10405.625554] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.636495] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.641867] pcieport :00:1b.0:[20] UnsupReq (First) [10405.647169] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.658369] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.663803] pcieport :00:1b.0:[20] UnsupReq (First) [10405.669263] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.680699] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.686267] pcieport :00:1b.0:[20] UnsupReq (First) [10405.691759] pcieport :00:1b.0: AER: TLP Header: 3400 0152 This has happened even since I got the machine. It also happened with 5.15. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2477 F wireplumber /dev/snd/seq:dan2474 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 6 13:52:35 2022 InstallationDate: Installed on 2022-07-20 (47 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: Intel(R) Client Systems NUC12DCMi7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35
[Kernel-packages] [Bug 1991974] Re: AMD Yellow Carp system hang on HDMI plug in/out over HP hook2 docking
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: hwe-next Importance: Undecided => Critical ** Changed in: hwe-next Status: New => Fix Released ** Changed in: hwe-next Status: Fix Released => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1991974 Title: AMD Yellow Carp system hang on HDMI plug in/out over HP hook2 docking Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] AMD Yellow Carp system hang on HDMI plug in/out over dock station. [Fix] 5 patches from mainline kernel v5.16 to be backported. [Test Case] Plug and unplug HDMI cable connected external monitor on a docking station connected to HP Lockheed platform to try trigger system hang. [Where problems could occur] This series tries to address null state of MST link encoder, and no know fix commits for them ever since till current mainline HEAD. [Other Info] While this is already available in v5.16 kernel and on, only 5.15 and oem-5.14 are nominated for fix. == original bug description == In order to resolve system hang during docking scenario with HDMI plug in/out, these patches are needed into hwe-5.15. v5.16 43dc2ad5 drm/amd/display: Fix MST link encoder availability check e3ab29aa drm/amd/display: Fix for link encoder access for MST 7fb52632 drm/amd/display: FEC configuration for dpia links ed0ffb5d drm/amd/display: FEC configuration for dpia links in MST mode c9beecc5 drm/amd/display: Add work around for tunneled MST To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991974/+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 1990920] Re: Fix resume on AMD platforms when TBT monitor is plugged
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1990920 Title: Fix resume on AMD platforms when TBT monitor is plugged Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Confirmed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] When TBT monitor is connected to AMD platform, system resume will hit stack corruption or BUG_ON() macro. [Fix] Revert the offending commit and handle MST properly. [Test] The system can resume normally and no more kernel splat. [Where problems could occur] The new logic is restriced to MST hub, so normal DP/HDMI usage should be unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990920/+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 1991704] Re: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
Installing linux-image-5.19.0-20-generic from kinetic-proposed resolved this issue for me. -- 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/1991704 Title: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen Status in linux package in Ubuntu: Fix Committed Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+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 1992647] Status changed to Confirmed
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/1992647 Title: [Acer Spin SP314-54N] Touchpad not recognized Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Bug description: Touchpad not recognized ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guilherme 1780 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 14:09:35 2022 InstallationDate: Installed on 2022-10-07 (4 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Spin SP314-54N ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=UUID=ce47c382-5d2f-4ad1-966d-cadcfe91cbe7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.12 dmi.board.name: Lenny_IL dmi.board.vendor: IL dmi.board.version: V1.12 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.12:bd03/15/2021:br1.12:efr1.7:svnAcer:pnSpinSP314-54N:pvrV1.12:rvnIL:rnLenny_IL:rvrV1.12:cvnAcer:ct31:cvrV1.12:sku: dmi.product.family: Spin 3 dmi.product.name: Spin SP314-54N dmi.product.sku: dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992647/+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 1992679] Status changed to Confirmed
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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: New Status in nvidia-graphics-drivers-515 source package in Jammy: New Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1979633] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623922/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623934/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623932/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623933/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623938/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623935/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623936/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623937/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623913/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623931/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623920/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623917/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623921/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623918/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1992788] [NEW] package nvidia-dkms-470 470.141.03-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit s
Public bug reported: Running Ubuntu 22.10 with kernel 6.0.1, Package worked before the kernel upgrade, reverts to Xorg. Might be due to my old NVIDIA GeForce GTX 650 Ti GPU. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: nvidia-dkms-470 470.141.03-0ubuntu1 Uname: Linux 6.0.1-060001-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Oct 13 12:39:52 2022 ErrorMessage: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-10-02 (10 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Daily amd64 (20221001) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-dkms-470 470.141.03-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kinetic need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1992788 Title: package nvidia-dkms-470 470.141.03-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Running Ubuntu 22.10 with kernel 6.0.1, Package worked before the kernel upgrade, reverts to Xorg. Might be due to my old NVIDIA GeForce GTX 650 Ti GPU. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: nvidia-dkms-470 470.141.03-0ubuntu1 Uname: Linux 6.0.1-060001-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Oct 13 12:39:52 2022 ErrorMessage: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-10-02 (10 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Daily amd64 (20221001) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-dkms-470 470.141.03-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1992788/+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 1979633] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623914/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623919/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623916/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623912/+files/CRDA.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/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623915/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 5120 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy Uname: Linux 5.15.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 04/11/2022 dmi.bios.release: 7.15 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.15RTR2 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.6 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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 1979633] Re: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated"
apport information ** Tags added: apport-collected ** Description changed: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: bonnaudl 5120 F pulseaudio + CasperMD5CheckResult: unknown + CurrentDesktop: KDE + DistroRelease: Ubuntu 22.04 + MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-50-generic N/A + linux-backports-modules-5.15.0-50-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.6 + Tags: jammy + Uname: Linux 5.15.0-50-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip disk fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo + _MarkForUpload: True + dmi.bios.date: 04/11/2022 + dmi.bios.release: 7.15 + dmi.bios.vendor: INSYDE Corp. + dmi.bios.version: 1.07.15RTR2 + dmi.board.asset.tag: Tag 12345 + dmi.board.name: NS50_70MU + dmi.board.vendor: TUXEDO + dmi.board.version: Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Notebook + dmi.chassis.version: N/A + dmi.ec.firmware.release: 7.6 + dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.15RTR2:bd04/11/2022:br7.15:efr7.6:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: + dmi.product.family: Not Applicable + dmi.product.name: TUXEDO InfinityBook S 15 Gen6 + dmi.product.sku: Not Applicable + dmi.product.version: Not Applicable + dmi.sys.vendor: TUXEDO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1979633/+attachment/5623911/+files/AlsaInfo.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/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel:
[Kernel-packages] [Bug 1992593] Status changed to Confirmed
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/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-515 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: New Status in nvidia-graphics-drivers-515 source package in Jammy: New Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+subscriptions --
[Kernel-packages] [Bug 1992593] Re: HDMI port not working after upgrade to 5.15.0-50-generic
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: New Status in linux source package in Jammy: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992647] Re: [Acer Spin SP314-54N] Touchpad not recognized
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992647 Title: [Acer Spin SP314-54N] Touchpad not recognized Status in linux package in Ubuntu: New Status in linux source package in Jammy: Confirmed Bug description: Touchpad not recognized ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guilherme 1780 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 14:09:35 2022 InstallationDate: Installed on 2022-10-07 (4 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Spin SP314-54N ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=UUID=ce47c382-5d2f-4ad1-966d-cadcfe91cbe7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.12 dmi.board.name: Lenny_IL dmi.board.vendor: IL dmi.board.version: V1.12 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.12:bd03/15/2021:br1.12:efr1.7:svnAcer:pnSpinSP314-54N:pvrV1.12:rvnIL:rnLenny_IL:rvrV1.12:cvnAcer:ct31:cvrV1.12:sku: dmi.product.family: Spin 3 dmi.product.name: Spin SP314-54N dmi.product.sku: dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992647/+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 1991691] Re: cannot change mount namespace
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991691 Title: cannot change mount namespace Status in Linux: New Status in linux package in Ubuntu: Fix Committed Status in snapd package in Ubuntu: Incomplete Bug description: Multiple snaps are either broken or "only" display permission denied messages. slack snap is not starting at all with: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied firefox snap does start, but also logs errors: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat /var/lib/snapd/hostfs/usr/share/doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat /var/lib/snapd/hostfs/usr/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat /usr/local/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat /var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Oct 4 17:29:01 2022 InstallationDate: Installed on 2017-09-26 (1834 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1991691/+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 1992593] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623883/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623882/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623881/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623888/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623887/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623885/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623886/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623884/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623880/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623876/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623879/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623877/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623875/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623873/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623878/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623874/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623872/+files/CRDA.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/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 1.187.33 Tags: focal Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2021 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07.A03 dmi.board.asset.tag: Standard dmi.board.name: PF5NU1G dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: Standard dmi.ec.firmware.release: 1.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: dmi.product.name: SCHENKER VIA 15 Pro dmi.product.sku: SVI15PM20 dmi.product.version: Standard dmi.sys.vendor: SchenkerTechnologiesGmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992593/+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 1992593] Re: HDMI port not working after upgrade to 5.15.0-50-generic
apport information ** Tags added: apport-collected focal ** Description changed: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.24 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: ali2669 F pipewire-media- + /dev/snd/controlC0: ali2669 F pipewire-media- + /dev/snd/seq:ali2668 F pipewire + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2022-01-25 (260 days ago) + InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) + MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.15.0-46-generic N/A + linux-backports-modules-5.15.0-46-generic N/A + linux-firmware 1.187.33 + Tags: focal + Uname: Linux 5.15.0-46-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/11/2021 + dmi.bios.release: 5.16 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: N.1.07.A03 + dmi.board.asset.tag: Standard + dmi.board.name: PF5NU1G + dmi.board.vendor: NB02 + dmi.board.version: Standard + dmi.chassis.asset.tag: Standard + dmi.chassis.type: 10 + dmi.chassis.vendor: SchenkerTechnologiesGmbH + dmi.chassis.version: Standard + dmi.ec.firmware.release: 1.7 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07.A03:bd05/11/2021:br5.16:efr1.7:svnSchenkerTechnologiesGmbH:pnSCHENKERVIA15Pro:pvrStandard:rvnNB02:rnPF5NU1G:rvrStandard:cvnSchenkerTechnologiesGmbH:ct10:cvrStandard:skuSVI15PM20: + dmi.product.name: SCHENKER VIA 15 Pro + dmi.product.sku: SVI15PM20 + dmi.product.version: Standard + dmi.sys.vendor: SchenkerTechnologiesGmbH ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1992593/+attachment/5623871/+files/AlsaInfo.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/1992593 Title: HDMI port not working after upgrade to 5.15.0-50-generic Status in linux package in Ubuntu: Confirmed Bug description: Yesterday i upgraded the linux kernel from 5.15.0-46-generic to 5.15.0-50. After rebooting the second monitor was not getting detected (connected via HDMI cable). When i booted back from 5.15.0-46, the monitor worked again. I am running Ubuntu 20.04.5 LTS *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:04:00.0 version: c6 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list configuration: driver=amdgpu latency=0 resources: irq:45 memory:d000-dfff memory:e000-e01f ioport:e000(size=256) memory:fe60-fe67 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ali2669 F pipewire-media- /dev/snd/controlC0: ali2669 F pipewire-media- /dev/snd/seq:ali2668 F pipewire CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-25 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: SchenkerTechnologiesGmbH SCHENKER VIA 15 Pro NonfreeKernelModules: zfs zunicode
[Kernel-packages] [Bug 1971712] Re: Add support for Intel DG2
you need to use i915.force_probe until maybe 6.2, but other than that it works quite well for the most part even in 6.0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: In Progress Status in mesa source package in Jammy: Fix Released Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1988018] Re: [mlx5] Intermittent VF-LAG activation failure
** Changed in: netplan.io (Ubuntu Kinetic) Status: New => Triaged ** Changed in: netplan.io (Ubuntu Kinetic) Importance: Undecided => Medium ** Tags added: foundations-triage-discuss -- 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/1988018 Title: [mlx5] Intermittent VF-LAG activation failure Status in linux package in Ubuntu: Fix Committed Status in netplan.io package in Ubuntu: Triaged Status in linux source package in Jammy: New Status in netplan.io source package in Jammy: New Status in linux source package in Kinetic: Fix Committed Status in netplan.io source package in Kinetic: Triaged Bug description: During system initialization there is a specific sequence that must be followed to enable the use of hardware offload and VF-LAG. Intermittently one may see that VF-LAG initialization fails: [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: lag map port 1:1 port 2:2 shared_fdb:1 [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_cmd_check:782:(pid 9): CREATE_LAG(0x840) op_mod(0x0) failed, status bad parameter(0x3), syndrome (0x7d49cb) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_create_lag:248:(pid 9): Failed to create LAG (-22) [Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: mlx5_activate_lag:288:(pid 9): Failed to activate VF LAG Make sure all VFs are unbound prior to VF LAG activation or deactivation This is caused by rebinding the driver prior to the VF lag being ready. A sysfs knob has recently been added to the driver [0] and we should monitor it before attempting to rebind the driver: $ cat /sys/kernel/debug/mlx5/\:08\:00.0/lag/state The kernel feature is available in the upcoming Kinetic 5.19 kernel and we should probably backport it to the Jammy 5.15 kernel. 0: https://github.com/torvalds/linux/commit/7f46a0b7327ae261f9981888708dbca22c283900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988018/+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 1737428] Re: VRF support to solve routing problems associated with multi-homing
Basic VRF support landed in netplan v0.105: https://github.com/canonical/netplan/pull/285 ** Changed in: netplan.io (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737428 Title: VRF support to solve routing problems associated with multi-homing Status in juju: Incomplete Status in MAAS: Invalid Status in linux package in Ubuntu: Incomplete Status in netplan.io package in Ubuntu: Fix Released Bug description: Problem description: * a host is multi-homed if it has multiple network interfaces with L3 addresses configured (physical or virtual interfaces, natural to OpenStack regardless of IPv4/IPv6 and IPv6 in general); (see 3.3.4 Local Multihoming https://tools.ietf.org/html/rfc1122#page-60 and 3.3.4.2 Multihoming Requirements) * if all hosts that need to participate in L3 communication are located on the same L2 network there is no need for a routing device to be present. ARP/NDP and auto-created directly connected routes are enough; * multi-homing with hosts located on different L2 networks requires more intelligent routing: - "directly connected" routes are no longer enough to talk to all relevant hosts in the same network space; - a default gateway in the main routing table may not be the correct routing device that knows where to forward traffic (management network traffic goes to a management switch and router, other traffic goes to L3 ToR switch but may go via different bonds); - even if a default gateway knows where to forward traffic, it may not be the intended physical path (storage replication traffic must go through a specific outgoing interface, not the same interface as storage access traffic although both interfaces are connected to the same ToR); - there is no longer a single "default gateway" as applications need either per-logical-direction routers or to become routers themselves (if destination == X, forward to next-hop Y). Leaf-spine architecture is a good example of how multiple L2 networks force you to use spaces that have VLANs in different switch fabrics => one or more hops between hosts with interfaces associated with the same network space; - while network spaces implicitly require L3 reachability between each host that has a NIC associated with a network space, the current definition does not mention routing infrastructure required for that. For a single L2 this problem is hidden by directly connected routes, for multi-L2, no solution is provided or discussed; * existing solutions to multi-homing require routing table management on a given host: complex static routing rules, dynamic routing (e.g. running an OSPF or BGP daemon on a host); * using static routes is rigid and requires network planning (i.e. working with network engineers which may have varying degrees of experience, doing VLSM planning etc.); * using dynamic routing requires a broader integration into an organization's L3 network infrastructure. Routing can be implemented differently across different organizations and it is a security and operational burden to integrate with a company's routing infrastructure. Summary: a mechanism is needed to associate an interface with a forwarding table (FIB) which has its own default gateway and make an application with a listen(2)ing socket(2) return connected sockets associated with different FIBs. In other words, applications need to implicitly get source/destination-based routing capabilities without the need to use static routing schemes or dynamic routing and with minimum or no modifications to the applications themselves. Goals: * avoid turning individual hosts into routers; * avoid complex static rules; * better support multi-fabric deployments with minimum effort (Juju, charms, MAAS, applications, network infrastructure); * reduce operational complexity (custom L3 infrastructure integration for each deployment); * reduce delivery risks (L3 infrastructure, L3 department responsiveness varies); * avoid any form of L2 stretching at the infrastructure level - this is inefficient for various reasons. NOTE: https://cumulusnetworks.com/blog/vrf-for-linux/ - I recommend to read this post to understand suggestions below. How to solve it? What does it mean for Juju to support VRF devices? * enslave certain devices on provisioning based on network space information (physical NICs, VLAN devices, bonds AND bridges created for containers must be considered) - VRF devices logically enslave devices similar to bridges but work differently (on L3, not L2); * the above is per network namespace so it will work equally well in a LXD container; Conceptually: # echo 'net.ipv4.tcp_l3mdev_accept = 1' >> /etc/sysctl.conf # echo 'net.ipv4.udp_l3mdev_accept = 1' >>
[Kernel-packages] [Bug 1992667] Re: Application windows invisible (on DG2 graphics)
I've managed to reproduce this bug on an Arc A380 and Arc A770 GPU. I've attached the requested lspci output for the A770. Ubuntu 22.04 has already received a mesa update with backported patches for DG2 support: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1971712 I haven't tried 22.10 yet, but I will do so in the coming days. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992667/+attachment/5623860/+files/lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992667 Title: Application windows invisible (on DG2 graphics) Status in linux-oem-6.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: When using GNOME Shell with Wayland, all application windows become invisible from time to time. This usually happens right after starting GNOME Shell for the first time or after having a VRAM intensive application open, such as a game. I have installed the latest linux-oem-6.0 kernel and manually enabled support for DG2 graphics by passing the i915.force_probe parameter with the PCIe ID of the graphics card. I have attached a screenshot of the described behavior below. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0 Uname: Linux 6.0.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Oct 12 17:23:40 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-11 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash 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/ubuntu/+source/linux-oem-6.0/+bug/1992667/+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 1992756] Re: Screen turns black for a long time after each login and when detecting screens or changing screen layout.
Thanks for the bug report. Please collect a log from when the bug is happening by: 1. Open a Terminal window and run: lspci -k > lspci.txt journalctl -f > recentjournal.txt Leave it running. 2. Reproduce the bug. 3. Press Ctrl+C in the Terminal window. 4. Attach the two resulting text files here. ** Tags added: hybrid i915 multigpu nvidia ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Also affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu. https://bugs.launchpad.net/bugs/1992756 Title: Screen turns black for a long time after each login and when detecting screens or changing screen layout. Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-515 package in Ubuntu: Incomplete Bug description: I have a Thinkpad P15 with a A2000 GPU with Ubuntu 22.04.1 LTS. This happens using Wayland and nvidia cuda drivers. It seems like the system uses very long to identify the screens. This happens when I use external monitors, but also when only using the laptop screen. Changing the screen layout takes so long that I am unable to accept the change before it is reverted to the previous. Only the mouse pointer is visible, the rest of the screens are black during this process. $ apt-cache policy cuda cuda: Installed: 11.7.1-1 Candidate: 11.8.0-1 Version table: 11.8.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages *** 11.7.1-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages 100 /var/lib/dpkg/status 11.7.0-1 600 600 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64 Packages $ nvidia-smi Thu Oct 13 10:46:02 2022 +-+ | NVIDIA-SMI 515.65.01Driver Version: 515.65.01CUDA Version: 11.7 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA RTX A200... On | :01:00.0 On | N/A | | N/A 46CP5 8W / N/A |146MiB / 4096MiB | 22% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 4451 G /usr/lib/xorg/Xorg145MiB | +-+ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 13 10:25:17 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-05 (37 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. 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/ubuntu/+source/gnome-shell/+bug/1992756/+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 1992435] Re: sof-hda-dsp Dmic0 not initial correctly
This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu2 --- alsa-ucm-conf (1.2.6.3-1ubuntu2) kinetic; urgency=medium * Backport patch to fix sof-hda-dsp Dmic0 initial. (LP: #1992435) -- Dirk Su Tue, 11 Oct 2022 16:09:17 +0800 ** Changed in: alsa-ucm-conf (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1992435 Title: sof-hda-dsp Dmic0 not initial correctly Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Bug description: [Impact] Device use sof-hda-dsp driver will not able to initial the Dmic0 status correctly [Test Plan] 1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service" 2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state" 3. reboot system 4. Dmic should be on and volume set to 70% [Where problems could occur] Only fix for Dmic0 control and upstream already merged the code. The risk will be low [Other Info] Pull Request in upstream https://github.com/alsa-project/alsa-ucm-conf/pull/132 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1992435/+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 1992679] Status changed to Confirmed
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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1930130] Re: package linux-image-4.15.0-142-generic 4.15.0-142.146~16.04.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1930130 Title: package linux-image-4.15.0-142-generic 4.15.0-142.146~16.04.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in linux-signed-hwe package in Ubuntu: Confirmed Bug description: I was trying to remove old kernel ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-142-generic 4.15.0-142.146~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 AptOrdering: linux-modules-extra-4.15.0-142-generic: Purge linux-image-4.15.0-142-generic: Purge linux-image-unsigned-4.15.0-142-generic: Install linux-image-unsigned-4.15.0-142-generic: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat May 29 16:41:28 2021 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2020-03-17 (438 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.2 SourcePackage: linux-signed-hwe Title: package linux-image-4.15.0-142-generic 4.15.0-142.146~16.04.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2021-01-07 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1930130/+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 1992679] Re: Can not login after new kernel installed
** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: Incomplete => New ** Also affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Can not login after new kernel installed + Can not login after new kernel installed (nvidia driver crashed) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: New Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1991691] Re: cannot change mount namespace
fwiw; I can confirm that the proposed patch also fixes issues with LXD virtual machines and block devices that was present on 5.19.0-19 and 5.19.0-20 ref bug 1992564. -- 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/1991691 Title: cannot change mount namespace Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Incomplete Bug description: Multiple snaps are either broken or "only" display permission denied messages. slack snap is not starting at all with: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied firefox snap does start, but also logs errors: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat /var/lib/snapd/hostfs/usr/share/doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat /var/lib/snapd/hostfs/usr/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat /usr/local/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat /var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Oct 4 17:29:01 2022 InstallationDate: Installed on 2017-09-26 (1834 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1991691/+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 1992564] Re: [kinetic] 5.19.0-19 and 5.19.0-20 kernels, lxd virtual-machine with block device not working
*** This bug is a duplicate of bug 1991691 *** https://bugs.launchpad.net/bugs/1991691 ** This bug has been marked a duplicate of bug 1991691 cannot change mount namespace -- 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/1992564 Title: [kinetic] 5.19.0-19 and 5.19.0-20 kernels, lxd virtual-machine with block device not working Status in linux package in Ubuntu: Confirmed Bug description: $ uname -a Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 Codename: kinetic $ snap info lxd | grep ^installed installed: 5.6-794016a (23680) 142MB - $ lxc storage show pool config: lvm.thinpool_name: lxd-pool lvm.use_thinpool: "true" lvm.vg.force_reuse: "true" lvm.vg_name: vgubuntu source: vgubuntu volatile.initial_source: vgubuntu volume.lvm.stripes: "3" description: "" name: pool driver: lvm $ lxc start actual-beagle Error: Failed setting up device via monitor: Failed adding block device for disk device "root": Failed adding block device: The device is not writable: Permission denied Downgrading to 5.19.0-18 makes it work again --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-18 (631 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230) MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 Tags: kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx: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: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+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 1992753] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1992753 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/1992753 Title: Intel Media driver DG1 AVC encode is broken. Status in linux package in Ubuntu: Incomplete Bug description: AVC Encode is broken with intel-media-driver-non-free (possibly also free version, haven't tested). Applying https://github.com/intel/media-driver/pull/1500 to upstream master fixed this for me. Can this be backported? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992753/+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 1992753] Re: Intel Media driver DG1 AVC encode is broken.
apt-cache show intel-media-va-driver-non-free Package: intel-media-va-driver-non-free Architecture: amd64 Version: 22.4.3+ds1-1 Multi-Arch: same Priority: optional Section: multiverse/video Source: intel-media-driver-non-free Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian Multimedia Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 32249 Provides: va-driver Depends: libva-driver-abi-1.14, libc6 (>= 2.34), libgcc-s1 (>= 3.3.1), libigdgmm12 (>= 22.1.3+ds1), libstdc++6 (>= 11) Conflicts: intel-media-va-driver Filename: pool/multiverse/i/intel-media-driver-non-free/intel-media-va-driver-non-free_22.4.3+ds1-1_amd64.deb Size: 5427282 MD5sum: f476891e25b642ba99c3bbb02e1d901e SHA1: 494c08749087ea8dcff66708d0f35496617946d6 SHA256: 0354dde03ddc81720ff0de9105ce288fdccaa4be7bdc86fe7e1725929e8c52c5 SHA512: d1d3a28201f7cbaa7011f3030f77056930798e0033501c662f952f375fa2bca83b0733cf39b4092af05c9f6640f91ed8fdcfda49422831439db7081dd0178d42 Homepage: https://github.com/intel/media-driver Description-en: VAAPI driver for the Intel GEN8+ Graphics family The VA-API (Video Acceleration API) enables hardware accelerated video decode/encode at various entry-points (VLD, IDCT, Motion Compensation etc.) for the prevailing coding standards today (MPEG-2, MPEG-4 ASP/H.263, MPEG-4 AVC/H.264, and VC-1/WMV3). It provides an interface to fully expose the video decode capabilities in today's GPUs. . This package contains the video decode and encode driver backend for the Intel HD Graphics of the Intel Core processor family. The supported platforms include: * Broadwell * Skylake * Broxton * Apollo Lake * Kaby Lake * Coffee Lake * Whiskey Lake * Cannon Lake * Ice Lake Description-md5: d0cac4050b590c0314de696b91343b77 -- 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/1992753 Title: Intel Media driver DG1 AVC encode is broken. Status in linux package in Ubuntu: Incomplete Bug description: AVC Encode is broken with intel-media-driver-non-free (possibly also free version, haven't tested). Applying https://github.com/intel/media-driver/pull/1500 to upstream master fixed this for me. Can this be backported? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992753/+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 1992753] [NEW] Intel Media driver DG1 AVC encode is broken.
Public bug reported: AVC Encode is broken with intel-media-driver-non-free (possibly also free version, haven't tested). Applying https://github.com/intel/media-driver/pull/1500 to upstream master fixed this for me. Can this be backported? ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992753 Title: Intel Media driver DG1 AVC encode is broken. Status in linux package in Ubuntu: Incomplete Bug description: AVC Encode is broken with intel-media-driver-non-free (possibly also free version, haven't tested). Applying https://github.com/intel/media-driver/pull/1500 to upstream master fixed this for me. Can this be backported? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992753/+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 1992671] Re: cm4 2021 version failed to boot on 20.04
I don't understand. Does the system work initially but then stops working after an update? If so, can you post the output of 'dpkg -l' from before the update and after the update? ** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu) Status: New => Incomplete -- 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/1992671 Title: cm4 2021 version failed to boot on 20.04 Status in linux-raspi package in Ubuntu: Incomplete Status in linux-raspi source package in Focal: New Bug description: The new CM4 (2021), which has UKCA sign on the board, here is its cpuinfo : Hardware: BCM2835 Revision: b03141 Model : Raspberry Pi Compute Module 4 Rev 1.1 Once it is connected to internet, the security patch creates in /boot lrwxrwxrwx 1 root root 43 Oct 12 14:31 dtb-5.4.0-1071-raspi -> dtbs/5.4.0-1071-raspi/./bcm2711-rpi-4-b.dtb At the same time, in /boot/firmware, all .elf files and .dat files are backed up and replaced. The new files make the next boot crash. If we connect it to screen, it shows that the cm4 needs new software to boot. The fix from our side is to mount as usb disk and replace all .elf and .dat files by the latest here : https://github.com/raspberrypi/firmware/tree/master/boot and then it can boot again. On CM4 (2020) this security patch doesn't crash on boot. Revision: b03140 Model : Raspberry Pi Compute Module 4 Rev 1.0 Here is the product change note : https://pip.raspberrypi.com/categories/645 This bug seems to be introduced before, the 1070 patch cause the same boot problem already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1992671/+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 1992435] Re: sof-hda-dsp Dmic0 not initial correctly
Hello Dirk, or anyone else affected, Accepted alsa-ucm-conf into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.6.3-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: alsa-ucm-conf (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1992435 Title: sof-hda-dsp Dmic0 not initial correctly Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: New Status in alsa-ucm-conf source package in Jammy: Fix Committed Bug description: [Impact] Device use sof-hda-dsp driver will not able to initial the Dmic0 status correctly [Test Plan] 1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service" 2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state" 3. reboot system 4. Dmic should be on and volume set to 70% [Where problems could occur] Only fix for Dmic0 control and upstream already merged the code. The risk will be low [Other Info] Pull Request in upstream https://github.com/alsa-project/alsa-ucm-conf/pull/132 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1992435/+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 1979633] Re: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated"
Hi Alexandre, there's no need to file a different bug, I just tagged this one as affecting "linux (Ubuntu)" as well (the launchpad "linux" project is actually the kernel. You just need to run the command mentioned in comment #12 to provide the extra information needed. -- 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/1979633 Title: The "bare" snap is the cause of error messages "unable to read partition table" and "partition table beyond EOD, truncated" Status in linux package in Ubuntu: Incomplete Status in snapd package in Ubuntu: Invalid Bug description: Hi, here is the problem: # journalctl | grep loop4 Jun 23 09:49:45 vougeot kernel: loop4: detected capacity change from 0 to 8 Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated The loop4 device is used to mount the "bare" snap: $ df -a | grep /snap/bare/ [...] /dev/loop4 128 128 0 100% /snap/bare/5 Note that on another system, the loop device will probably have another number. The error messages can be found with the following commands: # journalctl | grep "unable to read RDB block" Jun 23 09:49:45 vougeot kernel: Dev loop4: unable to read RDB block 8 # journalctl | grep "unable to read partition table" Jun 23 09:49:45 vougeot kernel: loop4: unable to read partition table # journalctl | grep "partition table beyond EOD" Jun 23 09:49:45 vougeot kernel: loop4: partition table beyond EOD, truncated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.5+22.04 Uname: Linux 5.18.6-051806-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Jun 23 11:39:16 2022 Snap.Changes: no changes found SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979633/+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
