[Kernel-packages] [Bug 1877871] Re: [radeon] X windows hangs following upgrade from 18.04 to 20.04
This bug remains in version 5.7.0-944 -- 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/1877871 Title: [radeon] X windows hangs following upgrade from 18.04 to 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885450] [NEW] hangs on shutdown
Public bug reported: Live Ubuntu 20.04 64bit hangs on shutdown, on two different PC. The shutdown image is shown. Then I switch to text mode and there are some messages. Attached are two screenshots of the console in about 30 second interval. After that I can reboot by SysReq keys. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "ububug_sd_1.jpg" https://bugs.launchpad.net/bugs/1885450/+attachment/5387973/+files/ububug_sd_1.jpg -- 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/1885450 Title: hangs on shutdown Status in linux package in Ubuntu: New Bug description: Live Ubuntu 20.04 64bit hangs on shutdown, on two different PC. The shutdown image is shown. Then I switch to text mode and there are some messages. Attached are two screenshots of the console in about 30 second interval. After that I can reboot by SysReq keys. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885450/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885450] Re: hangs on shutdown
** Attachment added: "ububug_sd_2.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885450/+attachment/5387974/+files/ububug_sd_2.jpg ** Description changed: Live Ubuntu 20.04 64bit hangs on shutdown, on two different PC. + The shutdown image is shown. Then I switch to text and there are some + messages. + Attached are two screenshots of the console in about 30 second interval. + + After that I can reboot by SysReq keys. ** Description changed: Live Ubuntu 20.04 64bit hangs on shutdown, on two different PC. - The shutdown image is shown. Then I switch to text and there are some - messages. + The shutdown image is shown. Then I switch to text mode and there are + some messages. Attached are two screenshots of the console in about 30 second interval. After that I can reboot by SysReq keys. -- 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/1885450 Title: hangs on shutdown Status in linux package in Ubuntu: New Bug description: Live Ubuntu 20.04 64bit hangs on shutdown, on two different PC. The shutdown image is shown. Then I switch to text mode and there are some messages. Attached are two screenshots of the console in about 30 second interval. After that I can reboot by SysReq keys. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885450/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
This bug may also be affecting focal-server-cloudimg builds at:
https://cloud-images.ubuntu.com/focal/.
See: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1874147
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in grub2 package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
Hi, this issue needs attention because it renders the cloud images for
Ubuntu 20.04 potentially unusable. Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in grub2 package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774359] Re: could not find module by name='off'
Just upgraded from Ubuntu 16 to 18.04. In my case the problem arises when I unload the driver and then try to load it again. After the error dmesg states the possible cause: [ 966.030549] NVRM: API mismatch: the client has the version 390.116, but NVRM: this kernel module has the version 384.130. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1774359 Title: could not find module by name='off' Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: When I try to load the nvidia module it doesn't load. $ sudo modprobe nvidia modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() could not find module by name='off' modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown parameter (see dmesg) $ sudo prime-select query intel $ sudo prime-offload $ cat /var/log/prime-supported.log Requires offloading $ cat /var/log/prime-offload.log Sorry the nvidia kernel module is not is loaded ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-common-390 390.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 09:42:42 2018 Dependencies: InstallationDate: Installed on 2018-05-30 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1774359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873194] Re: clipit interface not working in 20.04
** Description changed: - When running clipit in focal fossa beta the interface will crash when - opening the history list via shortcut (ctr + alt + h). + When running clipit in focal fossa the interface will crash when opening + the history list via shortcut (ctr + alt + h). Starting it from cli shows this error message: (clipit:7248): Gdk-CRITICAL **: 10:42:40.873: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed Clipit version is 1.4.4+git20190202-1 from https://launchpad.net/ubuntu/focal/+package/clipit - Ubuntu version is Ubuntu Focal Fossa (development branch) from 15.4.2020 - --- + Ubuntu version is Ubuntu Focal Fossa (20.04) as of 2nd of May 2020 + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-04-29 (1447 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal third-party-packages - Uname: Linux 5.4.0-21-generic x86_64 + Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-15 (0 days ago) UserGroups: adm cdrom dip docker kismet kvm lpadmin plugdev sambashare sudo _MarkForUpload: True -- 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/1873194 Title: clipit interface not working in 20.04 Status in clipit package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When running clipit in focal fossa the interface will crash when opening the history list via shortcut (ctr + alt + h). Starting it from cli shows this error message: (clipit:7248): Gdk-CRITICAL **: 10:42:40.873: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed Clipit version is 1.4.4+git20190202-1 from https://launchpad.net/ubuntu/focal/+package/clipit Ubuntu version is Ubuntu Focal Fossa (20.04) as of 2nd of May 2020 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-04-29 (1447 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal third-party-packages Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-15 (0 days ago) UserGroups: adm cdrom dip docker kismet kvm lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clipit/+bug/1873194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
Also, this bug is not specific to just Azure. I am using libvirt and
experiencing this issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in grub2 package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
I've traced the issue back to "00_header" and "10_linux" here:
https://git.launchpad.net/ubuntu/+source/grub2/tree/debian/patches
/ubuntu-add-initrd-less-boot-fallback.patch?h=ubuntu/focal
diffstat debian/patches/ubuntu-add-initrd-less-boot-fallback.patch
Makefile.am |3 ++
configure.ac | 10 +++
grub-initrd-fallback.service | 12 +
util/grub.d/00_header.in | 27
util/grub.d/10_linux.in | 56 +--
This is still an issue. I have to manually patch the cloud images with
guestmount after downloading them in order to make them to work. Please
advise. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in grub2 package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
The git commit which introduced the issue seems to be this:
commit 6a814c759e10feafb40c3669be30aa51eb5ce39b
Author: Mathieu Trudel-Lapierre
Date: Tue Jul 16 11:31:29 2019 -0400
Import patches-unapplied version 2.04-1ubuntu1 to ubuntu/eoan-proposed
Imported using git-ubuntu import.
(at https://git.launchpad.net/ubuntu/+source/grub2/)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in grub2 package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
Hmmm, I am not using the ISO, but rather the pre-installed cloudimg, and
I am not so sure it is actually fixed. I just tried out the latest one,
and can confirm the issue still persists with it:
https://cloud-images.ubuntu.com/focal/20200430.1/focal-server-cloudimg-
amd64.img
Here is the output from booting:
[0.00] Linux version 5.4.0-28-generic (buildd@lgw01-amd64-036) (gcc
version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #32-Ubuntu SMP Wed Apr 22 17:40:10 UTC
2020 (Ubuntu 5.4.0-28.32-generic 5.4.30)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic
root=PARTUUID=be1f3b17-864d-49f8-8249-5fb0edc7e606 ro console=tty1
console=ttyS0 panic=-1
...
[0.999771] VFS: Cannot open root device
"PARTUUID=be1f3b17-864d-49f8-8249-5fb0edc7e606" or unknown-block(0,0): error -6
[1.001738] Please append a correct "root=" boot option; here are the
available partitions:
[1.003295] 0b00 1048575 sr0
[1.003295] driver: sr
[1.004578] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
[1.006119] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-28-generic
#32-Ubuntu
[1.007522] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
Ubuntu-1.8.2-1ubuntu1 04/01/2014
[1.009254] Call Trace:
[1.009790] dump_stack+0x6d/0x9a
[1.010488] panic+0x101/0x2e3
[1.011137] mount_block_root+0x23f/0x2e8
[1.011931] mount_root+0x38/0x3a
[1.012624] prepare_namespace+0x13f/0x194
[1.013443] kernel_init_freeable+0x231/0x255
[1.014319] ? rest_init+0xb0/0xb0
[1.015018] kernel_init+0xe/0x100
[1.015721] ret_from_fork+0x35/0x40
[1.016842] Kernel Offset: 0x1ac0 from 0x8100 (relocation
range: 0x8000-0xbfff)
Upon reboot, initrdfail will now be set, and therefore it will actually load
the initrd on the second reboot. But, because I am trying to configure the
machine on the first boot using cloud-init NoCloud, it needs to actually work
on the first boot. (Anyways, I think it's a moot point that first time booting
should work.)
In the above, the "panic=-1" followed by "Cannot open root device"
indicates that there is still something amiss, at least with the
cloudimg distribution. I can file a different ticket for cloudimg, if it
would be more appropriate. Please advise. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in grub2 package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel u
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
I'm actually not sure the best place to file a ticket for the cloudimg
distribution. Any recommendation appreciated.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in grub2 package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]
My partners "HP Pavillon g6" started showing this issue upgrading from 19.04 -> 19.10. Following the steps documented in 29/31 I ended up with: evdev:name:SynPS/2 Synaptics TouchPad:dmi:bvnInsyde:bvrF.22:bd11/22/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr087A11385B1620100:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:* EVDEV_ABS_00=1266:5733:47 EVDEV_ABS_01=1029:4944:85 EVDEV_ABS_35=1266:5733:47 EVDEV_ABS_36=1029:4944:85 Which fixed it. -- 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/1825499 Title: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6] Status in systemd: Fix Released Status in libinput package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Status in libinput package in Fedora: Confirmed Bug description: After installing Kubuntu 19.04, I found that vertical sensitivity is much higher than horizontal sensitivity. Installing xserver-xorg-input-synaptics improved the situation a bit and enabled KDE touchpad setting that were disabled. It's very annoying. Laptop: HP Pavilion g6. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Fri Apr 19 12:00:02 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: D4Z91EA#ABV dmi.product.version: 088512005D160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/systemd/+bug/1825499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877871] Re: [radeon] X windows hangs following upgrade from 18.04 to 20.04
I installed both of the packages in reverse order due to dependencies. On reboot, the screen behaved the same, hanging with a white background. The latest boot log is attached. Thanks for the continued effort. ** Attachment added: "vmlinuz-5.7.0-994-generic boot.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877871/+attachment/5375666/+files/vmlinuz-5.7.0-994-generic%20boot.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/1877871 Title: [radeon] X windows hangs following upgrade from 18.04 to 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881346] [NEW] linux-kvm should support nftables
Public bug reported: LXD can't use nftables on the latest linux-kvm kernels for eoan, focal, and groovy: - groovy: 5.4.0.1009.9 - focal: 5.4.0-1011.11 - eoan: 5.3.0.1017.19 LXD detects that nft tools are available, and nft tables can be listed; however, trying to create a new table or rule fails. Because of this, LXD has to fall back on xtables, which is a legacy package. ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1881346 Title: linux-kvm should support nftables Status in linux-kvm package in Ubuntu: New Bug description: LXD can't use nftables on the latest linux-kvm kernels for eoan, focal, and groovy: - groovy: 5.4.0.1009.9 - focal: 5.4.0-1011.11 - eoan: 5.3.0.1017.19 LXD detects that nft tools are available, and nft tables can be listed; however, trying to create a new table or rule fails. Because of this, LXD has to fall back on xtables, which is a legacy package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1881346/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873194] Re: clipit interface not working in 20.04
Any user looking for a solution: The program copyQ is a working alternative and also comes with focal fossa. -- 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/1873194 Title: clipit interface not working in 20.04 Status in clipit package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When running clipit in focal fossa the interface will crash when opening the history list via shortcut (ctr + alt + h). Starting it from cli shows this error message: (clipit:7248): Gdk-CRITICAL **: 10:42:40.873: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed Clipit version is 1.4.4+git20190202-1 from https://launchpad.net/ubuntu/focal/+package/clipit Ubuntu version is Ubuntu Focal Fossa (20.04) as of 2nd of May 2020 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-04-29 (1447 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal third-party-packages Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-15 (0 days ago) UserGroups: adm cdrom dip docker kismet kvm lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clipit/+bug/1873194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
Also appears in focal, generating a syslog warning about every 5 seconds, which makes using a tty console quite difficult: $ uname -r 5.4.0-33-generic $ tail /var/log/syslog Jun 4 21:48:16 alpe kernel: [ 1350.631168] usb usb4-port1: Cannot enable. Maybe the USB cable is bad? Jun 4 21:48:20 alpe kernel: [ 1355.047109] usb usb4-port1: Cannot enable. Maybe the USB cable is bad? Jun 4 21:48:25 alpe kernel: [ 1359.507044] usb usb4-port1: Cannot enable. Maybe the USB cable is bad? -- 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/1856608 Title: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Incomplete Bug description: This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81. This bug was fixed by simply reverting the offending change. Bug 1859873 tracks root causing the issue and reapplying the change w/ any necessary fixes. [Impact] USB port unusable and boot time takes ~5 minutes longer to complete. Kernel emits messages like: usb usb2-port2: Cannot enable. Maybe the USB cable is bad? [Test Case] dmesg | grep "Cannot enable" [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882213] [NEW] cp file from external HDD to NFS on Pi 3B causes ubuntu 19.10 and 20.04 kernel to hang
Public bug reported: Copying a large file using cp on my Raspberry Pi 3B (not 3B+) from an externally-powered USB hard disk (Seagate Expansion 2TB) to an NFS- mounted filesystem across Ethernet causes the kernel of releases 19.10 and 20.04 to hang/freeze. This happens every time the copy is attempted, although the exact duration from the start of the copy to the hang varies from a few seconds to a couple of minutes. The kernel does not recover even after long waits (30mins+), and a power reset (pulling the plug) is required. (Although I admit I haven't tried yet simply disconnecting the USB cable of the HDD during a hang.) Likewise, messages are erratic and I suspect are only symptoms, notably watchdog BUG soft lockup messages and RCU stall messages on different CPU cores for different processes/threads. There are no hardware messages that I've seen recorded in log files (or appearing on the console) matching the incidents. Although I have had a swapfile configured on the SD card, the hang continues to happen doing the cp after "swapoff -a". I've also tried playing with taskset affinities and snappiness to no obvious effect - the hangs still keep happening. Copying from the external HDD to the SD card is successful, as is copying from the SD card to the NFS. Raspbian 4.19.0-8 (armmp-lpae) does not have this problem; it successfully copies the file from HDD to NFS across Ethernet without stalling. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-1011-raspi 5.4.0-1011.11 ProcVersionSignature: Ubuntu 5.4.0-1011.11-raspi 5.4.34 Uname: Linux 5.4.0-1011-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Fri Jun 5 07:37:44 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-raspi UpgradeStatus: Upgraded to focal on 2020-05-21 (14 days ago) ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 focal third-party-packages uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1882213 Title: cp file from external HDD to NFS on Pi 3B causes ubuntu 19.10 and 20.04 kernel to hang Status in linux-raspi package in Ubuntu: New Bug description: Copying a large file using cp on my Raspberry Pi 3B (not 3B+) from an externally-powered USB hard disk (Seagate Expansion 2TB) to an NFS- mounted filesystem across Ethernet causes the kernel of releases 19.10 and 20.04 to hang/freeze. This happens every time the copy is attempted, although the exact duration from the start of the copy to the hang varies from a few seconds to a couple of minutes. The kernel does not recover even after long waits (30mins+), and a power reset (pulling the plug) is required. (Although I admit I haven't tried yet simply disconnecting the USB cable of the HDD during a hang.) Likewise, messages are erratic and I suspect are only symptoms, notably watchdog BUG soft lockup messages and RCU stall messages on different CPU cores for different processes/threads. There are no hardware messages that I've seen recorded in log files (or appearing on the console) matching the incidents. Although I have had a swapfile configured on the SD card, the hang continues to happen doing the cp after "swapoff -a". I've also tried playing with taskset affinities and snappiness to no obvious effect - the hangs still keep happening. Copying from the external HDD to the SD card is successful, as is copying from the SD card to the NFS. Raspbian 4.19.0-8 (armmp-lpae) does not have this problem; it successfully copies the file from HDD to NFS across Ethernet without stalling. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-1011-raspi 5.4.0-1011.11 ProcVersionSignature: Ubuntu 5.4.0-1011.11-raspi 5.4.34 Uname: Linux 5.4.0-1011-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Fri Jun 5 07:37:44 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-raspi UpgradeStatus: Upgraded to focal on 2020-05-21 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1882213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877871] Re: [radeon] X windows hangs following upgrade from 18.04 to 20.04
Is there a way I can simply not start Radeon? I do not need it. I have attempted to blacklist Radeon in a couple of ways but have not been successful in getting the laptop to boot without booting in recovery mode. -- 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/1877871 Title: [radeon] X windows hangs following upgrade from 18.04 to 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset
I think I have the same problem. In the last week, my USB headset
(Microsoft LifeChat LX-3000) is often only recognized as an output, or
only recognized as an input, by PulseAudio. When checking with
alsamixer, it seems that Alsa recognizes both input and output, but
PulseAudio doesn't...
This does seem like a race condition in PulseAudio, so those Alsa
changes don't seem like what's caused my problem. How can I confirm if
this is the same problem as reported or a different one?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in alsa-lib package in Ubuntu:
Confirmed
Status in pulseaudio package in Ubuntu:
Confirmed
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1865499/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
Thanks oded-geek, did you happen to see a commit that might be
responsible for more stability there, or was it just on a hunch that you
tried out the mainline 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/1861395
Title:
system hang: i915 Resetting rcs0 for hang on rcs0
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Eoan:
Invalid
Status in linux source package in Focal:
Incomplete
Bug description:
System hangs, unknown cause, When this happens, the mouse pointer
still moves, but I can't do anything else with the keys or clicking in
the UI. Only recover I have found is a hard power-off
Last bit of kern.log below:
Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG:
ecode 9:1:0x, hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug
anywhere in the entire gfx stack, including userspace.
Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report
on bugs.freedesktop.org against DRI -> DRM/Intel
Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then
reassign to the right component if it's not a kernel issue.
Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required
to analyze GPU hangs, so please always attach it.
Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to
/sys/class/drm/card0/error
Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting
chip for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks
suppressed
Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0
ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000]
Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00
00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be
01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80
7d 8f 00
Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 30 12:51:24 2020
InstallationDate: Installed on 2018-06-18 (591 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dpb 115653 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-06-18 (604 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc.
Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated
Camera
Bus 001 Device 0
[Kernel-packages] [Bug 1845959] Re: QAT drivers for C3XXX and C62X not included as modules
Hi, I upgraded my kernel to 5.3.0-40.32 and qat_c3xxx caused hung task on my dm_crypt devices. I had to workaround by blacklisting qat_c3xxx. I'm using Supermicro A2SDI-4C-HLN4F with Intel Atom C3558. ** Attachment added: "hung_task.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845959/+attachment/5331790/+files/hung_task.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/1845959 Title: QAT drivers for C3XXX and C62X not included as modules Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Confirmed Bug description: [Impact] The kernel included in Ubuntu is built with the following configuration for the Intel® QuickAssit drivers: CONFIG_CRYPTO_DEV_QAT=m CONFIG_CRYPTO_DEV_QAT_DH895xCC=m # CONFIG_CRYPTO_DEV_QAT_C3XXX is not set # CONFIG_CRYPTO_DEV_QAT_C62X is not set CONFIG_CRYPTO_DEV_QAT_DH895xCCVF=m # CONFIG_CRYPTO_DEV_QAT_C3XXXVF is not set # CONFIG_CRYPTO_DEV_QAT_C62XVF is not set This is a request to use the following configuration that enables C3XXX, C62X and DH895xCC: CONFIG_CRYPTO_DEV_QAT=m CONFIG_CRYPTO_DEV_QAT_DH895xCC=m CONFIG_CRYPTO_DEV_QAT_C3XXX=m CONFIG_CRYPTO_DEV_QAT_C62X=m CONFIG_CRYPTO_DEV_QAT_DH895xCCVF=m CONFIG_CRYPTO_DEV_QAT_C3XXXVF=m CONFIG_CRYPTO_DEV_QAT_C62XVF=m [Fix] Apply the attached config patch and recompile [Regression potential] Low, we are enabling some upstream drivers. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gcabiddu 1133 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-09-30 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: enp1s0no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=29678774-3470-4779-a7ac-591572bd23c8 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-2.fc30 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-2.fc30:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-3.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845959/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865836] [NEW] Touchscreen Unresponsive in Focal, but Works in Eoan
Public bug reported: After upgrading my Surface Go to Focal from Eoan, the touchscreen has stopped working. A snippet from journalctl: 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 28 paused 0 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: always reports core events 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" "/dev/input/event4" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" "server/udev" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: is tagged by udev as: Touchscreen 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device is a touch device 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device removed 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" "udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input20/event4" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended input device "ELAN9038:00 04F3:261A" (type: TOUCHSCREEN, id 11) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "AccelerationScheme" "none" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) selected scheme none/0 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) acceleration factor: 2.000 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) acceleration threshold: 4 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: is tagged by udev as: Touchscreen 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device is a touch device 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/mouse0) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) No input driver specified, ignoring this device. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been added with another device file. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/event5) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: Applying InputClass "libinput tablet catchall" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) Using input driver 'libinput' for 'ELAN9038:00 04F3:261A' 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 29 paused 0 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: always reports core events 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" "/dev/input/event5" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" "server/udev" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: is tagged by udev as: Tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device is a tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device removed 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" "udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input23/event5" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended input device "ELAN9038:00 04F3:261A" (type: TABLET, id 12) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: is tagged by udev as: Tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device is a tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/mouse1) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) No input driver specified, ignoring this device. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been added with another device file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1694 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 02:27:15 2020 InstallationDate: Installed on 2020-01-29 (33 days a
[Kernel-packages] [Bug 1866149] [NEW] CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl
Public bug reported: I'm not completely sure which package to log this against. I'm running the kvm focal minimal cloud image from 20200302. I noticed on boot that there was an error complaining that systemd-systemctl couldn't update pid_max to the value it wanted: systemd-sysctl[117]: Couldn't write '4194304' to 'kernel/pid_max': Invalid argument Digging into it a bit more, this comes from /usr/lib/sysctl.d/50-pid-max.conf: # Bump the numeric PID range to its maximum of 2^22 (from the in-kernel default # of 2^16), to make PID collisions less likely. kernel.pid_max = 4194304 However, the linux-image-kvm kernel is compiled with CONFIG_BASE_SMALL=1 and this triggers the following code in include/linux/threads.h #define PID_MAX_LIMIT (CONFIG_BASE_SMALL ? PAGE_SIZE * 8 : \ (sizeof(long) > 4 ? 4 * 1024 * 1024 : PID_MAX_DEFAULT)) which means that if CONFIG_BASE_SMALL is set we get a maximum limit of PAGE_SIZE * 8, which on x86 would be 32768. As a workaround I can override it with a file in /etc/sysctl.d/ but this shouldn't be needed. I really don't know if CONFIG_BASE_SMALL makes any sense on x86 cloud images, they really aren't small machines in the scheme of things! Cheers David ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1866149 Title: CONFIG_BASE_SMALL=1 restricts pid space, which conflicts with systemd default sysctl Status in linux-kvm package in Ubuntu: New Bug description: I'm not completely sure which package to log this against. I'm running the kvm focal minimal cloud image from 20200302. I noticed on boot that there was an error complaining that systemd-systemctl couldn't update pid_max to the value it wanted: systemd-sysctl[117]: Couldn't write '4194304' to 'kernel/pid_max': Invalid argument Digging into it a bit more, this comes from /usr/lib/sysctl.d/50-pid-max.conf: # Bump the numeric PID range to its maximum of 2^22 (from the in-kernel default # of 2^16), to make PID collisions less likely. kernel.pid_max = 4194304 However, the linux-image-kvm kernel is compiled with CONFIG_BASE_SMALL=1 and this triggers the following code in include/linux/threads.h #define PID_MAX_LIMIT (CONFIG_BASE_SMALL ? PAGE_SIZE * 8 : \ (sizeof(long) > 4 ? 4 * 1024 * 1024 : PID_MAX_DEFAULT)) which means that if CONFIG_BASE_SMALL is set we get a maximum limit of PAGE_SIZE * 8, which on x86 would be 32768. As a workaround I can override it with a file in /etc/sysctl.d/ but this shouldn't be needed. I really don't know if CONFIG_BASE_SMALL makes any sense on x86 cloud images, they really aren't small machines in the scheme of things! Cheers David To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1866149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865836] Re: Touchscreen Unresponsive in Focal, but Works in Eoan
586]: (II) No input driver specified, ignoring this device. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been added with another device file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1694 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 02:27:15 2020 InstallationDate: Installed on 2020-01-29 (33 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:096f Microsoft Corp. Surface Type Cover Bus 001 Device 002: ID 0cf3:e302 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Go ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-14-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 SourcePackage: linux-5.4 StagingDrivers: ipu3_imgu UpgradeStatus: Upgraded to focal on 2020-01-30 (33 days ago) dmi.bios.date: 12/12/2018 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 1.0.14 dmi.board.name: Surface Go dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnMicrosoftCorporation:bvr1.0.14:bd12/12/2018:svnMicrosoftCorporation:pnSurfaceGo:pvr1:rvnMicrosoftCorporation:rnSurfaceGo:rvr:cvnMicrosoftCorporation:ct9:cvrChassisVersion: dmi.product.family: Surface dmi.product.name: Surface Go dmi.product.sku: Surface_Go_1824_Consumer dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1865836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865836] Re: Touchscreen Unresponsive in Focal, but Works in Eoan
sion[1586]: (II) No input driver specified, ignoring this device. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been added with another device file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1694 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 02:27:15 2020 InstallationDate: Installed on 2020-01-29 (33 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:096f Microsoft Corp. Surface Type Cover Bus 001 Device 002: ID 0cf3:e302 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Go ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-14-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 SourcePackage: linux-5.4 StagingDrivers: ipu3_imgu UpgradeStatus: Upgraded to focal on 2020-01-30 (33 days ago) dmi.bios.date: 12/12/2018 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 1.0.14 dmi.board.name: Surface Go dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnMicrosoftCorporation:bvr1.0.14:bd12/12/2018:svnMicrosoftCorporation:pnSurfaceGo:pvr1:rvnMicrosoftCorporation:rnSurfaceGo:rvr:cvnMicrosoftCorporation:ct9:cvrChassisVersion: dmi.product.family: Surface dmi.product.name: Surface Go dmi.product.sku: Surface_Go_1824_Consumer dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1865836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866357] [NEW] Pop sound from build-in speaker during cold boot and resume from S3
Public bug reported: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. ** 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/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: New Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866357] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1866357/+attachment/5334782/+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/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Confirmed Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Wyse 5070 Thin Client Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 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.9 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866357] Re: Pop sound from build-in speaker during cold boot and resume from S3
apport information ** Tags added: apport-collected bionic ** Description changed: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) - Device is not with me at this moment, I will provide more info if - required. + Device is not with me at this moment, I will provide more info if required. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 1901 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-03-09 (0 days ago) + InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 + MachineType: Dell Inc. Wyse 5070 Thin Client + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 + 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.9 + Tags: bionic + Uname: Linux 5.3.0-40-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/08/2020 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.5.0 + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 3 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: + dmi.product.family: Wyse Thin Client 5000 Series + dmi.product.name: Wyse 5070 Thin Client + dmi.product.sku: 080C + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1866357/+attachment/5334778/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Confirmed Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki
[Kernel-packages] [Bug 1866357] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1866357/+attachment/5334779/+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/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Confirmed Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Wyse 5070 Thin Client Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 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.9 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866357] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1866357/+attachment/5334781/+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/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Confirmed Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Wyse 5070 Thin Client Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 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.9 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866357] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1866357/+attachment/5334780/+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/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Confirmed Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Wyse 5070 Thin Client Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 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.9 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866357] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1866357/+attachment/5334786/+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/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Confirmed Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Wyse 5070 Thin Client Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 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.9 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866357] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1866357/+attachment/5334787/+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/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Confirmed Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Wyse 5070 Thin Client Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 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.9 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866357] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1866357/+attachment/5334784/+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/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Confirmed Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Wyse 5070 Thin Client Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 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.9 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866357] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1866357/+attachment/5334785/+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/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Confirmed Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Wyse 5070 Thin Client Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 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.9 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866357] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1866357/+attachment/5334783/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Confirmed Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Wyse 5070 Thin Client Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 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.9 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866357] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1866357/+attachment/5334789/+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/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Confirmed Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Wyse 5070 Thin Client Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 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.9 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866357] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1866357/+attachment/5334788/+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/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Confirmed Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Wyse 5070 Thin Client Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 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.9 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866357] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1866357/+attachment/5334790/+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/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Confirmed Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Wyse 5070 Thin Client Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 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.9 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866357] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1866357/+attachment/5334791/+files/WifiSyslog.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/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Confirmed Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Wyse 5070 Thin Client Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 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.9 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866357] Re: Pop sound from build-in speaker during cold boot and resume from S3
I can still reproduce this issue with kernel mentioned in comment#17. -- 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/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Confirmed Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Wyse 5070 Thin Client Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 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.9 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866357] Re: Pop sound from build-in speaker during cold boot and resume from S3
Currently I only have info for ubuntu kernel, the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. I have done some investigation, found the commit below, could you please help to check if this is one of the many differences between good and bad kernels that I mentioned? https://lore.kernel.org/patchwork/patch/1098499/ I will see if I can find a better machine to try your steps. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866357 Title: Pop sound from build-in speaker during cold boot and resume from S3 Status in linux package in Ubuntu: Confirmed Bug description: [Description] On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot and resume from S3, internal speaker will have a noticeable short pop noise. [More detail] There are similar bugs reported indicating it's related to codec powersaving [1]. On some devices, disable powersaving can workaround it, but the same workaround does not work on this device. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663 [Experiment] With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise So I started testing kernels between 4.13 and 4.15, found the issue does not present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that started to have the pop noise. [HW info] Codec: Realtek ALC3253 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Device is not with me at this moment, I will provide more info if required. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1901 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Wyse 5070 Thin Client Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet splash vt.handoff=1 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.9 Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Wyse Thin Client 5000 Series dmi.product.name: Wyse 5070 Thin Client dmi.product.sku: 080C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866697] [NEW] Kernel 5.5.x Does Not Support BCM4360 WiFi Adapter
Public bug reported: When I upgraded an older Macbook Air (running Ubuntu 18.04.4) from kernel 4.15 to 5.5, the wifi adapter no longer worked. The system was reporting that there were no wifi adapters found. I did research, tried some of the suggested changes (mostly installing the DEB package with the Broadcom kernel source) and had no luck getting wifi to work. Installed kernel 5.3.18 and the wifi adapter is found and is working. cat /proc/version_signature returns 'no such file' lscpi -vnvn returns (for the wifi adapter): 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03) Subsystem: Apple Inc. BCM4360 802.11ac Wireless Network Adapter [106b:0117] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort+ SERR- Capabilities: [ac] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000W DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr+ NoSnoop+ MaxPayload 128 bytes, MaxReadReq 1024 bytes DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <2us, L1 <32us ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR+, OBFF Via WAKE# DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [13c v1] Device Serial Number 48-d7-00-ff-ff-00-00-01 Capabilities: [150 v1] Power Budgeting Capabilities: [160 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Capabilities: [1b0 v1] Latency Tolerance Reporting Max snoop latency: 3145728ns Max no snoop latency: 3145728ns Capabilities: [220 v1] #15 Kernel modules: bcma lsb_release returns: Description:Ubuntu 18.04.4 LTS Release:18.04 apt-cache for the driver kernel source returns: bcmwl-kernel-source: Installed: 6.30.223.271+bdcom-0ubuntu5 Candidate: 6.30.223.271+bdcom-0ubuntu5 Version table: *** 6.30.223.271+bdcom-0ubuntu5 100 100 /var/lib/dpkg/status 6.30.223.271+bdcom-0ubuntu5~18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages 6.30.223.271+bdcom-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages What I expected to happen: Wifi connection (and icon showing in status bar) What happened instead: WiFi adapter not found. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: 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/186
[Kernel-packages] [Bug 1866697] Re: Kernel 5.5.x Does Not Support BCM4360 WiFi Adapter
apport information ** Tags added: apport-collected ** Description changed: When I upgraded an older Macbook Air (running Ubuntu 18.04.4) from kernel 4.15 to 5.5, the wifi adapter no longer worked. The system was reporting that there were no wifi adapters found. I did research, tried some of the suggested changes (mostly installing the DEB package with the Broadcom kernel source) and had no luck getting wifi to work. Installed kernel 5.3.18 and the wifi adapter is found and is working. cat /proc/version_signature returns 'no such file' lscpi -vnvn returns (for the wifi adapter): 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03) Subsystem: Apple Inc. BCM4360 802.11ac Wireless Network Adapter [106b:0117] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort+ SERR- Capabilities: [ac] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000W DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr+ NoSnoop+ MaxPayload 128 bytes, MaxReadReq 1024 bytes DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <2us, L1 <32us ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR+, OBFF Via WAKE# DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [13c v1] Device Serial Number 48-d7-00-ff-ff-00-00-01 Capabilities: [150 v1] Power Budgeting Capabilities: [160 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Capabilities: [1b0 v1] Latency Tolerance Reporting Max snoop latency: 3145728ns Max no snoop latency: 3145728ns Capabilities: [220 v1] #15 Kernel modules: bcma lsb_release returns: Description: Ubuntu 18.04.4 LTS Release: 18.04 apt-cache for the driver kernel source returns: bcmwl-kernel-source: Installed: 6.30.223.271+bdcom-0ubuntu5 Candidate: 6.30.223.271+bdcom-0ubuntu5 Version table: *** 6.30.223.271+bdcom-0ubuntu5 100 100 /var/lib/dpkg/status 6.30.223.271+bdcom-0ubuntu5~18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages 6.30.223.271+bdcom-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages What I expected to happen: Wifi connection (and icon showing in status bar) What happened instead: WiFi adapter not found. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.11 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubun
[Kernel-packages] [Bug 1850443] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301812/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850443] Re: Bluetooth: hidp: Fix assumptions on the return value of hidp_send_message
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dpb3553 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2018-06-18 (500 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc.
Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20HRCTO1WW
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=fa64d67d-26bf-4c42-a12f-c45b6ea5117c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
RelatedPackageVersions:
linux-restricted-modules-5.3.0-19-generic N/A
linux-backports-modules-5.3.0-19-generic N/A
linux-firmware1.183.1
Tags: eoan
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-26 (5 days ago)
UserGroups: adm cdrom dip libvirt lpadmin lxd netdev plugdev sambashare sudo
video
_MarkForUpload: True
dmi.bios.date: 09/03/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1MET57W (1.42 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HRCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN1MET57W(1.42):bd09/03/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 5th
dmi.product.name: 20HRCTO1WW
dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th
dmi.product.version: ThinkPad X1 Carbon 5th
dmi.sys.vendor: LENOVO
** Tags added: apport-collected eoan
--
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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850443] AlsaInfo.txt
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301810/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850443] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301814/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850443] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301811/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850443] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301821/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850443] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301817/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850443] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301815/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850443] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301813/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850443] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301818/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850443] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301816/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850443] RfKill.txt
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301820/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850443] Re: Bluetooth: hidp: Fix assumptions on the return value of hidp_send_message
Attaching logs from a reproduction, occured at 10:09:50 localtime in the
journal on the computer.
** 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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850443] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301822/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850443] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1850443/+attachment/5301819/+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/1850443
Title:
Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Please apply this mainline commit to affected Ubuntu kernels:
8bb3537095f1 Bluetooth: hidp: Fix assumptions on the return value of
hidp_send_message
...
Fixes: 48d9cc9d85dd ("Bluetooth: hidp: Let hidp_send_message return number of
queued bytes")
Specifically:
Eoan requires 8bb3537095f1.
Disco does not actually require 8bb3537095f1 (since it doesn't carry 48d9)
but its a good safety measure anyway.
kernels < Disco don't need 8bb3537095f1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850443/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849803] Re: NMI watchdog: Watchdog detected hard LOCKUP on cpu
*** This bug is a duplicate of bug 1799497 *** https://bugs.launchpad.net/bugs/1799497 ** This bug has been marked a duplicate of bug 1799497 4.15 kernel hard lockup about once a week -- 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/1849803 Title: NMI watchdog: Watchdog detected hard LOCKUP on cpu Status in linux package in Ubuntu: Confirmed Bug description: My system has been intermittently freezing (from once every couple of days up to several times a day; absolutely everything appears to be frozen, only the magic sysrq key works) for the past couple of weeks. Nothing in particular has changed recently other than updating packages. I've finally been able to get linux-crashdump set up so I at least have an error message to work with. I've attached the dmesg log it collected. I also have the kdump file it collected, which I'm hesistant to upload as I imagine it likely contains sensitive information (and it's also quite large), but let me know if there's any analysis it would be helpful for me to perform with it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-66-generic 4.15.0-66.75 ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 3067 F pulseaudio /dev/snd/pcmC0D0p: david 3067 F...m pulseaudio /dev/snd/controlC0: david 3067 F pulseaudio CurrentDesktop: KDE Date: Fri Oct 25 19:22:59 2019 InstallationDate: Installed on 2018-09-16 (404 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: docker0 no wireless extensions. lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic root=UUID=42ee6282-7d26-455d-a36f-66ba166e1ec8 ro quiet splash crashkernel=512M-:192M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-66-generic N/A linux-backports-modules-4.15.0-66-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-M dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0906:bd03/26/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-M:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799497] Re: 4.15 kernel hard lockup about once a week
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Bionic) 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/1799497 Title: 4.15 kernel hard lockup about once a week Status in linux package in Ubuntu: Confirmed Status in zram-config package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in zram-config source package in Bionic: Confirmed Bug description: My main server has been running into hard lockups about once a week ever since I switched to the 4.15 Ubuntu 18.04 kernel. When this happens, nothing is printed to the console, it's effectively stuck showing a login prompt. The system is running with panic=1 on the cmdline but isn't rebooting so the kernel isn't even processing this as a kernel panic. As this felt like a potential hardware issue, I had my hosting provider give me a completely different system, different motherboard, different CPU, different RAM and different storage, I installed that system on 18.04 and moved my data over, a week later, I hit the issue again. We've since also had a LXD user reporting similar symptoms here also on varying hardware: https://github.com/lxc/lxd/issues/5197 My system doesn't have a lot of memory pressure with about 50% of free memory: root@vorash:~# free -m totalusedfree shared buff/cache available Mem: 31819 17574 402 513 13842 13292 Swap: 159092687 13222 I will now try to increase console logging as much as possible on the system in the hopes that next time it hangs we can get a better idea of what happened but I'm not too hopeful given the complete silence on the console when this occurs. System is currently on: Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux But I've seen this since the GA kernel on 4.15 so it's not a recent regression. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 23 16:12 seq crw-rw 1 root audio 116, 33 Oct 23 16:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 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: Cannot stat file /proc/22822/fd/10: Permission denied Cannot stat file /proc/22831/fd/10: Permission denied DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none CRYPTSETUP=n IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S1200SP NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=575c878a-0be6-4806-9c83-28f67aedea65 ro biosdevname=0 net.ifnames=0 panic=1 verbose console=tty0 console=ttyS0,115200n8 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/25/2018 dmi.bios.vendor: Intel Corporation dmi.bios.version: S1200SP.86B.03.01.1029.012520180838 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S1200SP dmi.board.vendor: Intel Corporation dmi.board.version: H57532-271 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrS1200SP.86B.03.01.1029.012520180838:bd01/25/2018:svnIntelCorporation:pnS1200SP:pvr:rvnIntelCorporation:rnS1200SP:rvrH57532-271:cvn...:ct23:cvr..: dmi.product.family: Family dmi.product.name: S1200SP dmi.product.version:
[Kernel-packages] [Bug 1851230] [NEW] missing firmware files from oem image
Public bug reported: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "required_files.zip" https://bugs.launchpad.net/bugs/1851230/+attachment/5302711/+files/required_files.zip -- 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/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: New Bug description: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851230] Re: missing firmware files from oem image
apport information ** Tags added: apport-collected bionic ** Description changed: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: z 2949 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-07-25 (101 days ago) + InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 + MachineType: LENOVO 20QESITE03 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-1015-oem-osp1 N/A + linux-backports-modules-5.0.0-1015-oem-osp1 N/A + linux-firmware 1.173.10 + Tags: bionic + Uname: Linux 5.0.0-1015-oem-osp1 x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/29/2019 + dmi.bios.vendor: LENOVO + dmi.bios.version: N2HET33W (1.16 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20QESITE03 + dmi.board.vendor: LENOVO + dmi.board.version: Not Defined + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrN2HET33W(1.16):bd07/29/2019:svnLENOVO:pn20QESITE03:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE03:rvrNotDefined:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad X1 Carbon 7th + dmi.product.name: 20QESITE03 + dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th + dmi.product.version: ThinkPad X1 Carbon 7th + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1851230/+attachment/5302720/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: Confirmed Bug description: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 2949 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (101 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE03 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignatu
[Kernel-packages] [Bug 1851230] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1851230/+attachment/5302729/+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/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: Confirmed Bug description: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 2949 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (101 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE03 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET33W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE03 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET33W(1.16):bd07/29/2019:svnLENOVO:pn20QESITE03:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE03:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE03 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851230] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1851230/+attachment/5302731/+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/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: Confirmed Bug description: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 2949 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (101 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE03 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET33W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE03 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET33W(1.16):bd07/29/2019:svnLENOVO:pn20QESITE03:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE03:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE03 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851230] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1851230/+attachment/5302730/+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/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: Confirmed Bug description: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 2949 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (101 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE03 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET33W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE03 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET33W(1.16):bd07/29/2019:svnLENOVO:pn20QESITE03:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE03:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE03 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851230] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1851230/+attachment/5302726/+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/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: Confirmed Bug description: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 2949 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (101 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE03 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET33W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE03 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET33W(1.16):bd07/29/2019:svnLENOVO:pn20QESITE03:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE03:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE03 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851230] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1851230/+attachment/5302727/+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/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: Confirmed Bug description: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 2949 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (101 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE03 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET33W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE03 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET33W(1.16):bd07/29/2019:svnLENOVO:pn20QESITE03:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE03:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE03 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851230] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1851230/+attachment/5302725/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: Confirmed Bug description: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 2949 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (101 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE03 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET33W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE03 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET33W(1.16):bd07/29/2019:svnLENOVO:pn20QESITE03:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE03:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE03 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851230] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1851230/+attachment/5302723/+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/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: Confirmed Bug description: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 2949 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (101 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE03 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET33W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE03 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET33W(1.16):bd07/29/2019:svnLENOVO:pn20QESITE03:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE03:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE03 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851230] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1851230/+attachment/5302733/+files/WifiSyslog.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/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: Confirmed Bug description: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 2949 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (101 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE03 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET33W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE03 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET33W(1.16):bd07/29/2019:svnLENOVO:pn20QESITE03:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE03:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE03 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851230] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1851230/+attachment/5302728/+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/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: Confirmed Bug description: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 2949 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (101 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE03 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET33W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE03 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET33W(1.16):bd07/29/2019:svnLENOVO:pn20QESITE03:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE03:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE03 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851230] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1851230/+attachment/5302732/+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/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: Confirmed Bug description: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 2949 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (101 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE03 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET33W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE03 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET33W(1.16):bd07/29/2019:svnLENOVO:pn20QESITE03:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE03:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE03 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851230] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1851230/+attachment/5302724/+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/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: Confirmed Bug description: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 2949 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (101 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE03 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET33W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE03 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET33W(1.16):bd07/29/2019:svnLENOVO:pn20QESITE03:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE03:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE03 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851230] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1851230/+attachment/5302721/+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/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: Confirmed Bug description: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 2949 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (101 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE03 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET33W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE03 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET33W(1.16):bd07/29/2019:svnLENOVO:pn20QESITE03:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE03:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE03 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851230] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1851230/+attachment/5302722/+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/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: Confirmed Bug description: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 2949 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (101 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE03 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET33W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE03 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET33W(1.16):bd07/29/2019:svnLENOVO:pn20QESITE03:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE03:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE03 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851749] Re: Frequently getting thermal warnings and cpu throttling messages in syslog
Glad to see this filed, I have the same issue. Note there is a good discussion of the issue here: https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/ And the User made a github repo to address the problem in testing: https://github.com/erpalma/throttled I can clearly see the effect of the change using s-tui and monitoring cpu freq. Before the change, the throttle will limit me to around 1.5-1.7 GHZ under load, after the change, it's at 2.7GHZ consistent without the constant throttle messages in syslog/journalctl. I don't have enough depth in this area to understand the technical tradeoffs, but I did want to point out the research that I have used thus far. -- 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/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog Status in linux package in Ubuntu: In Progress Bug description: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above
[Kernel-packages] [Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140
** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 Status in HWE Next: Confirmed Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: New Bug description: [Impact] With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT is set to Y, then it will make the legacy intel soc driver fail, and moreover the current sof driver can't support broadwell well, as a result, many broadwell computers with I2S codec can't support sound anymore. [Fix] Intel submitted a patch, it will make those two kconfig options exclusive, and the legacy soc's option has higher priority, if both of them are enabled, sof's option will be disabled. [Test Case] Build the kernel and check the debian/build/$buidling_dir/.config, the SND_SOC_SOF_BROADWELL_SUPPORT is disabled. [Regression Risk] Low, so far, the sof driver can't support broadwell machine well, so there is no machine use this driver yet. Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.907475] broadwell-audio bro
[Kernel-packages] [Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140
There are two upstream commits that make the SOF and SST drivers mutually exclusive on a specific platform. The one for Broadwell is now merged into the Ubuntu kernel: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/eoan/commit/?id=d46917958a6366f3c63501e9962b60dd7d33a3bd But the matching one for Baytrail is missing. It should be merged as well: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=df7257e544faf838c3e7ad6b4e89ffe59e87f5e1 Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 Status in HWE Next: Confirmed Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: New Bug description: [Impact] With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT is set to Y, then it will make the legacy intel soc driver fail, and moreover the current sof driver can't support broadwell well, as a result, many broadwell computers with I2S codec can't support sound anymore. [Fix] Intel submitted a patch, it will make those two kconfig options exclusive, and the legacy soc's option has higher priority, if both of them are enabled, sof's option will be disabled. [Test Case] Build the kernel and check the debian/build/$buidling_dir/.config, the SND_SOC_SOF_BROADWELL_SUPPORT is disabled. [Regression Risk] Low, so far, the sof driver can't support broadwell machine well, so there is no machine use this driver yet. Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839
[Kernel-packages] [Bug 1856069] [NEW] package nvidia-dkms-418 418.56-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-418 package post-installation script subprocess returned error exit statu
Public bug reported: After upgrading to eoan and updating all packages, I'm unable to enable the nVidia drivers. I haven't done much to enable new PPAs yet, though. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 Date: Tue Dec 10 15:32:16 2019 ErrorMessage: installed nvidia-dkms-418 package post-installation script subprocess returned error exit status 10 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-418 Title: package nvidia-dkms-418 418.56-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-418 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-12-10 (0 days ago) ** Affects: nvidia-graphics-drivers-418 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan third-party-packages -- 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/1856069 Title: package nvidia-dkms-418 418.56-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-418 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-418 package in Ubuntu: New Bug description: After upgrading to eoan and updating all packages, I'm unable to enable the nVidia drivers. I haven't done much to enable new PPAs yet, though. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 Date: Tue Dec 10 15:32:16 2019 ErrorMessage: installed nvidia-dkms-418 package post-installation script subprocess returned error exit status 10 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-418 Title: package nvidia-dkms-418 418.56-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-418 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-12-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1856069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work on a Thinkpad p50
I just found out about this. I wanted to get rid of the screen tearing that I observed on my Nitro AN515-53 laptop running Ubuntu 18.04.3 LTS with NVIDIA GeForce GTX 1050 Mobile GPU. I used https://askubuntu.com/a/020 and set nvidia_drm modeset=1 but then my external monitors didn't work after the reboot. So I switched from gdm3 to lightdm and that does the trick for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1706474 Title: gdm3 nvidia modeset=1 is broken, external screens don't work on a Thinkpad p50 Status in gdm3 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Invalid Bug description: ubuntu 17.04 with gnome desktop. The laptop is a Thinkpad p50 with a quadro M1000M. To get this bug I am using the hybrid graphics mode. This problem occurs with 375.82 and also with the new 384 driver. When using gdm3 and options nvidia_375_drm modeset=1 the greeter only shows the laptop screen. My two external displays are not turned on. they do not appear in the listing of diplays in xrandr the problem does not occur if modeset=0 or if I use lightdm I suspect this is a known bug but I am not quite sure so I'm reporting it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140
** Package changed: ubuntu => hwe-next -- 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/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 Status in HWE Next: Confirmed Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [Impact] With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT is set to Y, then it will make the legacy intel soc driver fail, and moreover the current sof driver can't support broadwell well, as a result, many broadwell computers with I2S codec can't support sound anymore. [Fix] Intel submitted a patch, it will make those two kconfig options exclusive, and the legacy soc's option has higher priority, if both of them are enabled, sof's option will be disabled. [Test Case] Build the kernel and check the debian/build/$buidling_dir/.config, the SND_SOC_SOF_BROADWELL_SUPPORT is disabled. [Regression Risk] Low, so far, the sof driver can't support broadwell machine well, so there is no machine use this driver yet. Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <->
[Kernel-packages] [Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
The problem still manifests with 5.3.0-24-generic, in addition to the previously known-good kernel used by 19.04. Like others I tried disabling the TPM but it did not help. Given the problem still manifests with the previous kernel, this looks like it may be a GRUB issue. Will try downgrading GRUB and updating this ticket if I learn more. -- 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/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" Status in linux package in Ubuntu: Incomplete Bug description: [19.10] Boot hangs at "loading initial ramdisk" So after completing the upgrade from 19.04 to 19.10, my computer got stuck on the solid purple Grub screen upon reboot. After getting into the grub menu on next boot and booting from advanced options, I see that it gets to "loading initial ramdisk" and then just hangs forever. I am able to boot without issues on the old kernel (5.0.0-32-generic), but not the one that got installed with the upgrade (5.3.0-18-generic). Things I've tried based on what worked for other people who got this problem (though I haven't found anyone who has it specifically with 19.10): acpi=off dis_ucode_ldr disabling secure boot recovery mode making sure all packages are up to date I'm kind of at a loss of what to do, other than just keep using the old kernel. (which presumably might cause problems at some point?) I'm posting this from Ubuntu 19.04, since upgrade from 19.04 to 19.10 resulted in unable to boot system. Hardware Dell XPS 9550 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 91 structures occupying 5683 bytes. Table at 0x000E. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: 1.11.2 Release Date: 07/30/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.11 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: XPS 15 9550 Version: Not Specified Serial Number: 5QRHRF2 UUID: 4c4c4544-0051-5210-8048-b5c04f524632 Wake-up Type: Power Switch SKU Number: 06E4 Family: XPS Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 0N7TVV Version: A01 Serial Number: /5QRHRF2/CN129636CS0026/ Asset Tag: Not Specified Features: Board is a hosting board Board is replaceable Location In Chassis: Not Specified Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 22 bytes Chassis Information Manufacturer: Dell Inc. Type: Laptop Lock: Not Present Version: Not Specified Serial Number: 5QRHRF2 Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Laptop Handle 0x0004, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB1 Internal Connector Type: None External Reference Designator: USB1 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0005, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB2 Internal Connector Type: None External Reference Designator: USB2 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0006, DMI type 8, 9 bytes Port Connector Info
[Kernel-packages] [Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
This is to confirm manually downgrading the grub packages to those found in 19.04 fixes the problem. This is with TPM still disabled in the BIOS and dis_ucode_ldr kernel command line flag, but I don't think either of those are contributing to the successful boot. If you're stuck on this issue, $ sudo dpkg --get-selections | grep ^grub - For each package listed in the output, visit https://packages.ubuntu.com/ and search the 'disco-updates' distribution for the associated package name. - Get the URL: Ensure you selected 'disco-updates' distribution in the search config, do the search, click the single result (link is also "disco-updates"), click "amd64", right-click copy one of the .deb download links - wget each package in turn, for example: $ wget http://mirrors.kernel.org/ubuntu/pool/main/g/grub2/grub2-common_2.02+dfsg1-12ubuntu2.1_amd64.deb - dpkg -i each package in turn, for example: $ sudo dpkg -i grub2-common_2.02+dfsg1-12ubuntu2.1_amd64.deb Some packages depend on each other, so you might have to download e.g. the common package and install it with "dpkg -i" at the same time as the dependent package -- just supply both .debs on the dpkg command line. - Run update-grub and grub-install - Your machine should boot again. - Don't install upgrades from apt until a real fix appears -- they'll upgrade GRUB again. Investigate apt package pinning to keep this configuration permanently (TBD -- I haven't done this yet) -- 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/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" Status in linux package in Ubuntu: Incomplete Bug description: [19.10] Boot hangs at "loading initial ramdisk" So after completing the upgrade from 19.04 to 19.10, my computer got stuck on the solid purple Grub screen upon reboot. After getting into the grub menu on next boot and booting from advanced options, I see that it gets to "loading initial ramdisk" and then just hangs forever. I am able to boot without issues on the old kernel (5.0.0-32-generic), but not the one that got installed with the upgrade (5.3.0-18-generic). Things I've tried based on what worked for other people who got this problem (though I haven't found anyone who has it specifically with 19.10): acpi=off dis_ucode_ldr disabling secure boot recovery mode making sure all packages are up to date I'm kind of at a loss of what to do, other than just keep using the old kernel. (which presumably might cause problems at some point?) I'm posting this from Ubuntu 19.04, since upgrade from 19.04 to 19.10 resulted in unable to boot system. Hardware Dell XPS 9550 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 91 structures occupying 5683 bytes. Table at 0x000E. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: 1.11.2 Release Date: 07/30/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.11 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: XPS 15 9550 Version: Not Specified Serial Number: 5QRHRF2 UUID: 4c4c4544-0051-5210-8048-b5c04f524632 Wake-up Type: Power Switch SKU Number: 06E4 Family: XPS Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 0N7TVV Version: A01 Serial Number: /5QRHRF2/CN129636CS0026/ Asset Tag: Not Specified Features: Board is a hosting board Board is replaceable Location In Chassis: Not Specified Chassis Handle: 0x0003 Type: Motherboard Contained Object Hand
[Kernel-packages] [Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
Forgot to mention: I'm also on XPS 9550, and used an 18.04 live CD to get into a rescue system (mounted the SSD, bind mounted /proc /sys /run /dev then chrooted) -- 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/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" Status in linux package in Ubuntu: Incomplete Bug description: [19.10] Boot hangs at "loading initial ramdisk" So after completing the upgrade from 19.04 to 19.10, my computer got stuck on the solid purple Grub screen upon reboot. After getting into the grub menu on next boot and booting from advanced options, I see that it gets to "loading initial ramdisk" and then just hangs forever. I am able to boot without issues on the old kernel (5.0.0-32-generic), but not the one that got installed with the upgrade (5.3.0-18-generic). Things I've tried based on what worked for other people who got this problem (though I haven't found anyone who has it specifically with 19.10): acpi=off dis_ucode_ldr disabling secure boot recovery mode making sure all packages are up to date I'm kind of at a loss of what to do, other than just keep using the old kernel. (which presumably might cause problems at some point?) I'm posting this from Ubuntu 19.04, since upgrade from 19.04 to 19.10 resulted in unable to boot system. Hardware Dell XPS 9550 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 91 structures occupying 5683 bytes. Table at 0x000E. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: 1.11.2 Release Date: 07/30/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.11 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: XPS 15 9550 Version: Not Specified Serial Number: 5QRHRF2 UUID: 4c4c4544-0051-5210-8048-b5c04f524632 Wake-up Type: Power Switch SKU Number: 06E4 Family: XPS Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 0N7TVV Version: A01 Serial Number: /5QRHRF2/CN129636CS0026/ Asset Tag: Not Specified Features: Board is a hosting board Board is replaceable Location In Chassis: Not Specified Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 22 bytes Chassis Information Manufacturer: Dell Inc. Type: Laptop Lock: Not Present Version: Not Specified Serial Number: 5QRHRF2 Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Laptop Handle 0x0004, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB1 Internal Connector Type: None External Reference Designator: USB1 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0005, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB2 Internal Connector Type: None External Reference Designator: USB2 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0006, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSBC1 Internal Connector Type: None External Reference Designator: USB TYPEC External Connector Type: Access
[Kernel-packages] [Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
For anyone trying to figure out what's broken, $ git diff debian/2.02+dfsg1-12ubuntu2.1 debian/2.04-1ubuntu12|diffstat Using the repo from https://git.launchpad.net/~ubuntu-core- dev/grub/+git/ubuntu/ Unfortunately produces a 392k diff. The tags don't appear to share a common ancestry so 'git log' is similarly useless -- 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/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" Status in grub2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: [19.10] Boot hangs at "loading initial ramdisk" So after completing the upgrade from 19.04 to 19.10, my computer got stuck on the solid purple Grub screen upon reboot. After getting into the grub menu on next boot and booting from advanced options, I see that it gets to "loading initial ramdisk" and then just hangs forever. I am able to boot without issues on the old kernel (5.0.0-32-generic), but not the one that got installed with the upgrade (5.3.0-18-generic). Things I've tried based on what worked for other people who got this problem (though I haven't found anyone who has it specifically with 19.10): acpi=off dis_ucode_ldr disabling secure boot recovery mode making sure all packages are up to date I'm kind of at a loss of what to do, other than just keep using the old kernel. (which presumably might cause problems at some point?) I'm posting this from Ubuntu 19.04, since upgrade from 19.04 to 19.10 resulted in unable to boot system. Hardware Dell XPS 9550 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 91 structures occupying 5683 bytes. Table at 0x000E. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: 1.11.2 Release Date: 07/30/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.11 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: XPS 15 9550 Version: Not Specified Serial Number: 5QRHRF2 UUID: 4c4c4544-0051-5210-8048-b5c04f524632 Wake-up Type: Power Switch SKU Number: 06E4 Family: XPS Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 0N7TVV Version: A01 Serial Number: /5QRHRF2/CN129636CS0026/ Asset Tag: Not Specified Features: Board is a hosting board Board is replaceable Location In Chassis: Not Specified Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 22 bytes Chassis Information Manufacturer: Dell Inc. Type: Laptop Lock: Not Present Version: Not Specified Serial Number: 5QRHRF2 Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Laptop Handle 0x0004, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB1 Internal Connector Type: None External Reference Designator: USB1 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0005, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB2 Internal Connector Type: None External Reference Designator: USB2 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0006, DMI type 8, 9
[Kernel-packages] [Bug 1857074] Re: Cavium ThunderX CN88XX crashes on boot
I'm having trouble updating the kernel on one of my Cavium boxes due to this bug. Setting `nopti` in kernel parameters didn't stop the segfaults and anytime I try to run `apt update` after enabling the -proposed repo, apt hangs due to a segfault and I can't run it again unless I reboot. apt still won't exit cleanly though. Hoping for a tip on upgrading the 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/1857074 Title: Cavium ThunderX CN88XX crashes on boot Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Series: Bionic Kernel: 4.15.0-74.84 linux-generic Steps to reproduce: Install 4.15.0-74.84 Kernel and boot the system. The following crash was observed while testing the proposed kernel for the 2019.12.02 SRU Cycle. This kernel was built to include fixes for the following bugs: * [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX (LP: #1853326) - Revert "arm64: Use firmware to detect CPUs that are not affected by Spectre-v2" - Revert "arm64: Get rid of __smccc_workaround_1_hvc_*" * [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 and Kunpeng920 (LP: #1852723) - SAUCE: arm64: capabilities: Move setup_boot_cpu_capabilities() call to correct place The following crash appears to be a NEW bug. not related to the prior bugs listed above. This bug DOES NOT APPEAR to be related to LP#1857073. This is another NEW BUG. Hostname: Starmie Probable Cause is unknown at this point and still under investigation. [ OK ] Found device WDC_WD5003ABYZ-011FA0 efi. Mounting /boot/efi... [ OK ] Mounted /boot/efi. [ OK ] Reached target Local File Systems. Starting AppArmor initialization... Starting Tell Plymouth To Write Out Runtime Data... Starting ebtables ruleset management... [ 20.942427] kernel BUG at /build/linux-pWET3k/linux-4.15.0/fs/buffer.c:1240! [ 20.951416] Internal error: Oops - BUG: 0 [#1] SMP [ 20.958153] Modules linked in: nls_iso8859_1 thunderx_edac thunderx_zip cavium_rng_vf shpchp cavium_rng gpio_keys uio_pdrv_genirq ipmi_ssif uio ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf nicpf ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect aes_ce_blk sysimgblt fb_sys_fops aes_ce_cipher crc32_ce drm crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce ahci thunder_bgx libahci thunder_xcv i2c_thunderx mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [ 21.044326] Process systemd (pid: 1, stack limit = 0x5af6f18b) [ 21.053858] CPU: 1 PID: 1 Comm: systemd Not tainted 4.15.0-74-generic #84-Ubuntu [ 21.063931] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., BIOS 5.11 12/12/2012 [ 21.074790] pstate: 20400085 (nzCv daIf +PAN -UAO) [ 21.082096] pc : __find_get_block+0x2e8/0x398 [ 21.088917] lr : __getblk_gfp+0x3c/0x2a8 [ 21.095379] sp : 099ab7e0 [ 21.101062] x29: 099ab7e0 x28: [ 21.108699] x27: x26: [ 21.116265] x25: 0001 x24: [ 21.123788] x23: 0008 x22: 801f26116c80 [ 21.131302] x21: 801f26116c80 x20: 245c [ 21.138808] x19: 1000 x18: a59c3a70 [ 21.146300] x17: x16: [ 21.153730] x15: 0020 x14: 0012 [ 21.161083] x13: 2f7374696e752f64 x12: 0101010101010101 [ 21.168397] x11: 7f7f7f7f7f7f7f7f x10: 0972d000 [ 21.175689] x9 : x8 : 801f7ba7e3c0 [ 21.183042] x7 : 801f7ba7e3e0 x6 : [ 21.190667] x5 : 0004 x4 : 0020 [ 21.197955] x3 : 0008 x2 : 1000 [ 21.205680] x1 : 245c x0 : 0080 [ 21.212918] Call trace: [ 21.217257] __find_get_block+0x2e8/0x398 [ 21.223160] __getblk_gfp+0x3c/0x2a8 [ 21.228644] ext4_getblk+0xcc/0x1b0 [ 21.233991] ext4_bread_batch+0x78/0x1c8 [ 21.239726] ext4_find_entry+0x2d4/0x598 [ 21.245416] ext4_lookup+0xac/0x278 [ 21.250612] lookup_slow+0xac/0x190 [ 21.255736] walk_component+0x228/0x340 [ 21.261151] link_path_walk+0x2f4/0x568 [ 21.266499] path_parentat+0x44/0x88 [ 21.271521] filename_parentat+0xa0/0x170 [ 21.276924] filename_create+0x60/0x168 [ 21.282082] SyS_symlinkat+0x80/0x128 [ 21.287013] el0_svc_naked+0x30/0x34 [ 21.29
[Kernel-packages] [Bug 1862631] [NEW] Wifi disabled after sleep wakeup
Public bug reported: The system went to sleep on lid close and sometimes when you open the lid and attempt to login the screen flashes and you get logged out (GDM crashes) At this point you can login again but the WIFI system is no longer available. If you attempt to unload the iwlwifi module and reload you can see the firmware get loaded in but the system still shows no wifi available ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "files.tar" https://bugs.launchpad.net/bugs/1862631/+attachment/5327020/+files/files.tar -- 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/1862631 Title: Wifi disabled after sleep wakeup Status in linux package in Ubuntu: New Bug description: The system went to sleep on lid close and sometimes when you open the lid and attempt to login the screen flashes and you get logged out (GDM crashes) At this point you can login again but the WIFI system is no longer available. If you attempt to unload the iwlwifi module and reload you can see the firmware get loaded in but the system still shows no wifi available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862631] Re: Wifi disabled after sleep wakeup
apport information ** Tags added: apport-collected bionic ** Description changed: - The system went to sleep on lid close and sometimes when you open the - lid and attempt to login the screen flashes and you get logged out (GDM - crashes) At this point you can login again but the WIFI system is no - longer available. If you attempt to unload the iwlwifi module and - reload you can see the firmware get loaded in but the system still shows - no wifi available + The system went to sleep on lid close and sometimes when you open the lid and attempt to login the screen flashes and you get logged out (GDM crashes) At this point you can login again but the WIFI system is no longer available. If you attempt to unload the iwlwifi module and reload you can see the firmware get loaded in but the system still shows no wifi available + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: z 3629 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-07-25 (199 days ago) + InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 + MachineType: LENOVO 20QESITE06 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-1015-oem-osp1 N/A + linux-backports-modules-5.0.0-1015-oem-osp1 N/A + linux-firmware 1.173.10 + Tags: bionic + Uname: Linux 5.0.0-1015-oem-osp1 x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/02/2019 + dmi.bios.vendor: LENOVO + dmi.bios.version: N2HET34W (1.17 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20QESITE06 + dmi.board.vendor: LENOVO + dmi.board.version: Not Defined + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrN2HET34W(1.17):bd08/02/2019:svnLENOVO:pn20QESITE06:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE06:rvrNotDefined:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad X1 Carbon 7th + dmi.product.name: 20QESITE06 + dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th + dmi.product.version: ThinkPad X1 Carbon 7th + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1862631/+attachment/5327044/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862631 Title: Wifi disabled after sleep wakeup Status in linux package in Ubuntu: Confirmed Bug description: The system went to sleep on lid close and sometimes when you open the lid and attempt to login the screen flashes and you get logged out (GDM crashes) At this point you can login again but the WIFI system is no longer available. If you attempt to unload the iwlwifi module and reload you can see the firmware get loaded in but the system still shows no wifi available --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 3629 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (199 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE06 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-
[Kernel-packages] [Bug 1862631] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1862631/+attachment/5327045/+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/1862631 Title: Wifi disabled after sleep wakeup Status in linux package in Ubuntu: Confirmed Bug description: The system went to sleep on lid close and sometimes when you open the lid and attempt to login the screen flashes and you get logged out (GDM crashes) At this point you can login again but the WIFI system is no longer available. If you attempt to unload the iwlwifi module and reload you can see the firmware get loaded in but the system still shows no wifi available --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 3629 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (199 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE06 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET34W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE06 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET34W(1.17):bd08/02/2019:svnLENOVO:pn20QESITE06:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE06:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE06 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862631] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1862631/+attachment/5327046/+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/1862631 Title: Wifi disabled after sleep wakeup Status in linux package in Ubuntu: Confirmed Bug description: The system went to sleep on lid close and sometimes when you open the lid and attempt to login the screen flashes and you get logged out (GDM crashes) At this point you can login again but the WIFI system is no longer available. If you attempt to unload the iwlwifi module and reload you can see the firmware get loaded in but the system still shows no wifi available --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 3629 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (199 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE06 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET34W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE06 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET34W(1.17):bd08/02/2019:svnLENOVO:pn20QESITE06:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE06:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE06 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862631] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1862631/+attachment/5327050/+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/1862631 Title: Wifi disabled after sleep wakeup Status in linux package in Ubuntu: Confirmed Bug description: The system went to sleep on lid close and sometimes when you open the lid and attempt to login the screen flashes and you get logged out (GDM crashes) At this point you can login again but the WIFI system is no longer available. If you attempt to unload the iwlwifi module and reload you can see the firmware get loaded in but the system still shows no wifi available --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 3629 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (199 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE06 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET34W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE06 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET34W(1.17):bd08/02/2019:svnLENOVO:pn20QESITE06:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE06:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE06 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862631] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1862631/+attachment/5327049/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862631 Title: Wifi disabled after sleep wakeup Status in linux package in Ubuntu: Confirmed Bug description: The system went to sleep on lid close and sometimes when you open the lid and attempt to login the screen flashes and you get logged out (GDM crashes) At this point you can login again but the WIFI system is no longer available. If you attempt to unload the iwlwifi module and reload you can see the firmware get loaded in but the system still shows no wifi available --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 3629 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (199 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE06 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET34W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE06 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET34W(1.17):bd08/02/2019:svnLENOVO:pn20QESITE06:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE06:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE06 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862631] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1862631/+attachment/5327047/+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/1862631 Title: Wifi disabled after sleep wakeup Status in linux package in Ubuntu: Confirmed Bug description: The system went to sleep on lid close and sometimes when you open the lid and attempt to login the screen flashes and you get logged out (GDM crashes) At this point you can login again but the WIFI system is no longer available. If you attempt to unload the iwlwifi module and reload you can see the firmware get loaded in but the system still shows no wifi available --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 3629 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (199 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE06 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET34W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE06 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET34W(1.17):bd08/02/2019:svnLENOVO:pn20QESITE06:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE06:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE06 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862631] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1862631/+attachment/5327051/+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/1862631 Title: Wifi disabled after sleep wakeup Status in linux package in Ubuntu: Confirmed Bug description: The system went to sleep on lid close and sometimes when you open the lid and attempt to login the screen flashes and you get logged out (GDM crashes) At this point you can login again but the WIFI system is no longer available. If you attempt to unload the iwlwifi module and reload you can see the firmware get loaded in but the system still shows no wifi available --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 3629 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (199 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE06 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET34W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE06 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET34W(1.17):bd08/02/2019:svnLENOVO:pn20QESITE06:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE06:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE06 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862631] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1862631/+attachment/5327048/+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/1862631 Title: Wifi disabled after sleep wakeup Status in linux package in Ubuntu: Confirmed Bug description: The system went to sleep on lid close and sometimes when you open the lid and attempt to login the screen flashes and you get logged out (GDM crashes) At this point you can login again but the WIFI system is no longer available. If you attempt to unload the iwlwifi module and reload you can see the firmware get loaded in but the system still shows no wifi available --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 3629 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (199 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE06 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET34W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE06 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET34W(1.17):bd08/02/2019:svnLENOVO:pn20QESITE06:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE06:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE06 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862631] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1862631/+attachment/5327053/+files/ProcModules.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/1862631 Title: Wifi disabled after sleep wakeup Status in linux package in Ubuntu: Confirmed Bug description: The system went to sleep on lid close and sometimes when you open the lid and attempt to login the screen flashes and you get logged out (GDM crashes) At this point you can login again but the WIFI system is no longer available. If you attempt to unload the iwlwifi module and reload you can see the firmware get loaded in but the system still shows no wifi available --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 3629 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (199 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE06 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET34W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE06 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET34W(1.17):bd08/02/2019:svnLENOVO:pn20QESITE06:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE06:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE06 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862631] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1862631/+attachment/5327052/+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/1862631 Title: Wifi disabled after sleep wakeup Status in linux package in Ubuntu: Confirmed Bug description: The system went to sleep on lid close and sometimes when you open the lid and attempt to login the screen flashes and you get logged out (GDM crashes) At this point you can login again but the WIFI system is no longer available. If you attempt to unload the iwlwifi module and reload you can see the firmware get loaded in but the system still shows no wifi available --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 3629 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (199 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE06 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET34W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE06 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET34W(1.17):bd08/02/2019:svnLENOVO:pn20QESITE06:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE06:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE06 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez
Dan, I can confirm that after enabling proposed for bionic and then issuing the command which installs bluez/5.48-0ubuntu3.2 $ sudo apt-get install bluez/bionic-proposed The issue has been fixed for me. I have a Dell Latitude E5400. Thanks, David -- 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/1759836 Title: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in bluez source package in Bionic: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Invalid Status in bluez source package in Disco: Fix Released Status in linux source package in Disco: Invalid Status in systemd source package in Disco: Invalid Status in bluez source package in Eoan: Fix Released Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Invalid Status in bluez package in Debian: New Bug description: [impact] on specific Dell systems, with a specific usb bluetooth device built- in, the udev rule 'hid2hci' provided by the 'bluez' package causes an endless loop of uevents resulting from 'bind' or 'unbind' kernel uevents. These new events were added to the kernel after the 'hid2hci' udev rule was written. [test case] the specific Dell system is required to be able to reproduce this, or at least the specific usb bluetooth hardware included in that system. Reproducing this is reportedly easy, for example comment 75 indicates it happens on every boot. When this happens, any process monitor (e.g. ps, top, etc) will show the 'udevd' process using 100% of a cpu, and 'udevadm monitor' should show repeated 'bind' and 'unbind' events as mentioned in comment 39. [regression potential] as this alters what kernel uevents the 'hid2hci' udev rule processes, regressions would involve the affected usb bluetooth device failing to be set up, or otherwise not processing the uevents correctly. [other info] this is not fixed yet upstream, as of my last check, but has been submitted upstream as mentioned in comment 95. original description: -- The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
