[Kernel-packages] [Bug 2059738] Re: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04
Confirmed ; reboot ... - Asked for elevation because of a process inhibiting shutdown - This was cancelled - I then got logged out of my session - I logged in again and got prompted for a system program crash dump elevation - This was provided but _then_ my system rebooted - Same issue, unresponsive to power button until a long-press was completed first Last entries in log from a lid-close are ... 2024-04-29T07:54:52.626549+01:00 hitomi systemd[1]: Reached target sleep.target - Sleep. 2024-04-29T07:54:52.640520+01:00 hitomi systemd[1]: Starting systemd-suspend.service - System Suspend... 2024-04-29T07:54:52.705918+01:00 hitomi kernel: PM: suspend entry (deep) 2024-04-29T07:54:52.706135+01:00 hitomi systemd-sleep[8809]: Performing sleep operation 'suspend'... -- 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/2059738 Title: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04 Status in snapd: Confirmed Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: [Overview] I have been testing installations of a number of Lubuntu and Xubuntu Noble Numbat 24.04 Daily builds since Feb 2024 on a DELL Wyse 3040 (UEFI bios), more latterly focused on Lubuntu. It would appear that since introduction of Kernel 6.8 into the daily builds, the installed system fails to carry out a successful reboot or power off when commanded from the desktop or the command line [Symptoms] When selecting either Leave-->Shutdown or Leave-->Reboot from the control panel, the process starts shutting down processes in an orderly fashion, until it gets to the part where it needs to power off hardware, where it hangs. shutdown -H now also fails in the same manner shutdown -r now also fails in the same manner With quiet bootflag disabled, the last system message on display before the hang is "Starting reboot..." or "Starting power-off..." [Workaround] The power button must be pressed for 5 secs to power down the hardware [Possibly related bugs] #1594023 Poweroff or reboot hangs. Laptop won't shutdown. 16.04 #2036987 Laptop Does Not Power Off After Installing Daily Build Of 23.10 [Unsuccessful Workarounds] Tried boot flags acpi=force acpi=nocrq reboot=pci suggested in #1594023 - No effect [Observations] I do believe that shutdown/reboot was working correctly on a live USB Lubuntu Noble Numbat Alpha build on the same hardware downloaded 22-Feb-2024. This release had an earlier kernel than 6.8. Sadly i no longer have the .iso to confirm this. All Lubuntu Noble daily builds since kernel 6.8 was introduced appear to exhibit the symptoms as above [System info] Operating System: Ubuntu Noble Numbat (development branch) Kernel: Linux 6.8.0-11-generic Architecture: x86-64 Hardware Vendor: Dell Inc. Hardware Model: Wyse 3040 Thin Client Firmware Version: 1.2.5 Firmware Date: Mon 2018-08-20 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2059738/+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 2059738] Re: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04
Seeing this on my T460s as well Suspend (on lid close) ; the machine reaches the state where the lid light and the light on the power button "throb" as they would with 22.04, but the machine will not resume from suspend in response to keyboard events, mouse events, or a brief press to the power button. Poweroff : the machine reaches a state where everything appears "off", no lights, no screen activity etc, but the machine does not restart in response to a brief press of the power button. In both cases, a long-press of the power button is required. You can tell this has "taken" when the lights on the hardwire ethernet port blink briefly on release. Then a normal brief press will restart the machine. Both of these conditions happen reliably on lid close (suspend) or poweroff (from menu or command). Going to test reboot now since this is mentioned above. -- 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/2059738 Title: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04 Status in snapd: Confirmed Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: [Overview] I have been testing installations of a number of Lubuntu and Xubuntu Noble Numbat 24.04 Daily builds since Feb 2024 on a DELL Wyse 3040 (UEFI bios), more latterly focused on Lubuntu. It would appear that since introduction of Kernel 6.8 into the daily builds, the installed system fails to carry out a successful reboot or power off when commanded from the desktop or the command line [Symptoms] When selecting either Leave-->Shutdown or Leave-->Reboot from the control panel, the process starts shutting down processes in an orderly fashion, until it gets to the part where it needs to power off hardware, where it hangs. shutdown -H now also fails in the same manner shutdown -r now also fails in the same manner With quiet bootflag disabled, the last system message on display before the hang is "Starting reboot..." or "Starting power-off..." [Workaround] The power button must be pressed for 5 secs to power down the hardware [Possibly related bugs] #1594023 Poweroff or reboot hangs. Laptop won't shutdown. 16.04 #2036987 Laptop Does Not Power Off After Installing Daily Build Of 23.10 [Unsuccessful Workarounds] Tried boot flags acpi=force acpi=nocrq reboot=pci suggested in #1594023 - No effect [Observations] I do believe that shutdown/reboot was working correctly on a live USB Lubuntu Noble Numbat Alpha build on the same hardware downloaded 22-Feb-2024. This release had an earlier kernel than 6.8. Sadly i no longer have the .iso to confirm this. All Lubuntu Noble daily builds since kernel 6.8 was introduced appear to exhibit the symptoms as above [System info] Operating System: Ubuntu Noble Numbat (development branch) Kernel: Linux 6.8.0-11-generic Architecture: x86-64 Hardware Vendor: Dell Inc. Hardware Model: Wyse 3040 Thin Client Firmware Version: 1.2.5 Firmware Date: Mon 2018-08-20 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2059738/+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 1906067] Re: Boot from ISO - exFAT support missing
*** This bug is a duplicate of bug 2038694 *** https://bugs.launchpad.net/bugs/2038694 ** Package changed: linux (Ubuntu) => casper (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906067 Title: Boot from ISO - exFAT support missing Status in casper package in Ubuntu: Confirmed Bug description: Please add support for booting the ISO image via grub2 (loopback) in initrd. For larger images and a USB sticks, FAT32 is no longer sufficient. Most popular distributions already have support for exFAT in initrd (they can find and mount ISO on this filesystem). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1906067/+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 1906067] Re: Boot from ISO - exFAT support missing
I don't know how Live ISO images are generated in Ubuntu. I thought it was the same as in Debian. -- 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/1906067 Title: Boot from ISO - exFAT support missing Status in linux package in Ubuntu: Confirmed Bug description: Please add support for booting the ISO image via grub2 (loopback) in initrd. For larger images and a USB sticks, FAT32 is no longer sufficient. Most popular distributions already have support for exFAT in initrd (they can find and mount ISO on this filesystem). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906067/+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 1906067] Re: Boot from ISO - exFAT support missing
I have already submitted a patch, waiting for approval: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060346 ** Bug watch added: Debian Bug tracker #1060346 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060346 -- 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/1906067 Title: Boot from ISO - exFAT support missing Status in linux package in Ubuntu: Confirmed Bug description: Please add support for booting the ISO image via grub2 (loopback) in initrd. For larger images and a USB sticks, FAT32 is no longer sufficient. Most popular distributions already have support for exFAT in initrd (they can find and mount ISO on this filesystem). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906067/+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 2020022] Re: [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup
Confirmed that the test kernel in Comment #14 fixes the issue.
Thanks.
** Attachment added: "dmesg-6.2.0-39_enableVMD"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020022/+attachment/572/+files/6.2.0-39_enableVMD.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/2020022
Title:
[SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD
in UEFI setup
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
In Progress
Status in linux source package in Mantic:
Fix Released
Status in linux source package in Noble:
Fix Released
Bug description:
[Impact]
When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic
leads to the system reboot. The following log is shown:
[ 166.605518] DMAR: VT-d detected Invalidation Queue Error: Reason f
[ 166.605522] DMAR: VT-d detected Invalidation Time-out Error: SID
[ 166.612445] DMAR: VT-d detected Invalidation Completion Error: SID
[ 166.612447] DMAR: QI HEAD: UNKNOWN qw0 = 0x0, qw1 = 0x0
[ 166.612449] DMAR: QI PRIOR: UNKNOWN qw0 = 0x0, qw1 = 0x0
...
Additional info:
* The issue happens on both Lenovo SE350 server and Lenovo SR850 v2 server.
Debugging info and fix commit info:
* `git bisect` indicates the offending commit is 6aab5622296b ("PCI: vmd:
Clean up domain before enumeration"). The root cause is that VMD driver tries
to clear a PCI configuration space range when resetting a VMD domain
(https://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544),
which leads to the failure.
[Fix]
* Another `git bisect` indicates the fix commit is 20f3337d350c ("x86:
don't use REP_GOOD or ERMS for small memory clearing). I confirmed that this
commit can fix the issue.
Would it be possible to include the commit 20f3337d350c in Ubuntu
22.04.2/23.10 kernel?
[Test Plan]
Reproduce Step
1.Disable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology -->
Enable/Disable Intel VMD : Disabled
2.Install OS
3.Enable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology -->
Enable/Disable Intel VMD : Enabled
4.Rebooting will reproduce this issue
[ Where problems could occur ]
* Lenovo SE350 server and Lenovo SR850 v2 server
* The regression leads to the boot failure (cannot boot info OS successfully).
[ Other Info ]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/enable_vmd_lp_2020022
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020022/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
A bit surprised that this isn't treated with more urgency. We're on an LTS ubuntu and we get broken updates, basically. Though so far I can't see it having a major impact in my case (can still use zfs and updating other packages seems to work) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020022] Re: [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup
Confirmed that the kernel (v6.5) of 23.10 does not have the issue.
** Attachment added: "[23.10] v6.5 kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020022/+attachment/5704279/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2020022
Title:
[SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD
in UEFI setup
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
In Progress
Status in linux source package in Mantic:
Fix Released
Bug description:
[Impact]
When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic
leads to the system reboot. The following log is shown:
[ 166.605518] DMAR: VT-d detected Invalidation Queue Error: Reason f
[ 166.605522] DMAR: VT-d detected Invalidation Time-out Error: SID
[ 166.612445] DMAR: VT-d detected Invalidation Completion Error: SID
[ 166.612447] DMAR: QI HEAD: UNKNOWN qw0 = 0x0, qw1 = 0x0
[ 166.612449] DMAR: QI PRIOR: UNKNOWN qw0 = 0x0, qw1 = 0x0
...
Additional info:
* The issue happens on both Lenovo SE350 server and Lenovo SR850 v2 server.
Debugging info and fix commit info:
* `git bisect` indicates the offending commit is 6aab5622296b ("PCI: vmd:
Clean up domain before enumeration"). The root cause is that VMD driver tries
to clear a PCI configuration space range when resetting a VMD domain
(https://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544),
which leads to the failure.
[Fix]
* Another `git bisect` indicates the fix commit is 20f3337d350c ("x86:
don't use REP_GOOD or ERMS for small memory clearing). I confirmed that this
commit can fix the issue.
Would it be possible to include the commit 20f3337d350c in Ubuntu
22.04.2/23.10 kernel?
[Test Plan]
Reproduce Step
1.Disable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology -->
Enable/Disable Intel VMD : Disabled
2.Install OS
3.Enable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology -->
Enable/Disable Intel VMD : Enabled
4.Rebooting will reproduce this issue
[ Where problems could occur ]
* Lenovo SE350 server and Lenovo SR850 v2 server
* The regression leads to the boot failure (cannot boot info OS
successfully).
[ Other Info ]
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/lunar/+ref/LP2020022
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020022/+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 2025192] Re: broken installation while mirror syncing new kernel packages
Started experiencing this behavior yesterday evening (Jun 29), see attached image. ** Attachment added: "kernelsyncbug.png" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2025192/+attachment/5683151/+files/kernelsyncbug.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2025192 Title: broken installation while mirror syncing new kernel packages Status in linux-meta package in Ubuntu: Confirmed Bug description: A new kernel package for jammy was released 3 hours ago. It is probably being synced to mirrors right now. It can be seen at https://launchpad.net/ubuntu/+source/linux-meta: 5.15.0.76.74 updates (main) 3 hours ago A little before that, I was deploying 10 Jammy machines in maas, without any problem. After that, I started having all 10 machines fail deployment. The reason is that curtin will fail package updates (complete log attached). This is the important part: ==8<--- Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmp_24ek5y0/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', '--option=Dpkg::options::=--force-unsafe-io', '--option=Dpkg::Options::=--force-confold', 'install', 'linux-generic'] with allowed return codes [0] (capture=False) Reading package lists... Building dependency tree... Reading state information... 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: linux-headers-generic : Depends: linux-headers-5.15.0-76-generic but it is not installable linux-image-generic : Depends: linux-image-5.15.0-76-generic but it is not going to be installed Depends: linux-modules-extra-5.15.0-76-generic but it is not installable Recommends: thermald but it is not going to be installed E: Unable to correct problems, you have held broken packages. ==8<--- The repository being used is "http://archive.ubuntu.com/ubuntu jammy/main" It may be the case that there is still a partial mirror there, but it should not break and instead just use the latest available version while the new one is not completely avalable. I'm not sure this is only valid for linux kernel packages (maybe this is a general problem with any package) but I'm opening to linux-meta since it happened with linux in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2025192/+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 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
seems to be a nouveau issue , please install nvidia official drivers from ubuntu repos and blacklist nouveau driver at boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs
I have same problem on Adler Lake Intel. After resume there is no any logs in journal. I have Nvidia P2000 GPU. Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-12700KF -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007718 Title: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs Status in linux-meta-hwe-5.19 package in Ubuntu: Confirmed Bug description: After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from 5.15.0.60) suspend/wake up is broken on my laptop. The system refuses to wake up in about 50% of the cases, seemingly random. The only "solution" is a forced system power down. Reverting back to 5.15.0.60 resolves this issue immediately. I suspect some patch was not re-applied to 5.19, since there are many postings on Reddit (for instance) about sleep problems with newer AMD CPUs, but 5.15 was running beautifully. My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU. UPDATE: See attached log. This may not be a case of the laptop failing to resume, but a case of the laptop not suspending properly! What happened was the following. When packing in my things, I closed the laptop and put it in my bag. At home I picked it up again, and immediately noticed how unusually hot it was. The laptop didn't resume properly on opening the lid, but was frozen as before. So this might actually be a case of the laptop FAILING TO SUSPEND properly, instead of failing to wake up. UPDATE: I just noticed the battery was down to the low 40% from at least 80%. Given the temperature on opening the laption I suspect the CPU has been working hard during "sleep time". EDIT: Changed title after confirmation for earlier Ryzen 5000 CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.19/+bug/2007718/+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 2007781] [NEW] Wifi occasionally doesn't work aynmore before turning it off and on again
Public bug reported: My wifi randomly gets not recognized anymore, by that I mean there is a question mark appearing on the wifi symbol, whcih means that it doesn't connect me to the internet. Only when I turn it off and on again it works again for a while. I tried to fix the problem by installing dhcpd5 and changing the network.config file, but it didn't work sadly. journalctl gives the following output: Feb 19 15:00:02 adrian-IdeaPad-3-15ADA05 dhcpcd[708]: wlp2s0: part of a Router Advertisement expired Feb 19 15:00:05 adrian-IdeaPad-3-15ADA05 rtkit-daemon[1103]: Supervising 8 threads of 5 processes of 1 users. Feb 19 15:00:05 adrian-IdeaPad-3-15ADA05 rtkit-daemon[1103]: Supervising 8 threads of 5 processes of 1 users. Feb 19 15:00:14 adrian-IdeaPad-3-15ADA05 firefox_firefox.desktop[14211]: [2023-02-19T14:00:14Z ERROR mp4parse] Found 2 nul bytes in "\0\0" Feb 19 15:00:14 adrian-IdeaPad-3-15ADA05 firefox_firefox.desktop[14211]: [2023-02-19T14:00:14Z ERROR mp4parse] Found 2 nul bytes in "\0\0" Feb 19 15:00:14 adrian-IdeaPad-3-15ADA05 firefox_firefox.desktop[14211]: [2023-02-19T14:00:14Z ERROR mp4parse] Found 2 nul bytes in "\0\0" Feb 19 15:00:14 adrian-IdeaPad-3-15ADA05 firefox_firefox.desktop[14211]: [2023-02-19T14:00:14Z ERROR mp4parse] Found 2 nul bytes in "\0\0" Feb 19 15:00:18 adrian-IdeaPad-3-15ADA05 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 19 15:00:18 adrian-IdeaPad-3-15ADA05 systemd-resolved[605]: wlp2s0: Bus client set DNS server list to: fe80::1 Feb 19 15:00:19 adrian-IdeaPad-3-15ADA05 systemd[1]: Starting Load/Save RF Kill Switch Status... Feb 19 15:00:19 adrian-IdeaPad-3-15ADA05 systemd[1]: Started Load/Save RF Kill Switch Status. Feb 19 15:00:19 adrian-IdeaPad-3-15ADA05 kernel: wlp2s0: deauthenticating from 60:8d:26:17:13:f0 by local choice (Reason: 3=DEAUTH_LEAVING) Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 kernel: ath10k_pci :02:00.0: failed to install key for vdev 0 peer 60:8d:26:17:13:f0: -110 Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 kernel: wlp2s0: failed to remove key (0, 60:8d:26:17:13:f0) from hardware (-110) Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 wpa_supplicant[744]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=60:8d:26:17:13:f0 reason=3 locally_generated=1 Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 wpa_supplicant[744]: BSSID 60:8d:26:17:13:f0 ignore list count incremented to 2, ignoring for 10 seconds Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::7c95:24aa:4e04:9716. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3395] manager: rfkill: Wi-Fi hardware radio set disabled Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 dhcpcd[708]: wlp2s0: carrier lost Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3396] device (wlp2s0): state change: activated -> unavailable (reason 'none', sys-iface-state: 'managed') Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3400] dhcp4 (wlp2s0): canceled DHCP transaction Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.2.175. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3401] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds) Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Withdrawing address record for fe80::9fcf:9cfa:e273:e098 on wlp2s0. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3401] dhcp4 (wlp2s0): state changed no lease Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Withdrawing address record for fe80::7c95:24aa:4e04:9716 on wlp2s0. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Withdrawing address record for 192.168.2.178 on wlp2s0. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 avahi-daemon[671]: Withdrawing address record for 192.168.2.175 on wlp2s0. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 wpa_supplicant[744]: rfkill: WLAN soft blocked Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 wpa_supplicant[744]: rfkill: WLAN soft blocked Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 systemd-resolved[605]: wlp2s0: Bus client set default route setting: no Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 systemd-resolved[605]: wlp2s0: Bus client reset DNS server list. Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3735] manager: NetworkManager state is now DISCONNECTED Feb 19 15:00:22 adrian-IdeaPad-3-15ADA05 NetworkManager[739]: [1676815222.3764] audit: op="radio-control" arg="wireless-enabled:off" pid=1804 uid
[Kernel-packages] [Bug 2007759] Re: Spotify freezes my entire system
** Description changed: When I open spotify and have it open for a while my system freezes and I need to hard reset afterwards. ubuntu 22.10 spotify version 1.1.84.716.gc5f8b819 + + The main error that I always get aren't included in any txt files but + here is the one error I copy paste from askubuntu: + + retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140051 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: RW: 0x1 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140051 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: RW: 0x1 + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) + Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) + + -- + ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: adrian 1576 F wireplumber - /dev/snd/controlC0: adrian 1576 F wireplumber - /dev/snd/seq:adrian 1573 F pipewire + USERPID ACCESS COMMAND + /dev/snd/controlC1: adrian 1576 F wireplumber + /dev/snd/controlC0: adrian 1576 F wireplumber + /dev/snd/seq:adrian 1573 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 18 20:11:39 2023 InstallationDate: Installed on 2023-01-27 (21 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 81W1 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=683321d2-f902-45fc-86c5-b0d4410e061a 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-31-generic N/A - linux-backports-modules-5.19.0-31-generic N/A - linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 + linux-restricted-modules-5.19.0-31-generic N/A + linux-backports-modules-5.19.0-31-generic N/A + linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2023-01-27 (21 days ago) dmi.bios.date: 04/18/2022 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ADA05 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrE8CN34WW:bd04/18/2022:br1.34:efr1.34:svnLENOVO:pn81W1:pvrIdeaPad315ADA05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315ADA05:skuLENOVO_MT_81W1_BU_idea_FM_IdeaPad315ADA05: dmi.product.family: IdeaPad 3 15ADA05 dmi.product.name: 81W1 dmi.product.sku: LENOVO_MT_81W1_BU_idea_FM_IdeaPad 3 15ADA05 dmi.produ
[Kernel-packages] [Bug 2007759] [NEW] Spotify freezes my entire system
Public bug reported: When I open spotify and have it open for a while my system freezes and I need to hard reset afterwards. ubuntu 22.10 spotify version 1.1.84.716.gc5f8b819 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1576 F wireplumber /dev/snd/controlC0: adrian 1576 F wireplumber /dev/snd/seq:adrian 1573 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 18 20:11:39 2023 InstallationDate: Installed on 2023-01-27 (21 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 81W1 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=683321d2-f902-45fc-86c5-b0d4410e061a 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-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2023-01-27 (21 days ago) dmi.bios.date: 04/18/2022 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ADA05 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrE8CN34WW:bd04/18/2022:br1.34:efr1.34:svnLENOVO:pn81W1:pvrIdeaPad315ADA05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315ADA05:skuLENOVO_MT_81W1_BU_idea_FM_IdeaPad315ADA05: dmi.product.family: IdeaPad 3 15ADA05 dmi.product.name: 81W1 dmi.product.sku: LENOVO_MT_81W1_BU_idea_FM_IdeaPad 3 15ADA05 dmi.product.version: IdeaPad 3 15ADA05 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/2007759 Title: Spotify freezes my entire system Status in linux package in Ubuntu: New Bug description: When I open spotify and have it open for a while my system freezes and I need to hard reset afterwards. ubuntu 22.10 spotify version 1.1.84.716.gc5f8b819 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1576 F wireplumber /dev/snd/controlC0: adrian 1576 F wireplumber /dev/snd/seq:adrian 1573 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 18 20:11:39 2023 InstallationDate: Installed on 2023-01-27 (21 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 81W1 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=683321d2-f902-45fc-86c5-b0d4410e061a 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-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2023-01-27 (21 days ago) dmi.bios.date: 04/18/2022 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ADA05 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrE8CN34WW:bd04/18/2022:br1.34:efr1.34:svnLENOVO:pn81W1:pvrIdeaPad315ADA05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315ADA05:skuLENOVO_MT_81W1_BU_idea_FM_IdeaPad315ADA05: dmi.product.family: IdeaPad 3 15ADA05 dmi.product.name: 81W1 dmi.product.sku: LENOVO_MT_81W1_BU_idea_FM_IdeaPad 3 15ADA05 dmi.product.version: IdeaPad 3 15ADA05 dmi.sys.vendo
[Kernel-packages] [Bug 1968104] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1968104/+attachment/5579155/+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/1968104 Title: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk Status in linux package in Ubuntu: Confirmed Bug description: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Apr 11 02:49 seq crw-rw+ 1 root audio 116, 33 Apr 11 02:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-11 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04b3:4010 IBM Corp. XClarity Controller Bus 001 Device 007: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse Bus 001 Device 002: ID 2a4b:0400 EMULEX Corporation Pilot4 Integrated Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Lenovo ThinkSystem SR650 V2 MB Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 02/16/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE117C-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z72A001WW dmi.board.vendor: Lenovo dmi.board.version: 04 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE117C-1.30:bd02/16/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR650V2MB:pvr04:rvnLenovo:rn7Z72A001WW:rvr04:cvnLenovo:ct23:cvrnone:sku7Z72A001WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR650 V2 MB dmi.product.sku: 7Z72A001WW dmi.product.version: 04 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968104/+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 1968104] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1968104/+attachment/5579159/+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/1968104 Title: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk Status in linux package in Ubuntu: Confirmed Bug description: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Apr 11 02:49 seq crw-rw+ 1 root audio 116, 33 Apr 11 02:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-11 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04b3:4010 IBM Corp. XClarity Controller Bus 001 Device 007: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse Bus 001 Device 002: ID 2a4b:0400 EMULEX Corporation Pilot4 Integrated Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Lenovo ThinkSystem SR650 V2 MB Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 02/16/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE117C-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z72A001WW dmi.board.vendor: Lenovo dmi.board.version: 04 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE117C-1.30:bd02/16/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR650V2MB:pvr04:rvnLenovo:rn7Z72A001WW:rvr04:cvnLenovo:ct23:cvrnone:sku7Z72A001WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR650 V2 MB dmi.product.sku: 7Z72A001WW dmi.product.version: 04 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968104/+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 1968104] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1968104/+attachment/5579158/+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/1968104 Title: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk Status in linux package in Ubuntu: Confirmed Bug description: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Apr 11 02:49 seq crw-rw+ 1 root audio 116, 33 Apr 11 02:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-11 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04b3:4010 IBM Corp. XClarity Controller Bus 001 Device 007: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse Bus 001 Device 002: ID 2a4b:0400 EMULEX Corporation Pilot4 Integrated Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Lenovo ThinkSystem SR650 V2 MB Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 02/16/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE117C-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z72A001WW dmi.board.vendor: Lenovo dmi.board.version: 04 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE117C-1.30:bd02/16/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR650V2MB:pvr04:rvnLenovo:rn7Z72A001WW:rvr04:cvnLenovo:ct23:cvrnone:sku7Z72A001WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR650 V2 MB dmi.product.sku: 7Z72A001WW dmi.product.version: 04 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968104/+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 1968104] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1968104/+attachment/5579153/+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/1968104 Title: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk Status in linux package in Ubuntu: Confirmed Bug description: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Apr 11 02:49 seq crw-rw+ 1 root audio 116, 33 Apr 11 02:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-11 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04b3:4010 IBM Corp. XClarity Controller Bus 001 Device 007: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse Bus 001 Device 002: ID 2a4b:0400 EMULEX Corporation Pilot4 Integrated Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Lenovo ThinkSystem SR650 V2 MB Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 02/16/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE117C-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z72A001WW dmi.board.vendor: Lenovo dmi.board.version: 04 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE117C-1.30:bd02/16/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR650V2MB:pvr04:rvnLenovo:rn7Z72A001WW:rvr04:cvnLenovo:ct23:cvrnone:sku7Z72A001WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR650 V2 MB dmi.product.sku: 7Z72A001WW dmi.product.version: 04 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968104/+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 1968104] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1968104/+attachment/5579160/+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/1968104 Title: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk Status in linux package in Ubuntu: Confirmed Bug description: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Apr 11 02:49 seq crw-rw+ 1 root audio 116, 33 Apr 11 02:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-11 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04b3:4010 IBM Corp. XClarity Controller Bus 001 Device 007: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse Bus 001 Device 002: ID 2a4b:0400 EMULEX Corporation Pilot4 Integrated Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Lenovo ThinkSystem SR650 V2 MB Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 02/16/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE117C-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z72A001WW dmi.board.vendor: Lenovo dmi.board.version: 04 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE117C-1.30:bd02/16/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR650V2MB:pvr04:rvnLenovo:rn7Z72A001WW:rvr04:cvnLenovo:ct23:cvrnone:sku7Z72A001WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR650 V2 MB dmi.product.sku: 7Z72A001WW dmi.product.version: 04 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968104/+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 1968104] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1968104/+attachment/5579156/+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/1968104 Title: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk Status in linux package in Ubuntu: Confirmed Bug description: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Apr 11 02:49 seq crw-rw+ 1 root audio 116, 33 Apr 11 02:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-11 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04b3:4010 IBM Corp. XClarity Controller Bus 001 Device 007: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse Bus 001 Device 002: ID 2a4b:0400 EMULEX Corporation Pilot4 Integrated Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Lenovo ThinkSystem SR650 V2 MB Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 02/16/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE117C-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z72A001WW dmi.board.vendor: Lenovo dmi.board.version: 04 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE117C-1.30:bd02/16/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR650V2MB:pvr04:rvnLenovo:rn7Z72A001WW:rvr04:cvnLenovo:ct23:cvrnone:sku7Z72A001WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR650 V2 MB dmi.product.sku: 7Z72A001WW dmi.product.version: 04 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968104/+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 1968104] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1968104/+attachment/5579157/+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/1968104 Title: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk Status in linux package in Ubuntu: Confirmed Bug description: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Apr 11 02:49 seq crw-rw+ 1 root audio 116, 33 Apr 11 02:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-11 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04b3:4010 IBM Corp. XClarity Controller Bus 001 Device 007: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse Bus 001 Device 002: ID 2a4b:0400 EMULEX Corporation Pilot4 Integrated Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Lenovo ThinkSystem SR650 V2 MB Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 02/16/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE117C-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z72A001WW dmi.board.vendor: Lenovo dmi.board.version: 04 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE117C-1.30:bd02/16/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR650V2MB:pvr04:rvnLenovo:rn7Z72A001WW:rvr04:cvnLenovo:ct23:cvrnone:sku7Z72A001WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR650 V2 MB dmi.product.sku: 7Z72A001WW dmi.product.version: 04 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968104/+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 1968104] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1968104/+attachment/5579154/+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/1968104 Title: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk Status in linux package in Ubuntu: Confirmed Bug description: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Apr 11 02:49 seq crw-rw+ 1 root audio 116, 33 Apr 11 02:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-11 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04b3:4010 IBM Corp. XClarity Controller Bus 001 Device 007: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse Bus 001 Device 002: ID 2a4b:0400 EMULEX Corporation Pilot4 Integrated Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Lenovo ThinkSystem SR650 V2 MB Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 02/16/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE117C-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z72A001WW dmi.board.vendor: Lenovo dmi.board.version: 04 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE117C-1.30:bd02/16/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR650V2MB:pvr04:rvnLenovo:rn7Z72A001WW:rvr04:cvnLenovo:ct23:cvrnone:sku7Z72A001WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR650 V2 MB dmi.product.sku: 7Z72A001WW dmi.product.version: 04 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968104/+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 1968104] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1968104/+attachment/5579151/+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/1968104 Title: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk Status in linux package in Ubuntu: Confirmed Bug description: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Apr 11 02:49 seq crw-rw+ 1 root audio 116, 33 Apr 11 02:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-11 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04b3:4010 IBM Corp. XClarity Controller Bus 001 Device 007: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse Bus 001 Device 002: ID 2a4b:0400 EMULEX Corporation Pilot4 Integrated Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Lenovo ThinkSystem SR650 V2 MB Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 02/16/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE117C-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z72A001WW dmi.board.vendor: Lenovo dmi.board.version: 04 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE117C-1.30:bd02/16/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR650V2MB:pvr04:rvnLenovo:rn7Z72A001WW:rvr04:cvnLenovo:ct23:cvrnone:sku7Z72A001WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR650 V2 MB dmi.product.sku: 7Z72A001WW dmi.product.version: 04 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968104/+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 1968104] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1968104/+attachment/5579149/+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/1968104 Title: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk Status in linux package in Ubuntu: Confirmed Bug description: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Apr 11 02:49 seq crw-rw+ 1 root audio 116, 33 Apr 11 02:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-11 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04b3:4010 IBM Corp. XClarity Controller Bus 001 Device 007: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse Bus 001 Device 002: ID 2a4b:0400 EMULEX Corporation Pilot4 Integrated Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Lenovo ThinkSystem SR650 V2 MB Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 02/16/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE117C-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z72A001WW dmi.board.vendor: Lenovo dmi.board.version: 04 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE117C-1.30:bd02/16/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR650V2MB:pvr04:rvnLenovo:rn7Z72A001WW:rvr04:cvnLenovo:ct23:cvrnone:sku7Z72A001WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR650 V2 MB dmi.product.sku: 7Z72A001WW dmi.product.version: 04 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968104/+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 1968104] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1968104/+attachment/5579152/+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/1968104 Title: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk Status in linux package in Ubuntu: Confirmed Bug description: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Apr 11 02:49 seq crw-rw+ 1 root audio 116, 33 Apr 11 02:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-11 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04b3:4010 IBM Corp. XClarity Controller Bus 001 Device 007: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse Bus 001 Device 002: ID 2a4b:0400 EMULEX Corporation Pilot4 Integrated Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Lenovo ThinkSystem SR650 V2 MB Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 02/16/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE117C-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z72A001WW dmi.board.vendor: Lenovo dmi.board.version: 04 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE117C-1.30:bd02/16/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR650V2MB:pvr04:rvnLenovo:rn7Z72A001WW:rvr04:cvnLenovo:ct23:cvrnone:sku7Z72A001WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR650 V2 MB dmi.product.sku: 7Z72A001WW dmi.product.version: 04 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968104/+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 1968104] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1968104/+attachment/5579150/+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/1968104 Title: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk Status in linux package in Ubuntu: Confirmed Bug description: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Apr 11 02:49 seq crw-rw+ 1 root audio 116, 33 Apr 11 02:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-11 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04b3:4010 IBM Corp. XClarity Controller Bus 001 Device 007: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse Bus 001 Device 002: ID 2a4b:0400 EMULEX Corporation Pilot4 Integrated Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Lenovo ThinkSystem SR650 V2 MB Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 02/16/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE117C-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z72A001WW dmi.board.vendor: Lenovo dmi.board.version: 04 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE117C-1.30:bd02/16/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR650V2MB:pvr04:rvnLenovo:rn7Z72A001WW:rvr04:cvnLenovo:ct23:cvrnone:sku7Z72A001WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR650 V2 MB dmi.product.sku: 7Z72A001WW dmi.product.version: 04 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968104/+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 1968104] Re: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk
apport information ** Tags added: apport-collected jammy uec-images ** Description changed: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw+ 1 root audio 116, 1 Apr 11 02:49 seq + crw-rw+ 1 root audio 116, 33 Apr 11 02:49 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu80 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-04-11 (0 days ago) + InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 04b3:4010 IBM Corp. XClarity Controller + Bus 001 Device 007: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse + Bus 001 Device 002: ID 2a4b:0400 EMULEX Corporation Pilot4 Integrated Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Lenovo ThinkSystem SR650 V2 MB + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 mgag200drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro + ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-23-generic N/A + linux-backports-modules-5.15.0-23-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu1 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: jammy uec-images + Uname: Linux 5.15.0-23-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lxd plugdev sudo + _MarkForUpload: True + dmi.bios.date: 02/16/2022 + dmi.bios.release: 1.30 + dmi.bios.vendor: Lenovo + dmi.bios.version: AFE117C-1.30 + dmi.board.asset.tag: none + dmi.board.name: 7Z72A001WW + dmi.board.vendor: Lenovo + dmi.board.version: 04 + dmi.chassis.asset.tag: none + dmi.chassis.type: 23 + dmi.chassis.vendor: Lenovo + dmi.chassis.version: none + dmi.ec.firmware.release: 1.80 + dmi.modalias: dmi:bvnLenovo:bvrAFE117C-1.30:bd02/16/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR650V2MB:pvr04:rvnLenovo:rn7Z72A001WW:rvr04:cvnLenovo:ct23:cvrnone:sku7Z72A001WW: + dmi.product.family: ThinkSystem + dmi.product.name: ThinkSystem SR650 V2 MB + dmi.product.sku: 7Z72A001WW + dmi.product.version: 04 + dmi.sys.vendor: Lenovo ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1968104/+attachment/5579148/+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/1968104 Title: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk Status in linux package in Ubuntu: Confirmed Bug description: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors.
[Kernel-packages] [Bug 1968104] [NEW] [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk
Public bug reported: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-bug linux ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/1968104/+attachment/5577765/+files/dmesg -- 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/1968104 Title: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk Status in linux package in Ubuntu: New Bug description: After installing OS in a SW RAID1 disk (this disk is created in UEFI setup - via Intel VMD/VROC), the dmesg shows the following GPT messages after the installation and booting into the OS. --- [8.715400] GPT:Primary header thinks Alt. header is not at the end of the disk. [8.716425] GPT:419430399 != 7814037167 [8.717422] GPT:Alternate GPT header not at the end of the disk. [8.718224] GPT:419430399 != 7814037167 [8.719007] GPT: Use GNU Parted to correct GPT errors. --- [Note] 1. The issue does not happen when installing OS in a SW RAID0 disk, a SW RAID5 disk or a SW RAID10 disk. 2. Kernel community had the patch submission/discussion about this issue (in 2016): https://lore.kernel.org/lkml/1476699630-127009-1-git-send-email-h...@suse.de/. However, the patch is still pending there due to this feedback: https://lore.kernel.org/lkml/20161018095637.tgdjehscttskq...@ws.net.home/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968104/+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 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
Thanks, I saw two commits are in Ubuntu-5.15.0-23.23.
--
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/1937295
Title:
[SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping
is enabled by IOMMU
Status in subiquity:
Invalid
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
In Progress
Bug description:
[Impact]
A hardware partner discovered they were unable to install Ubuntu on
some servers using VROC setups. They point to this issue involving
DMAR that is blocking discovery of the VROC RAID devices:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2565e5b69c44b4e42469afea3cc5a97e74d1ed45
`git bisect` points to this offending commit ee81ee84f873 ("PCI:
vmd: Disable MSI-X remapping when possible"), which disables VMD MSI
remapping. The IOMMU hardware blocks the compatibility format
interrupt request because Interrupt Remapping Enable Status (IRES) and
Extended Interrupt Mode Enable (EIME) are enabled. Please refer to
section "5.1.4 Interrupt-Remapping Hardware Operation" in Intel VT-d
spec.
To fix the issue, VMD driver still enables the interrupt remapping
irrespective of VMD_FEAT_CAN_BYPASS_MSI_REMAP if the IOMMU subsystem
enables the interrupt remapping.
[Fix]
2565e5b69c44 PCI: vmd: Do not disable MSI-X remapping if interrupt
remapping is enabled by IOMMU
[Test Plan]
1. Boot into VRoC controller in uEFI Setup and create a raid10 disk.
2. Install affected Ubuntu release on the RAID10.
3. The system hangs at "Partitions formatting 33%".
[Where problems could occur]
The fix itself is a very small change to drivers/pci/controller/vmd.c
and problems should not occur. The root cause was discovered by the
hardware partner's engineers, who tested and submitted it upstream
where it was accepted and landed in 5.16.
That said, I doubt this will fix 18.04.6 as it would require a respin
to get the patched kernel onto the ISO. 20.04 should pick it up in
ISO in 20.04.5, so there could still be the initial issue since those
ISOs would be lacking the patched kernel.
[Other Info]
As noted, this would need to not only land in the kernel but land in
the kernel in the ISO to resolve the issue in the installation
process. I'll bring this back as far as Focal with the expectation
that while 20.04.4 is too late, it will be present using the GA kernel
in 20.04.5 later on.
*
Original Bug Summary:
A hardware partner has been testing 18.04 subiquity images on their
servers with VROC enabled and configured in a RAID 10 setup.
In their own words:
Steps to reproduce:
1. Boot into VRoC controller in uEFI Setup and create a raid10
disk.
2. Install Ubuntu 18.04.5 on the RAID10.
3. The system hangs at "Partitions formatting 33%".
After looking at the launchpad
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/), the
fix was included in the updated kernel.
[Quotes from the launchpad]
The released kernels are:
Hirsute: 5.11.0-22-generic
Groovy: 5.8.0-59-generic
Focal: 5.4.0-77-generic
Bionic: 4.15.0-147-generic
I've asked them to also confirm this on 20.04.2, and check that
20.04.3 dailies fix the issue.
It is at least a very reasonable hypothesis that this will also break
on all current ISO installs as none of them are respun once released
to include updated SRUs in the installation media. This currently
affects 20.04.2 but that will be resolved shortly when 20.04.3
releases as the GA and HWE kernels in that image should have the SRU
that fixes this issue. However, 18.04 has no further releases, and
even the 18.04.5 daily-live and daily images on cdimages.ubuntu.com
are not built after 18.04.5 was released.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1937295/+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 1962143] Re: [Ubuntu 22.04] "TSC calibration failed" is shown in dmesg
*** This bug is a duplicate of bug 1953731 *** https://bugs.launchpad.net/bugs/1953731 Thanks, I saw two commits are in 5.15.0-17.17. ** Description changed: - When booting into RHEL9.0, the "TSC calibration failed" message is shown - in dmesg. + When booting into Ubuntu 22.04, the "TSC calibration failed" message is + shown in dmesg. [0.00] kernel: tsc: Fast TSC calibration failed The issue was fixed by upstream series c7719e793478 and b50db7095fe0. I've tested the series, and the test passed. commit c7719e79347803b8e3b6b50da8c6db410a3012b5 Author: Feng Tang Date: Wed Nov 17 10:37:50 2021 +0800 - x86/tsc: Add a timer to make sure TSC_adjust is always checked - + x86/tsc: Add a timer to make sure TSC_adjust is always checked commit b50db7095fe002fa3e16605546cba66bf1b68a3e Author: Feng Tang Date: Wed Nov 17 10:37:51 2021 +0800 - x86/tsc: Disable clocksource watchdog for TSC on qualified platorms + x86/tsc: Disable clocksource watchdog for TSC on qualified platorms Please consider to include the series 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/1962143 Title: [Ubuntu 22.04] "TSC calibration failed" is shown in dmesg Status in linux package in Ubuntu: Incomplete Bug description: When booting into Ubuntu 22.04, the "TSC calibration failed" message is shown in dmesg. [0.00] kernel: tsc: Fast TSC calibration failed The issue was fixed by upstream series c7719e793478 and b50db7095fe0. I've tested the series, and the test passed. commit c7719e79347803b8e3b6b50da8c6db410a3012b5 Author: Feng Tang Date: Wed Nov 17 10:37:50 2021 +0800 x86/tsc: Add a timer to make sure TSC_adjust is always checked commit b50db7095fe002fa3e16605546cba66bf1b68a3e Author: Feng Tang Date: Wed Nov 17 10:37:51 2021 +0800 x86/tsc: Disable clocksource watchdog for TSC on qualified platorms Please consider to include the series in 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962143/+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 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
BTW, would it be possible to include the upstream commit
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/iommu/intel?id=b00833768e170a31af09268f7ab96aecfcca9623)
in Ubuntu 22.04 kernel?
This is another VMD issue. It would be appreciated if it can be merged
in 22.04 kernel.
The commit is also in stable kernel v5.15.27.
--
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/1937295
Title:
[SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping
is enabled by IOMMU
Status in subiquity:
Invalid
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
In Progress
Bug description:
[Impact]
A hardware partner discovered they were unable to install Ubuntu on
some servers using VROC setups. They point to this issue involving
DMAR that is blocking discovery of the VROC RAID devices:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2565e5b69c44b4e42469afea3cc5a97e74d1ed45
`git bisect` points to this offending commit ee81ee84f873 ("PCI:
vmd: Disable MSI-X remapping when possible"), which disables VMD MSI
remapping. The IOMMU hardware blocks the compatibility format
interrupt request because Interrupt Remapping Enable Status (IRES) and
Extended Interrupt Mode Enable (EIME) are enabled. Please refer to
section "5.1.4 Interrupt-Remapping Hardware Operation" in Intel VT-d
spec.
To fix the issue, VMD driver still enables the interrupt remapping
irrespective of VMD_FEAT_CAN_BYPASS_MSI_REMAP if the IOMMU subsystem
enables the interrupt remapping.
[Fix]
2565e5b69c44 PCI: vmd: Do not disable MSI-X remapping if interrupt
remapping is enabled by IOMMU
[Test Plan]
1. Boot into VRoC controller in uEFI Setup and create a raid10 disk.
2. Install affected Ubuntu release on the RAID10.
3. The system hangs at "Partitions formatting 33%".
[Where problems could occur]
The fix itself is a very small change to drivers/pci/controller/vmd.c
and problems should not occur. The root cause was discovered by the
hardware partner's engineers, who tested and submitted it upstream
where it was accepted and landed in 5.16.
That said, I doubt this will fix 18.04.6 as it would require a respin
to get the patched kernel onto the ISO. 20.04 should pick it up in
ISO in 20.04.5, so there could still be the initial issue since those
ISOs would be lacking the patched kernel.
[Other Info]
As noted, this would need to not only land in the kernel but land in
the kernel in the ISO to resolve the issue in the installation
process. I'll bring this back as far as Focal with the expectation
that while 20.04.4 is too late, it will be present using the GA kernel
in 20.04.5 later on.
*
Original Bug Summary:
A hardware partner has been testing 18.04 subiquity images on their
servers with VROC enabled and configured in a RAID 10 setup.
In their own words:
Steps to reproduce:
1. Boot into VRoC controller in uEFI Setup and create a raid10
disk.
2. Install Ubuntu 18.04.5 on the RAID10.
3. The system hangs at "Partitions formatting 33%".
After looking at the launchpad
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/), the
fix was included in the updated kernel.
[Quotes from the launchpad]
The released kernels are:
Hirsute: 5.11.0-22-generic
Groovy: 5.8.0-59-generic
Focal: 5.4.0-77-generic
Bionic: 4.15.0-147-generic
I've asked them to also confirm this on 20.04.2, and check that
20.04.3 dailies fix the issue.
It is at least a very reasonable hypothesis that this will also break
on all current ISO installs as none of them are respun once released
to include updated SRUs in the installation media. This currently
affects 20.04.2 but that will be resolved shortly when 20.04.3
releases as the GA and HWE kernels in that image should have the SRU
that fixes this issue. However, 18.04 has no further releases, and
even the 18.04.5 daily-live and daily images on cdimages.ubuntu.com
are not built after 18.04.5 was released.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1937295/+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 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
Would it be possible to include the fix patch in Ubuntu 22.04? We need
Ubuntu 22.04 (Jammy) daily build because the issue can be produced
during the installation stage with VMD enabled.
--
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/1937295
Title:
[SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping
is enabled by IOMMU
Status in subiquity:
Invalid
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
In Progress
Bug description:
[Impact]
A hardware partner discovered they were unable to install Ubuntu on
some servers using VROC setups. They point to this issue involving
DMAR that is blocking discovery of the VROC RAID devices:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2565e5b69c44b4e42469afea3cc5a97e74d1ed45
`git bisect` points to this offending commit ee81ee84f873 ("PCI:
vmd: Disable MSI-X remapping when possible"), which disables VMD MSI
remapping. The IOMMU hardware blocks the compatibility format
interrupt request because Interrupt Remapping Enable Status (IRES) and
Extended Interrupt Mode Enable (EIME) are enabled. Please refer to
section "5.1.4 Interrupt-Remapping Hardware Operation" in Intel VT-d
spec.
To fix the issue, VMD driver still enables the interrupt remapping
irrespective of VMD_FEAT_CAN_BYPASS_MSI_REMAP if the IOMMU subsystem
enables the interrupt remapping.
[Fix]
2565e5b69c44 PCI: vmd: Do not disable MSI-X remapping if interrupt
remapping is enabled by IOMMU
[Test Plan]
1. Boot into VRoC controller in uEFI Setup and create a raid10 disk.
2. Install affected Ubuntu release on the RAID10.
3. The system hangs at "Partitions formatting 33%".
[Where problems could occur]
The fix itself is a very small change to drivers/pci/controller/vmd.c
and problems should not occur. The root cause was discovered by the
hardware partner's engineers, who tested and submitted it upstream
where it was accepted and landed in 5.16.
That said, I doubt this will fix 18.04.6 as it would require a respin
to get the patched kernel onto the ISO. 20.04 should pick it up in
ISO in 20.04.5, so there could still be the initial issue since those
ISOs would be lacking the patched kernel.
[Other Info]
As noted, this would need to not only land in the kernel but land in
the kernel in the ISO to resolve the issue in the installation
process. I'll bring this back as far as Focal with the expectation
that while 20.04.4 is too late, it will be present using the GA kernel
in 20.04.5 later on.
*
Original Bug Summary:
A hardware partner has been testing 18.04 subiquity images on their
servers with VROC enabled and configured in a RAID 10 setup.
In their own words:
Steps to reproduce:
1. Boot into VRoC controller in uEFI Setup and create a raid10
disk.
2. Install Ubuntu 18.04.5 on the RAID10.
3. The system hangs at "Partitions formatting 33%".
After looking at the launchpad
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/), the
fix was included in the updated kernel.
[Quotes from the launchpad]
The released kernels are:
Hirsute: 5.11.0-22-generic
Groovy: 5.8.0-59-generic
Focal: 5.4.0-77-generic
Bionic: 4.15.0-147-generic
I've asked them to also confirm this on 20.04.2, and check that
20.04.3 dailies fix the issue.
It is at least a very reasonable hypothesis that this will also break
on all current ISO installs as none of them are respun once released
to include updated SRUs in the installation media. This currently
affects 20.04.2 but that will be resolved shortly when 20.04.3
releases as the GA and HWE kernels in that image should have the SRU
that fixes this issue. However, 18.04 has no further releases, and
even the 18.04.5 daily-live and daily images on cdimages.ubuntu.com
are not built after 18.04.5 was released.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1937295/+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 1962143] [NEW] [Ubuntu 22.04] "TSC calibration failed" is shown in dmesg
Public bug reported: When booting into RHEL9.0, the "TSC calibration failed" message is shown in dmesg. [0.00] kernel: tsc: Fast TSC calibration failed The issue was fixed by upstream series c7719e793478 and b50db7095fe0. I've tested the series, and the test passed. commit c7719e79347803b8e3b6b50da8c6db410a3012b5 Author: Feng Tang Date: Wed Nov 17 10:37:50 2021 +0800 x86/tsc: Add a timer to make sure TSC_adjust is always checked commit b50db7095fe002fa3e16605546cba66bf1b68a3e Author: Feng Tang Date: Wed Nov 17 10:37:51 2021 +0800 x86/tsc: Disable clocksource watchdog for TSC on qualified platorms Please consider to include the series in 22.04. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/1962143/+attachment/5563344/+files/dmesg -- 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/1962143 Title: [Ubuntu 22.04] "TSC calibration failed" is shown in dmesg Status in linux package in Ubuntu: New Bug description: When booting into RHEL9.0, the "TSC calibration failed" message is shown in dmesg. [0.00] kernel: tsc: Fast TSC calibration failed The issue was fixed by upstream series c7719e793478 and b50db7095fe0. I've tested the series, and the test passed. commit c7719e79347803b8e3b6b50da8c6db410a3012b5 Author: Feng Tang Date: Wed Nov 17 10:37:50 2021 +0800 x86/tsc: Add a timer to make sure TSC_adjust is always checked commit b50db7095fe002fa3e16605546cba66bf1b68a3e Author: Feng Tang Date: Wed Nov 17 10:37:51 2021 +0800 x86/tsc: Disable clocksource watchdog for TSC on qualified platorms Please consider to include the series in 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962143/+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 1952217] Re: bluetoothd coredumps from double free on connection of headset
bluetoothd 5.62 (installed from source @ `applied/ubuntu/devel` ) working well. ** Attachment added: "syslog.5.62.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+attachment/5543298/+files/syslog.5.62.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1952217 Title: bluetoothd coredumps from double free on connection of headset Status in bluez package in Ubuntu: New Bug description: Problem: Since the security updates on 2021-11-23 connecting my headset causes bluetoothd to crash, which drops all the other connections. Expected: Headset connects and works as it has done previously. ❯ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ❯ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.4 Candidate: 5.53-0ubuntu3.4 Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for the LDAC codecs for this headset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+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 1952217] Re: bluetoothd coredumps from double free on connection of headset
Syslog from affected system. - First action is to select the affected headset from the Bluetooth applet The first thing that happens is the coredum. Then the service restarts ; this seems to be fast enough that the connection is still in progress, you can see the audio endpoints being registered, ? because the state is lost this does not complete and the device reports disconnection. * - Second action is activation of a Bluetooth keyboard This connects and functions correctly - Third action is selecting the affected headset again Same response. The keyboard is also disconnected but reconnects automatically. * this is not true : these endpoints are re-registered merely on restarting the bluetooth service. ** Attachment added: "syslog.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+attachment/5543295/+files/syslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1952217 Title: bluetoothd coredumps from double free on connection of headset Status in bluez package in Ubuntu: New Bug description: Problem: Since the security updates on 2021-11-23 connecting my headset causes bluetoothd to crash, which drops all the other connections. Expected: Headset connects and works as it has done previously. ❯ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ❯ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.4 Candidate: 5.53-0ubuntu3.4 Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for the LDAC codecs for this headset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+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 1952217] [NEW] bluetoothd coredumps from double free on connection of headset
Public bug reported: Problem: Since the security updates on 2021-11-23 connecting my headset causes bluetoothd to crash, which drops all the other connections. Expected: Headset connects and works as it has done previously. ❯ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 ❯ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.4 Candidate: 5.53-0ubuntu3.4 Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for the LDAC codecs for this headset. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1952217 Title: bluetoothd coredumps from double free on connection of headset Status in bluez package in Ubuntu: New Bug description: Problem: Since the security updates on 2021-11-23 connecting my headset causes bluetoothd to crash, which drops all the other connections. Expected: Headset connects and works as it has done previously. ❯ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ❯ apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3.4 Candidate: 5.53-0ubuntu3.4 Headset is a Sony WH-1000XM3. I have ppa:berglh/pulseaudio-a2dp installed for the LDAC codecs for this headset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1952217/+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 1951939] [NEW] Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels)
Public bug reported: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels). Intel wants to investigate this, and they want to see if there are missing patches that could resolve this. [steps] $ dmesg | grep "intel_pstate" [actual] > intel_pstate: CPU model not supported [expected] > intel_pstate: supported [details] lore.kernel.org reference: https://yhbt.net/lore/all/CAAYoRsUcyFsFWDE=r+amgdba6hcgxgte2jj_nhas5e4tdgi...@mail.gmail.com/ ** Affects: linux (Ubuntu) Importance: High Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951939 Title: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels) Status in linux package in Ubuntu: New Bug description: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels). Intel wants to investigate this, and they want to see if there are missing patches that could resolve this. [steps] $ dmesg | grep "intel_pstate" [actual] > intel_pstate: CPU model not supported [expected] > intel_pstate: supported [details] lore.kernel.org reference: https://yhbt.net/lore/all/CAAYoRsUcyFsFWDE=r+amgdba6hcgxgte2jj_nhas5e4tdgi...@mail.gmail.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951939/+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 1951940] [NEW] Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels)
Public bug reported: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels). Intel wants to investigate this, and they want to see if there are missing patches that could resolve this. [steps] $ dmesg | grep "intel_pstate" [actual] > intel_pstate: CPU model not supported [expected] > intel_pstate: supported [details] lore.kernel.org reference: https://yhbt.net/lore/all/CAAYoRsUcyFsFWDE=r+amgdba6hcgxgte2jj_nhas5e4tdgi...@mail.gmail.com/ ** Affects: linux (Ubuntu) Importance: High Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951940 Title: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels) Status in linux package in Ubuntu: New Bug description: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels). Intel wants to investigate this, and they want to see if there are missing patches that could resolve this. [steps] $ dmesg | grep "intel_pstate" [actual] > intel_pstate: CPU model not supported [expected] > intel_pstate: supported [details] lore.kernel.org reference: https://yhbt.net/lore/all/CAAYoRsUcyFsFWDE=r+amgdba6hcgxgte2jj_nhas5e4tdgi...@mail.gmail.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951940/+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 1951941] [NEW] Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels)
Public bug reported: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels). Intel wants to investigate this, and they want to see if there are missing patches that could resolve this. [steps] $ dmesg | grep "intel_pstate" [actual] > intel_pstate: CPU model not supported [expected] > intel_pstate: supported [details] lore.kernel.org reference: https://yhbt.net/lore/all/CAAYoRsUcyFsFWDE=r+amgdba6hcgxgte2jj_nhas5e4tdgi...@mail.gmail.com/ ** Affects: linux (Ubuntu) Importance: High Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951941 Title: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels) Status in linux package in Ubuntu: New Bug description: Icelake cpus are not showing intel_pstate support on 20.04, 20.10, 21.04, 21.10 (ga & hwe kernels). Intel wants to investigate this, and they want to see if there are missing patches that could resolve this. [steps] $ dmesg | grep "intel_pstate" [actual] > intel_pstate: CPU model not supported [expected] > intel_pstate: supported [details] lore.kernel.org reference: https://yhbt.net/lore/all/CAAYoRsUcyFsFWDE=r+amgdba6hcgxgte2jj_nhas5e4tdgi...@mail.gmail.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951941/+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 1946216] [NEW] PL2303GL chips not recognised by 21.10 beta
Public bug reported:
L2303GL usb to serial chips are not recognised by the pl2303 module in
5.13.0-16-generic #16-Ubuntu SMP Fri Sep 3 14:53:27 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux (the current 21.10 candidate kernel). These
chips are fairly common so it will cause a problem for users.
I reported this to the upstream maintainer and he confirmed it is a
known issue and fixed by commit dcf097e7d21f ("USB: serial: pl2303: fix
GL type detection"). Please backport for 21.10.
Email correspondence confirming bug pasted below.
Johan Hovold
9:33 AM (1 hour ago)
to me, linux-usb
On Tue, Oct 05, 2021 at 05:28:24PM +0100, Adrian Knagg-Baugh wrote:
> Hi,
> As requested in dmesg I'm reporting an unknown device type for the
> pl2303 driver. Here's the extract from dmesg:
>
> [ 2824.450073] usb 1-2: new full-speed USB device number 5 using xhci_hcd
> [ 2824.621910] usb 1-2: New USB device found, idVendor=067b,
> idProduct=23d3, bcdDevice= 4.05
> [ 2824.621922] usb 1-2: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [ 2824.621926] usb 1-2: Product: USB-Serial Controller
> [ 2824.621928] usb 1-2: Manufacturer: Prolific Technology Inc.
> [ 2824.621931] usb 1-2: SerialNumber: EKCRb19B616
> [ 2824.630068] pl2303 1-2:1.0: pl2303 converter detected
> [ 2824.630084] pl2303 1-2:1.0: unknown device type, please report to
> linux-...@vger.kernel.org
>
> adrian@mononoke:~$ uname -a
> Linux mononoke 5.13.0-16-generic #16-Ubuntu SMP Fri Sep 3 14:53:27 UTC
> 2021 x86_64 x86_64 x86_64 GNU/Linux
>
> The pl2303 is in a Skywatcher telescope synscan handset, the behaviour
> is a regression since it was working fine in the 5.11 kernels packaged
> with Ubuntu 21.04, it's only since updating to 5.13 (which I've had to
> do to resolve issues with the graphics card in my new laptop) that
> I've seen the problem.
>
> See below for the output of sudo lsusb -v
>
> I hope this helps.
Thanks for the report. This should already have been fixed by commit
dcf097e7d21f ("USB: serial: pl2303: fix GL type detection") which was
backported to v5.13.15 (released about a month ago).
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-16-generic 5.13.0-16.16
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: adrian 1773 F pulseaudio
/dev/snd/controlC0: adrian 1773 F pulseaudio
/dev/snd/controlC1: adrian 1773 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 6 10:55:35 2021
InstallationDate: Installed on 2021-10-02 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
MachineType: ASUSTeK COMPUTER INC. ROG Strix G513IH_G513IH
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic
root=UUID=8a2303d3-7aba-4e56-9501-3d719f7e2f1f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-16-generic N/A
linux-backports-modules-5.13.0-16-generic N/A
linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2021
dmi.bios.release: 5.16
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: G513IH.310
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G513IH
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 0.68
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513IH.310:bd07/16/2021:br5.16:efr0.68:svnASUSTeKCOMPUTERINC.:pnROGStrixG513IH_G513IH:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnG513IH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ROG Strix
dmi.product.name: ROG Strix G513IH_G513IH
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug impish wayland-session
--
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/1946216
Title:
PL2303GL chips not recognised by 21.10 beta
Status in linux package in Ubuntu:
New
Bug description:
L2303GL usb to serial chips are not recognised by the pl2303 module in
5.13.0-16-generic #16-Ubuntu SMP Fri Sep 3 14:53:27 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux (the current 21.10 candidate kernel). These
chips are fairly common so it will cause a problem for users.
I reported this to the upstream maintainer an
[Kernel-packages] [Bug 1943430] Re: Restarted computer, touchpad stopped working.
Touchpad suddenly started working after a couple of restarts, maybe it could be an issue with the CMOS battery? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943430 Title: Restarted computer, touchpad stopped working. Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Was using the computer quickly to join a zoom call like normal. Didn't install anything or modify any files. Shut off the computer only to start it up again and have the touchpad not working. Using Thinkpad T470S. Worth mentioning that the trackpoint (red button on keyboard) has not been working ever since install. Trackpad buttons (the three above the touchpad) do not work either, but they have worked once after intense googling, but do not work either right now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 13 10:46:59 2021 InstallationDate: Installed on 2021-08-28 (15 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1943430/+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 1943430] [NEW] Restarted computer, touchpad stopped working.
Public bug reported: Was using the computer quickly to join a zoom call like normal. Didn't install anything or modify any files. Shut off the computer only to start it up again and have the touchpad not working. Using Thinkpad T470S. Worth mentioning that the trackpoint (red button on keyboard) has not been working ever since install. Trackpad buttons (the three above the touchpad) do not work either, but they have worked once after intense googling, but do not work either right now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 13 10:46:59 2021 InstallationDate: Installed on 2021-08-28 (15 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Drivers" https://bugs.launchpad.net/bugs/1943430/+attachment/5524927/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943430 Title: Restarted computer, touchpad stopped working. Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Was using the computer quickly to join a zoom call like normal. Didn't install anything or modify any files. Shut off the computer only to start it up again and have the touchpad not working. Using Thinkpad T470S. Worth mentioning that the trackpoint (red button on keyboard) has not been working ever since install. Trackpad buttons (the three above the touchpad) do not work either, but they have worked once after intense googling, but do not work either right now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 13 10:46:59 2021 InstallationDate: Installed on 2021-08-28 (15 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1943430/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Until Kernel will be officially released, just use these: https://people.canonical.com/~hwang4/9710/ sudo dpkg -i linux-image- unsigned-5.11.0-33-generic_5.11.0-33.35_amd64.deb linux- modules-5.11.0-33-generic_5.11.0-33.35_amd64.deb linux-modules- extra-5.11.0-33-generic_5.11.0-33.35_amd64.deb Dell XPS 9710 works in Ubuntu 20.04/21.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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+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 1933274] Re: TGL-H skl_dram_get_dimm_info crashes with "Missing case (val == 65535)"
Hey, it says bug status is "Incomplete", but shouldn't it be moved from this status? I think that there is a very specific information in description and attachments so maybe logs are not 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/1933274 Title: TGL-H skl_dram_get_dimm_info crashes with "Missing case (val == 65535)" Status in linux package in Ubuntu: Incomplete Bug description: Tracing this back, I found the current Ubuntu 5.11 kernel has incorrect offsets for some platforms (TGL-H and ADL). I created an upstream bug at https://gitlab.freedesktop.org/drm/intel/-/issues/3662 and was directed to a commit, 5d0c938ec9cc, that ought to fix this issue. See the attached patch file for this commit applied to the current Ubuntu 5.11 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933274/+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 1923291] Re: package zfs-dkms (not installed) failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10
Apologies, I thought I'd replied to Colin's msg above. I'd rebuilt the box a couple of time by the time I read that and no longer had the make.log available as the disk had been reformated. Can confirm that moving to 21.04 and no longer had the problem -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1923291 Title: package zfs-dkms (not installed) failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 Status in zfs-linux package in Ubuntu: Incomplete Bug description: Trying to get new PC running, combination of Ryzen CPU, B550 motherboard & zfs filesystems means I need to use recent kernel, but cannot install zfs ProblemType: Package DistroRelease: Ubuntu 20.10 Package: zfs-dkms (not installed) Uname: Linux 5.11.12-051112-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 10 16:59:29 2021 ErrorMessage: installed zfs-dkms package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SourcePackage: zfs-linux Title: package zfs-dkms (not installed) failed to install/upgrade: installed zfs-dkms 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/zfs-linux/+bug/1923291/+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 1923291] [NEW] package zfs-dkms (not installed) failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10
Public bug reported: Trying to get new PC running, combination of Ryzen CPU, B550 motherboard & zfs filesystems means I need to use recent kernel, but cannot install zfs ProblemType: Package DistroRelease: Ubuntu 20.10 Package: zfs-dkms (not installed) Uname: Linux 5.11.12-051112-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 10 16:59:29 2021 ErrorMessage: installed zfs-dkms package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SourcePackage: zfs-linux Title: package zfs-dkms (not installed) failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1923291 Title: package zfs-dkms (not installed) failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 Status in zfs-linux package in Ubuntu: New Bug description: Trying to get new PC running, combination of Ryzen CPU, B550 motherboard & zfs filesystems means I need to use recent kernel, but cannot install zfs ProblemType: Package DistroRelease: Ubuntu 20.10 Package: zfs-dkms (not installed) Uname: Linux 5.11.12-051112-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 10 16:59:29 2021 ErrorMessage: installed zfs-dkms package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SourcePackage: zfs-linux Title: package zfs-dkms (not installed) failed to install/upgrade: installed zfs-dkms 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/zfs-linux/+bug/1923291/+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 1919472] Re: 5.4.0-1040-azure taints kernel with a warning (512)
Cool. Sounds great. I will update the GitHub Actions ticket to let them know. As I cannot change the kernel in GitHub Actions I can test it once the GitHub Actions has been updated. -- 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/1919472 Title: 5.4.0-1040-azure taints kernel with a warning (512) Status in linux package in Ubuntu: Confirmed Bug description: Since GitHub Actions has been updated to 5.4.0-1040-azure our CI (https://github.com/checkpoint-restore/criu/issues/1390) fails because a user space test leads to a kernel warning: [ 226.964883] writing to auto_msgmni has no effect [ 226.978221] [ cut here ] [ 226.978226] refcount_t hit zero at __nft_mt_tg_destroy+0x20/0x30 [nft_compat] in kworker/u4:4[103], uid/euid: 0/0 [ 226.978232] WARNING: CPU: 1 PID: 103 at kernel/panic.c:677 refcount_error_report+0x9b/0xab [ 226.978233] Modules linked in: nft_counter xt_mark nft_compat nf_tables raw_diag udp_diag tcp_diag inet_diag netlink_diag af_packet_diag unix_diag veth xfs dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat br_netfilter bridge stp llc xt_owner iptable_security xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter aufs overlay binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua joydev hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper hv_netvsc serio_raw pata_acpi hv_balloon hyperv_fb hyperv_keyboard cfbfillrect hid_hyperv cfbimgblt hid cfbcopyarea hv_utils sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables autofs4 [ 226.978254] CPU: 1 PID: 103 Comm: kworker/u4:4 Not tainted 5.4.0-1040-azure #42-Ubuntu [ 226.978255] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 [ 226.978260] Workqueue: netns cleanup_net [ 226.978262] RIP: 0010:refcount_error_report+0x9b/0xab [ 226.978264] Code: 00 45 8b 85 c0 08 00 00 48 8b 93 80 00 00 00 49 8d 8d b0 0a 00 00 41 56 41 89 c1 4c 89 e6 48 c7 c7 20 40 91 88 e8 10 00 00 00 <0f> 0b 58 48 8d 65 e0 5b 41 5c 41 5d 41 5e 5d c3 0f 1f 44 00 00 55 [ 226.978265] RSP: :a0768027baa0 EFLAGS: 00010286 [ 226.978266] RAX: RBX: a0768027bbd8 RCX: 0006 [ 226.978267] RDX: 0007 RSI: 0096 RDI: 88d5b8b16580 [ 226.978268] RBP: a0768027bac8 R08: 0406 R09: 0004 [ 226.978269] R10: R11: 0001 R12: 88910e83 [ 226.978270] R13: 88d5b701 R14: R15: 88d5b701 [ 226.978271] FS: () GS:88d5b8b0() knlGS: [ 226.978272] CS: 0010 DS: ES: CR0: 80050033 [ 226.978273] CR2: 7f5cc79e340c CR3: 0001930e8003 CR4: 003706e0 [ 226.978275] DR0: DR1: DR2: [ 226.978276] DR3: DR6: fffe0ff0 DR7: 0400 [ 226.978276] Call Trace: [ 226.978282] ex_handler_refcount+0x50/0x70 [ 226.978283] fixup_exception+0x4a/0x61 [ 226.978286] do_trap+0x4e/0xf0 [ 226.978288] do_error_trap+0x7c/0xb0 [ 226.978290] ? nft_target_dump+0xc1/0xcc [nft_compat] [ 226.978292] do_invalid_op+0x3c/0x50 [ 226.978293] ? nft_target_dump+0xc1/0xcc [nft_compat] [ 226.978296] invalid_op+0x28/0x30 [ 226.978298] RIP: 0010:__nft_mt_tg_destroy+0x20/0x30 [nft_compat] [ 226.978299] Code: c3 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 89 f3 f0 ff 0d bc 2e 00 00 0f 84 c0 10 00 00 0f 88 ba 10 00 00 fb f7 f4 c6 48 8b 3b e8 43 5c 0a c7 5b 5d c3 0f 1f 44 00 00 55 [ 226.978300] RSP: :a0768027bc88 EFLAGS: 00010246 [ 226.978301] RAX: RBX: 88d4e683f6d8 RCX: c07f2000 [ 226.978301] RDX: 88d4e683f6d8 RSI: 88d4e683f6d8 RDI: c07f7100 [ 226.978302] RBP: a0768027bc90 R08: ff00 R09: 88d4ec58 [ 226.978303] R10: 88d4e683f780 R11: 0001 R12: 88d4e683f6d8 [ 226.978304] R13: c07f7100 R14: dead0100 R15: 88d4e683f8a0 [ 226.978307] __nft_match_destroy.isra.0+0x5b/0x80 [nft_compat] [ 226.978309] nft_match_destroy+0x1c/0x20 [nft_compat] [ 226.978313] nf_tables_expr_destroy+0x1f/0x30 [nf_tables] [ 226.978316] nf_tables_rule_destroy+0x49/0x70 [nf_tables] [ 226.978320] nf_tables_exit_net+0x1ae/0x3e0 [nf_tables] [ 226.978323] ops_exit_list.isra.0+0x3b/0x70 [ 226.978325] cleanup_net+0x1f0/0x300 [ 226.978329] process_one_work+0x1e5/0x3a0 [ 226.978331] worker_thread+0x4d/0x3f0 [ 226.978333] kthread+0x104/0x140 [
[Kernel-packages] [Bug 1919472] Re: 5.4.0-1040-azure taints kernel with a warning (512)
** 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/1919472 Title: 5.4.0-1040-azure taints kernel with a warning (512) Status in linux package in Ubuntu: Confirmed Bug description: Since GitHub Actions has been updated to 5.4.0-1040-azure our CI (https://github.com/checkpoint-restore/criu/issues/1390) fails because a user space test leads to a kernel warning: [ 226.964883] writing to auto_msgmni has no effect [ 226.978221] [ cut here ] [ 226.978226] refcount_t hit zero at __nft_mt_tg_destroy+0x20/0x30 [nft_compat] in kworker/u4:4[103], uid/euid: 0/0 [ 226.978232] WARNING: CPU: 1 PID: 103 at kernel/panic.c:677 refcount_error_report+0x9b/0xab [ 226.978233] Modules linked in: nft_counter xt_mark nft_compat nf_tables raw_diag udp_diag tcp_diag inet_diag netlink_diag af_packet_diag unix_diag veth xfs dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat br_netfilter bridge stp llc xt_owner iptable_security xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter aufs overlay binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua joydev hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper hv_netvsc serio_raw pata_acpi hv_balloon hyperv_fb hyperv_keyboard cfbfillrect hid_hyperv cfbimgblt hid cfbcopyarea hv_utils sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables autofs4 [ 226.978254] CPU: 1 PID: 103 Comm: kworker/u4:4 Not tainted 5.4.0-1040-azure #42-Ubuntu [ 226.978255] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 [ 226.978260] Workqueue: netns cleanup_net [ 226.978262] RIP: 0010:refcount_error_report+0x9b/0xab [ 226.978264] Code: 00 45 8b 85 c0 08 00 00 48 8b 93 80 00 00 00 49 8d 8d b0 0a 00 00 41 56 41 89 c1 4c 89 e6 48 c7 c7 20 40 91 88 e8 10 00 00 00 <0f> 0b 58 48 8d 65 e0 5b 41 5c 41 5d 41 5e 5d c3 0f 1f 44 00 00 55 [ 226.978265] RSP: :a0768027baa0 EFLAGS: 00010286 [ 226.978266] RAX: RBX: a0768027bbd8 RCX: 0006 [ 226.978267] RDX: 0007 RSI: 0096 RDI: 88d5b8b16580 [ 226.978268] RBP: a0768027bac8 R08: 0406 R09: 0004 [ 226.978269] R10: R11: 0001 R12: 88910e83 [ 226.978270] R13: 88d5b701 R14: R15: 88d5b701 [ 226.978271] FS: () GS:88d5b8b0() knlGS: [ 226.978272] CS: 0010 DS: ES: CR0: 80050033 [ 226.978273] CR2: 7f5cc79e340c CR3: 0001930e8003 CR4: 003706e0 [ 226.978275] DR0: DR1: DR2: [ 226.978276] DR3: DR6: fffe0ff0 DR7: 0400 [ 226.978276] Call Trace: [ 226.978282] ex_handler_refcount+0x50/0x70 [ 226.978283] fixup_exception+0x4a/0x61 [ 226.978286] do_trap+0x4e/0xf0 [ 226.978288] do_error_trap+0x7c/0xb0 [ 226.978290] ? nft_target_dump+0xc1/0xcc [nft_compat] [ 226.978292] do_invalid_op+0x3c/0x50 [ 226.978293] ? nft_target_dump+0xc1/0xcc [nft_compat] [ 226.978296] invalid_op+0x28/0x30 [ 226.978298] RIP: 0010:__nft_mt_tg_destroy+0x20/0x30 [nft_compat] [ 226.978299] Code: c3 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 89 f3 f0 ff 0d bc 2e 00 00 0f 84 c0 10 00 00 0f 88 ba 10 00 00 fb f7 f4 c6 48 8b 3b e8 43 5c 0a c7 5b 5d c3 0f 1f 44 00 00 55 [ 226.978300] RSP: :a0768027bc88 EFLAGS: 00010246 [ 226.978301] RAX: RBX: 88d4e683f6d8 RCX: c07f2000 [ 226.978301] RDX: 88d4e683f6d8 RSI: 88d4e683f6d8 RDI: c07f7100 [ 226.978302] RBP: a0768027bc90 R08: ff00 R09: 88d4ec58 [ 226.978303] R10: 88d4e683f780 R11: 0001 R12: 88d4e683f6d8 [ 226.978304] R13: c07f7100 R14: dead0100 R15: 88d4e683f8a0 [ 226.978307] __nft_match_destroy.isra.0+0x5b/0x80 [nft_compat] [ 226.978309] nft_match_destroy+0x1c/0x20 [nft_compat] [ 226.978313] nf_tables_expr_destroy+0x1f/0x30 [nf_tables] [ 226.978316] nf_tables_rule_destroy+0x49/0x70 [nf_tables] [ 226.978320] nf_tables_exit_net+0x1ae/0x3e0 [nf_tables] [ 226.978323] ops_exit_list.isra.0+0x3b/0x70 [ 226.978325] cleanup_net+0x1f0/0x300 [ 226.978329] process_one_work+0x1e5/0x3a0 [ 226.978331] worker_thread+0x4d/0x3f0 [ 226.978333] kthread+0x104/0x140 [ 226.978334] ? process_one_work+0x3a0/0x3a0 [ 226.978336] ? kthread_park+0x90/0x90 [ 226.978337]
[Kernel-packages] [Bug 1919472] [NEW] 5.4.0-1040-azure taints kernel with a warning (512)
Public bug reported: Since GitHub Actions has been updated to 5.4.0-1040-azure our CI (https://github.com/checkpoint-restore/criu/issues/1390) fails because a user space test leads to a kernel warning: [ 226.964883] writing to auto_msgmni has no effect [ 226.978221] [ cut here ] [ 226.978226] refcount_t hit zero at __nft_mt_tg_destroy+0x20/0x30 [nft_compat] in kworker/u4:4[103], uid/euid: 0/0 [ 226.978232] WARNING: CPU: 1 PID: 103 at kernel/panic.c:677 refcount_error_report+0x9b/0xab [ 226.978233] Modules linked in: nft_counter xt_mark nft_compat nf_tables raw_diag udp_diag tcp_diag inet_diag netlink_diag af_packet_diag unix_diag veth xfs dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat br_netfilter bridge stp llc xt_owner iptable_security xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter aufs overlay binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua joydev hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper hv_netvsc serio_raw pata_acpi hv_balloon hyperv_fb hyperv_keyboard cfbfillrect hid_hyperv cfbimgblt hid cfbcopyarea hv_utils sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables autofs4 [ 226.978254] CPU: 1 PID: 103 Comm: kworker/u4:4 Not tainted 5.4.0-1040-azure #42-Ubuntu [ 226.978255] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 [ 226.978260] Workqueue: netns cleanup_net [ 226.978262] RIP: 0010:refcount_error_report+0x9b/0xab [ 226.978264] Code: 00 45 8b 85 c0 08 00 00 48 8b 93 80 00 00 00 49 8d 8d b0 0a 00 00 41 56 41 89 c1 4c 89 e6 48 c7 c7 20 40 91 88 e8 10 00 00 00 <0f> 0b 58 48 8d 65 e0 5b 41 5c 41 5d 41 5e 5d c3 0f 1f 44 00 00 55 [ 226.978265] RSP: :a0768027baa0 EFLAGS: 00010286 [ 226.978266] RAX: RBX: a0768027bbd8 RCX: 0006 [ 226.978267] RDX: 0007 RSI: 0096 RDI: 88d5b8b16580 [ 226.978268] RBP: a0768027bac8 R08: 0406 R09: 0004 [ 226.978269] R10: R11: 0001 R12: 88910e83 [ 226.978270] R13: 88d5b701 R14: R15: 88d5b701 [ 226.978271] FS: () GS:88d5b8b0() knlGS: [ 226.978272] CS: 0010 DS: ES: CR0: 80050033 [ 226.978273] CR2: 7f5cc79e340c CR3: 0001930e8003 CR4: 003706e0 [ 226.978275] DR0: DR1: DR2: [ 226.978276] DR3: DR6: fffe0ff0 DR7: 0400 [ 226.978276] Call Trace: [ 226.978282] ex_handler_refcount+0x50/0x70 [ 226.978283] fixup_exception+0x4a/0x61 [ 226.978286] do_trap+0x4e/0xf0 [ 226.978288] do_error_trap+0x7c/0xb0 [ 226.978290] ? nft_target_dump+0xc1/0xcc [nft_compat] [ 226.978292] do_invalid_op+0x3c/0x50 [ 226.978293] ? nft_target_dump+0xc1/0xcc [nft_compat] [ 226.978296] invalid_op+0x28/0x30 [ 226.978298] RIP: 0010:__nft_mt_tg_destroy+0x20/0x30 [nft_compat] [ 226.978299] Code: c3 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 89 f3 f0 ff 0d bc 2e 00 00 0f 84 c0 10 00 00 0f 88 ba 10 00 00 fb f7 f4 c6 48 8b 3b e8 43 5c 0a c7 5b 5d c3 0f 1f 44 00 00 55 [ 226.978300] RSP: :a0768027bc88 EFLAGS: 00010246 [ 226.978301] RAX: RBX: 88d4e683f6d8 RCX: c07f2000 [ 226.978301] RDX: 88d4e683f6d8 RSI: 88d4e683f6d8 RDI: c07f7100 [ 226.978302] RBP: a0768027bc90 R08: ff00 R09: 88d4ec58 [ 226.978303] R10: 88d4e683f780 R11: 0001 R12: 88d4e683f6d8 [ 226.978304] R13: c07f7100 R14: dead0100 R15: 88d4e683f8a0 [ 226.978307] __nft_match_destroy.isra.0+0x5b/0x80 [nft_compat] [ 226.978309] nft_match_destroy+0x1c/0x20 [nft_compat] [ 226.978313] nf_tables_expr_destroy+0x1f/0x30 [nf_tables] [ 226.978316] nf_tables_rule_destroy+0x49/0x70 [nf_tables] [ 226.978320] nf_tables_exit_net+0x1ae/0x3e0 [nf_tables] [ 226.978323] ops_exit_list.isra.0+0x3b/0x70 [ 226.978325] cleanup_net+0x1f0/0x300 [ 226.978329] process_one_work+0x1e5/0x3a0 [ 226.978331] worker_thread+0x4d/0x3f0 [ 226.978333] kthread+0x104/0x140 [ 226.978334] ? process_one_work+0x3a0/0x3a0 [ 226.978336] ? kthread_park+0x90/0x90 [ 226.978337] ret_from_fork+0x35/0x40 [ 226.978339] ---[ end trace e1d9a47b641e4e0a ]--- Our test checks before each test if the tainted value has changed and aborts the CI run with a failure if the kernel is tainted. So in this case the kernel is tainted and our tests are aborted. This did not happen with 5.4.0-1039-azure. So this is a regression introduce with 5.4.0-1040-azure. https://github.com/checkpoint-restore/criu/issues/1390
[Kernel-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
Been running -460 for ages, my syslog occupies 80GB of disk space and out of 526M log lines, 99.996% of them mention "Nautilus". ** Also affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+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 1878045] Re: doing dist-upgrade got error related do Broadcom
@angels After the latest update I had that issue too. Wifi bar in the settings was completely gone. When I typed: "apt purge bcmwl-kernel-source" command I got this message: E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root? I tried again with sudo prefix and it worked, so if you are still having the issue try this: sudo apt purge bcmwl-kernel-source sudo apt-get install broadcom-sta-source sudo apt-get install broadcom-sta-dkms sudo apt-get install broadcom-sta-common Hope it will work for you as well! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Fix Released Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+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 1648418] Re: Cannot mount HFS+ volume
The hfs filesystem driver is part of the kernel, not the hfsprogs package. ** Package changed: hfsprogs (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1648418 Title: Cannot mount HFS+ volume Status in linux package in Ubuntu: Incomplete Bug description: By using sudo mount -o force -t hfsplus /dev/xvdf1 timemachine/ it keeps saying that mount: unknown filesystem type 'hfsplus' However hfsprobe is already installed. If I try the fsck it works fine: sudo fsck.hfsplus -f /dev/xvdf1 ** /dev/xvdf1 ** Checking HFS Plus volume. ** Checking Extents Overflow file. ** Checking Catalog file. ** Checking Catalog hierarchy. ** Checking volume bitmap. ** Checking volume information. ** The volume untitled appears to be OK. cat /proc/filesystems nodev sysfs nodev rootfs nodev ramfs nodev bdev nodev proc nodev cpuset nodev cgroup nodev tmpfs nodev devtmpfs nodev debugfs nodev tracefs nodev securityfs nodev sockfs nodev bpf nodev pipefs nodev devpts ext3 ext2 ext4 squashfs nodev hugetlbfs vfat nodev ecryptfs fuseblk nodev fuse nodev fusectl nodev pstore nodev mqueue btrfs nodev autofs iso9660 which hfsplus is not in the list. Ubuntu version: Linux version 4.4.0-45-generic (buildd@lgw01-34) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) ) #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648418/+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 1045991] Re: GLIBC COMPILATION FAILS ON HFS+ MADE BY HFSPROGS
The hfs filesystem driver is part of the kernel, not the hfsprogs package. ** Package changed: hfsprogs (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1045991 Title: GLIBC COMPILATION FAILS ON HFS+ MADE BY HFSPROGS Status in linux package in Ubuntu: Incomplete Bug description: Using LFS 7.0 and 7.1, gcc-4.6.2, gcc-4.6.1, binutils 2.21.1a and binutils-2.22. Glibc fails to compile on HFS+ formatted by HFSProgs. An error similar to an -fPIC error, except it does not state to recompile with -fPIC. i686_GOTOFF Relocation error, on i686. I tried different versions of the entire toolchain. On i686 Install binutils install gcc install linux-headers install glibc -../glibc-2.16.0/configure \ --prefix=/tools \ --host=$LFS_TGT \ --build=$(../glibc-2.16.0/scripts/config.guess) \ --disable-profile \ --enable-add-ons\ --enable-kernel=2.6.25 \ --with-headers=/tools/include \ libc_cv_forced_unwind=yes \ libc_cv_ctors_header=yes\ libc_cv_c_cleanup=yes make -j2 make install Using the exact same procedure and commands I receive no errors on ext4. I filed a bug with the Glibc developers, and they said that it must be a bug with HFS+. PostScript I also receive a relocation error on x86_64 with the same versions and procedure. Sorry I forgot to mention- The error is with librtld.so and libc_pic.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1045991/+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 1894321] [NEW] linux-libc-dev: linux/errno.h referrs to non-existing asm/errno.h
Public bug reported: It's a duplication of #1771309 though, as I am not an author, I can't add log there. /usr/include/asm does not exist on my machine - only /usr/include/asm-generic. This seems to be a common problem: (https://stackoverflow.com/questions/14795608/asm-errno-h-no-such-file-or-directory ) The relevant packages I have installed: dpkg -l | egrep "linux-(headers|libc)" ii linux-headers-4.15.0-1154.15.0-115.116 all Header files related to Linux kernel version 4.15.0 ii linux-headers-4.15.0-115-generic4.15.0-115.116 amd64Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-5.4.0-42-generic 5.4.0-42.46~18.04.1 amd64Linux kernel headers for version 5.4.0 on 64 bit x86 SMP ii linux-headers-5.4.0-45-generic 5.4.0-45.49~18.04.2 amd64Linux kernel headers for version 5.4.0 on 64 bit x86 SMP ii linux-headers-generic 4.15.0.115.103 amd64Generic Linux kernel headers ii linux-headers-generic-hwe-18.04 5.4.0.45.49~18.04.38amd64Generic Linux kernel headers ii linux-headers-generic-hwe-18.04-edge 5.4.0.45.49~18.04.38amd64Generic Linux kernel headers ii linux-libc-dev:amd644.15.0-115.116 amd64Linux Kernel Headers for development ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-libc-dev 4.15.0-115.116 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: afiergol 9070 F pulseaudio /dev/snd/controlC0: afiergol 9070 F pulseaudio /dev/snd/pcmC0D0p: afiergol 9070 F...m pulseaudio CurrentDesktop: GNOME Date: Fri Sep 4 19:28:56 2020 Dependencies: HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c InstallationDate: Installed on 2018-04-05 (883 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: LENOVO 20L6S04200 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager i915.enable_gvt=1 kvm.ignore_msrs=1 nouveau.blacklist=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-22 (744 days ago) dmi.bios.date: 06/02/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET59W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S04200 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET59W(1.34):bd06/02/2020:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNODPK:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S04200 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1894321 Title: linux-libc-dev: linux/errno.h referrs to non-existing asm/errno.h Status in linux package in Ubuntu: New Bug description: It's a duplication of #1771309 though, as I am not an author, I can't add log there. /usr/include/asm does not exist on my machine - only /usr/include/asm-generic. This seems to be a common problem: (https://stackoverflow.com/questions/14795608/asm-errno-h-no-such-file-or-directory ) The relevant packages I have installed: dpkg -l | egrep "linux-(headers|libc)" ii linux-headers-4.15.0-115 4.15.0-115.116 all Header files related to Linux kernel version 4.15.0 ii linux-headers-4.15.0-115-generic 4.15.0-115.116 amd64Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-5.4.0-42-generic 5.4.0-42.46~18.04.1 amd64Linux kernel headers for version
[Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
I tried to re-open this bug, because we still get reports on the CRIU side that this is not fixed: https://github.com/checkpoint- restore/criu/issues/860#issuecomment-668628745 We also still see this in Travis not working. ** Changed in: linux (Ubuntu) Status: Fix Released => Confirmed ** Changed in: linux (Ubuntu Eoan) Status: Fix Released => Confirmed ** Changed in: linux (Ubuntu Focal) Status: Fix Released => Confirmed ** Bug watch added: github.com/checkpoint-restore/criu/issues #860 https://github.com/checkpoint-restore/criu/issues/860 -- 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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1492532] Re: 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
THis issue is also occurs on Ubuntu 20.04 Linux A320M-H 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) The usb blueetooth dongle doesnt work in linux 5.x, in ubuntu broke settings -- 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/1492532 Title: 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: The most cheap usb bluetooth sticks will not work with kernel 4.1.0 or 4.2.0 (Wily). There is a patch upstream which fix this issue: https://bugzilla.kernel.org/show_bug.cgi?id=103451 --- ApportVersion: 2.18-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: norbert1412 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=d44420f1-113e-442d-93ef-3c67761be6ed InstallationDate: Installed on 2015-07-26 (40 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150725) MachineType: Acer Aspire 5737Z NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=cfecd393-8411-4a45-8d87-d5c3d0ebb5c1 ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 RelatedPackageVersions: linux-restricted-modules-4.2.0-7-generic N/A linux-backports-modules-4.2.0-7-generic N/A linux-firmware 1.147 Tags: wily Uname: Linux 4.2.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/22/2009 dmi.bios.vendor: Acer dmi.bios.version: V1.10 dmi.board.name: KALA0 dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV1.10:bd06/22/2009:svnAcer:pnAspire5737Z:pvrV1.04:rvnAcer:rnKALA0:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5737Z dmi.product.version: V1.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1492532/+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 1863864] Re: Lenovo e590 laptop hangs when connect to dock station with kernel 5.3.0+
I've got a problem that I believe might be linked. I'm using a Lenvovo ThinkPad E590 with ubuntu 18.04 kernel 5.3.0-42 Problem arise when using a USB-C dock station with minimal equipment on it (power, mouse, keyboard). If I start with the USB-C dock station connected, the system freezes shortly after boot (only mouse left moving, with everything else frozen, including keyboard CAPS and NUM lock) If I allow the system to boot, and THEN connect the dock, then things seem to work fine. -- 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/1863864 Title: Lenovo e590 laptop hangs when connect to dock station with kernel 5.3.0+ Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo ThinkPad e590, which connected via USB Type-C to Lenovo Dock station. To doc station connected network cable, USB mouse, keyboard, power, and two monitors. On previous kernel versions (include 5.0.0-37) it works ok. But after update to any version on 5.3.0 I can't use it with doc station: 1) If I boot with connected Dock station then 2 external monitors are black and laptop monitor the same black 2) If I boot without connected Dock station then Laptop works ok. At the moment when I connect USB Type-C cable to laptop screen become black, and 2 external monitors show the image, but it hangs: I can move the mouse cursor but all other UI hangs, even the clock does not work, only REISUB helps. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: andrii 1548 F pulseaudio /dev/snd/controlC1: andrii 1548 F pulseaudio /dev/snd/controlC0: andrii 1548 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2019-07-26 (207 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: LENOVO 20NB000YRT Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-37-generic root=/dev/mapper/vg0-root ro cryptops=target=vg0-root,source=/dev/disk/by-uuid/737a3cbd-a798-45e6-88e3-602d767eae77,lvm=vg0 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.14 Tags: tessa Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET27W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NB000YRT dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET27W(1.10):bd01/22/2019:svnLENOVO:pn20NB000YRT:pvrThinkPadE590:rvnLENOVO:rn20NB000YRT:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E590 dmi.product.name: 20NB000YRT dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590 dmi.product.version: ThinkPad E590 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrii 1520 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2019-07-26 (209 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 06cb:00a2 Synaptics, Inc. Bus 001 Device 003: ID 5986:2113 Acer, Inc Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NB000YRT Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic root=/dev/mapper/vg0-root ro cryptops=target=vg0-root,source=/dev/disk/by-uuid/737a3cbd-a798-45e6-88e3-602d767eae77,lvm=vg0 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.173.14 Tags: tessa Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET27W (1.10 ) dmi.board.asset.tag: Not Available
[Kernel-packages] [Bug 1857257] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318314/+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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318310/+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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318316/+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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318312/+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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318309/+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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
apport information ** Tags added: apport-collected eoan uec-images ** Description changed: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux- image-5.0.0-32-generic still works and linux-image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jan 7 18:52 seq + crw-rw 1 root audio 116, 33 Jan 7 18:52 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + DistroRelease: Ubuntu 19.10 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: DigitalOcean Droplet + Package: linux (not installed) + PciMultimedia: + + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 + ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-26-generic N/A + linux-backports-modules-5.3.0-26-generic N/A + linux-firmwareN/A + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: eoan uec-images + Uname: Linux 5.3.0-26-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 12/12/2017 + dmi.bios.vendor: DigitalOcean + dmi.bios.version: 20171212 + dmi.chassis.type: 1 + dmi.chassis.vendor: Bochs + dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: + dmi.product.family: DigitalOcean_Droplet + dmi.product.name: Droplet + dmi.product.version: 20171212 + dmi.sys.vendor: DigitalOcean ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318308/+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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug
[Kernel-packages] [Bug 1857257] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318311/+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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318315/+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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1857257/+attachment/5318313/+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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
Replying to Andrew Vagin's comment: This patch references the bug you mentioned: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/commit/?h=hwe=5613773b6f576de155c39a7b7a04e45f9f6eaf46 -- 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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
Multiple projects are now disabling CRIU tests in Travis because of this bug: https://github.com/containerd/containerd/pull/3898 https://github.com/opencontainers/runc/issues/2196 https://github.com/opencontainers/runc/pull/2198 ** Bug watch added: github.com/opencontainers/runc/issues #2196 https://github.com/opencontainers/runc/issues/2196 -- 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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
** 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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1857257] [NEW] linux-image-5.0.0-35-generic breaks checkpointing of container
Public bug reported: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux- image-5.0.0-32-generic still works and linux-image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: New Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
As per comment 25, the issue seems to affect other Lenovo systems. -- 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/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 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.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+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 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
I have submitted the patch for stable kernels: https://patchwork.kernel.org/patch/11297115/ Assuming it is accepted, it will probably turn up in Ubuntu kernels eventually. -- 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/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 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.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+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 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
That is a shame. Here is a new patch that disables command queuing which should avoid the problem. The old patch is then not needed. ** Patch added: "0001-mmc-sdhci-Workaround-broken-command-queuing-on-Intel.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5312929/+files/0001-mmc-sdhci-Workaround-broken-command-queuing-on-Intel.patch -- 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/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 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.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+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 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
I need to see if the value of the SSC1 register changed. It is shown in the CQHCI REGISTER DUMP looking like "mmc0: cqhci: Task clr: 0x | SSC1: 0x00010008" -- 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/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 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.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+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 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
I would start with a working setup, presumably Ubuntu 18.04. Then get the latest stable kernel (note, it is possible -rc kernels are broken): git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux- stable.git -b linux-5.4.y Patch it, build and install. Amend /etc/defaults/grub to have: GRUB_TIMEOUT_STYLE=menu GRUB_DISABLE_SUBMENU=y GRUB_TIMEOUT=10 GRUB_CMDLINE_LINUX_DEFAULT="" To have affect need to do: sudo update-grub Then you should at least be able to choose the kernel and see some messages. -- 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/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 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.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+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 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Err, here is the patch ** Patch added: "0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5311922/+files/0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch -- 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/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 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.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+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 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Here is an updated patch without the dependency on #include If it doesn't work, please provide kernel messages. ** Patch removed: "0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5311741/+files/0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch -- 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/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 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.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+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 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Actually it should apply cleanly to any kernel from 4.17 onward (4.16 would require a little backporting) To apply the patch, in the linux git directory: git am 0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch -- 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/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 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.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+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 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Is it possible to try this patch? ** Patch added: "0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5311741/+files/0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch -- 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/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 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.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+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 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
I have some ideas that I am testing -- 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/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 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.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+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 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
No, acpidump should not show any difference running from a newer 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/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 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.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+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 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Can someone please provide an acpidump? -- 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/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 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.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+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 1818407] Re: Cant access emmc, error -84
I tried to reproduce this problem with an ASUS L403NA with an Intel N4200 processor and SanDisk DF4064 eMMC, but it worked fine. For people still experiencing this issue, here is a debug patch that will print debug information to the kernel messages to help analyze the issue. It can be applied to linux stable v5.3.y . If you try this patch, please attach the kernel messages to this bug. ** Patch added: "Debugging patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407/+attachment/5301398/+files/0001-HACK-mmc-Add-HS400-debug-prints-sdhci-IRQ-error-prin.patch -- 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/1818407 Title: Cant access emmc, error -84 Status in linux package in Ubuntu: Confirmed Bug description: Greetings! I just got my new convertible(Asus TP202NAS, brand new) and wanted to install kubuntu 18.10 onto the internal storage, only to find that it cant see it. In dmesg i only got these two error: mc0: mmc_select_hs400 failed, error -84 mc0: error -84 whilst initializing mmc card Tried to google around for a solution but i didnt found any solution to this, also tried the kubuntu IRC channel but didnt got any luck there too /EDIT Submitted from a live session. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-release-upgrader-core 1:18.10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 CrashDB: ubuntu Date: Sun Mar 3 13:59:13 2019 LiveMediaBuild: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3661 F pulseaudio CasperVersion: 1.394 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 LiveMediaBuild: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 003: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:3501 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. TP202NAS Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP202NAS.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP202NAS 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.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP202NAS.209:bd07/19/2018:svnASUSTeKCOMPUTERINC.:pnTP202NAS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP202NAS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: VivoBook Flip dmi.product.name: TP202NAS 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/1818407/+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 1839006] Re: No sound is playing from this laptop
No, I haven't installed timidity. It seems to be that the drivers for this laptop do not exist -- 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/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+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 1839006] Re: No sound is playing from this laptop
I am able to get the pulseaudio log, but not on startup (in the tmp folder) I've tried a few methods, but nothing works. -- 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/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+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 1839006] Re: No sound is playing from this laptop
Yes I see. I have followed your instructions. Tried a different way. Is this it: ** Attachment added: "pulseverbose.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+attachment/5281612/+files/pulseverbose.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+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 1839006] Re: No sound is playing from this laptop
Again, I have followed the instructions here. There is no a.txt file in the tmp folder. It seems like pulseaudio is running. ** Attachment added: "pulse_fun" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+attachment/5281539/+files/pulse_fun -- 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/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+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 1839006] Re: No sound is playing from this laptop
** Attachment added: "client_1.conf" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+attachment/5281522/+files/client_1.conf -- 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/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+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 1839006] Re: No sound is playing from this laptop
** Attachment added: "client_3.conf" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+attachment/5281524/+files/client_3.conf -- 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/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+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 1839006] Re: No sound is playing from this laptop
Adding this line to the conf file does not generate the a.txt file on startup. I tried adding the line, altering the line with the extra arguments tags and adding to the extra arguments variable ** Attachment added: "tmp_list.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+attachment/5281521/+files/tmp_list.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/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+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 1839006] Re: No sound is playing from this laptop
** Attachment added: "client_2.conf" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+attachment/5281523/+files/client_2.conf -- 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/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+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 1839006] Re: No sound is playing from this laptop
Hello Hui, I followed the steps you outlined, but my laptop still isn't playing sound. -- 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/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+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 1839006] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1839006/+attachment/5281249/+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/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+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 1839006] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1839006/+attachment/5281242/+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/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+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 1839006] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1839006/+attachment/5281241/+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/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+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 1839006] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1839006/+attachment/5281247/+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/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+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 1839006] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1839006/+attachment/5281253/+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/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+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 1839006] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1839006/+attachment/5281251/+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/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+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 1839006] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1839006/+attachment/5281250/+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/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+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 1839006] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1839006/+attachment/5281252/+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/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+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
