[Kernel-packages] [Bug 1262634] Re: Latest firmware for qla2xxx
I'm pretty sure this has been dealt with ** Changed in: linux-firmware (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1262634 Title: Latest firmware for qla2xxx Status in linux-firmware package in Ubuntu: Fix Released Bug description: Please update the firmwares in /lib/firmware with the latest from http://ldriver.qlogic.com/firmware/. Esp. the qla2400 firmware is older than the latest from Qlogic which includes several improvements to timeouts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1262634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
Hi Daniel, thx for testing the special kernel build and verifying that it now boots again on KVM. Since the initial request from the kernel team was to verify that secureboot and lockdown works with 5.10 on ppc64el, it would be important to test that, too - maybe you or Nayna may try secureboot lock-down testing as well? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: Canonical requests to test the secure boot for the 5.10 kernel but kernel fails to boot with secure boot disabled. The 5.10 kernel can be found in: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap They can be installed by installing the linux-generic-wip package with this PPA enabled. As usual, they are only signed using a key specific to that PPA. This key can be retrieved from the signing tarballs for the kernels, e.g.: http://ppa.launchpad.net/canonical-kernel- team/bootstrap/ubuntu/dists/hirsute/main/signed/linux-5.10-ppc64el/5.10.0-2.3/signed.tar.gz Our tester installed the 5.10 kernel via aptitude. If booting directly from the bootmenu, it stucks at: "kexec_core: Starting new kernel" If booting recovery kernel for 5.10.0, it proceeds farther and after kexec_core, it failed at: " [0.029830] LSM: Security Framework initializing [0.029916] Yama: b " Two attempts with a different scenario; running with 5.8 kernel and boot via commandline for 5.10: kexec -l /boot/vmlinux-5.10.0-0-generic --initrd=/boot/initrd.img-5.10.0-0-generic --append="root=UUID=49d000cb-dba2-4d70-809e-38f2b31d0f09 ro quiet splash" kexec -e Both attempts also failed while rebooting, once with the same error as the error from booting with bootmenu; the other failure occurred a lot earlier. Wondering what new CONFIGs and/or features for the 5.10 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
** Description changed: - [SRU] - - BugLink: https://bugs.launchpad.net/bugs/1879633 + [SRU Justification] [Impact] Qualcomm QCA6390 series not recognized due to the lack of ath11k driver. $ lspci :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101] - Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] + Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] [Fix] 25 additional fixes in ath tree (https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git), tag ath11k-qca6390-bringup-202011301608 to resolve issues on TGL platforms, and firmware updates from mainline are required. [Test Case] 1. Install firmwares & boot from patched kernel, 2. ath11k should be now up and running. Check with -`sudo dmesg | grep ath11k` + `sudo dmesg | grep ath11k` [Where problems could occur] There has been a lot patches landed in kernel since 5.7 devel cycle. The last bits here has merge base with mainline at v5.10-rc4, and since then only patches for ath11k itself has been committed. == Original Bug Description == Qualcomm QCA6390 series not recognized due to the lack of ath11k driver. :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101] Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] Depending on bug 1891632 to fix Wi-Fi dead after resumed from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1842 F pulseaudio CasperMD5CheckResult: skip DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enx00e04c6801fa no wireless extensions. MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=580a1e2b-9a42-4f3b-b20f-ddbed7b572f5 ro ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.6.0-1010-oem N/A linux-backports-modules-5.6.0-1010-oem N/A linux-firmware 1.187+lp1867862.1 RfKill: Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/14/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.9 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.9:bd05/14/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1879633 Title: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Triaged Status in linux source package in Groovy: Triaged Status in linux-firmware source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [SRU Justification] [Impact] Qualcomm QCA6390 series not recognized due to the lack of ath11k driver. $ lspci :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101] Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] [Fix] 25 additional fixes in ath tree (https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git), tag ath11k-qca6390-bringup-202011301608 to resolve issues on TGL platforms, and firmware updates from mainline are required. [Test Case] 1. Install firmwares & boot from patched kernel, 2. ath11k should be now up and running. Check with `sudo dmesg |
[Kernel-packages] [Bug 1904521] Re: Intel Tiger Lake IDs supplement
** Tags removed: verification-needed-focal verification-needed-groovy ** Tags added: verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1904521 Title: Intel Tiger Lake IDs supplement Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Bug description: [Impact] Intel Tiger Lake-H platform requires new pin settings and IDs to enable. [Fix] Intel provides us a list of TGL-H commits from 5.8 and 5.9, we need all of the commits to enable TGL-H platforms completely. [Test] Verified those commits on Intel TGL-H SDP [Regression potential] Low, all of those commits are adding new IDs for TGL-H platform. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1904521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890130] Re: Add support for Intel Bluetooth Device Typhoon Peak (8087:0032)
** Description changed:
- [SRU]
-
- BugLink: https://bugs.launchpad.net/bugs/1890130
+ [SRU Justification: linux-firmware]
[Impact]
To support new Intel Typhoon Peak Bluetooth, USB ID 8087:0032
specifically.
[Fix]
Kernel driver patchset
https://patchwork.kernel.org/project/bluetooth/list/?series=387475
targeting v5.11, as well as firmware intel/ibt-0041-0041.{ddc,sfi} from
linux-firmware commit 5cbf459c1ed9 and 7eb7fda50e9a.
[Test Case]
1. Install aforementioned firmware blobs and boot with kernel built with
these patches applied.
2. Run `btmgmt info` to find out if bluetooth controller is now
available.
[Where problems could occur]
Typhoon Peak is a whole new generation that it has its own call path to
load firmware, initial setup, etc. These patches are almost completely
isolated from previous generation, so little regression risk introduced.
== Original Bug Description ==
Device from /sys/kernel/debug/usb/devices:
T: Bus=01 Lev=01 Prnt=01 Port=13 Cnt=02 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=8087 ProdID=0032 Rev= 0.00
Prerequisite commits:
*
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=875e16759005e3bdaa84eb2741281f37ba35b886
*
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3e4e3f73b9f4
And:
https://patchwork.kernel.org/project/bluetooth/list/?series=387475
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: u 2507 F pulseaudio
CasperMD5CheckResult: skip
Dependencies:
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-charmander+X68
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-11-09 (25 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
MachineType: Dell Inc. Latitude 5520
Package: linux
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-2005-oem
root=UUID=0ece6279-6ac8-4155-8542-c7a41c97f7d4 ro i915.enable_psr=1
ProcVersionSignature: Ubuntu
5.10.0-2005.6+lp1902848.lp1890130.4.ax210.iwlwifi.bluetooth-oem 5.10.0-rc5
RelatedPackageVersions:
linux-restricted-modules-5.10.0-2005-oem N/A
linux-backports-modules-5.10.0-2005-oem N/A
linux-firmware 1.187.3
Tags: focal
Uname: Linux 5.10.0-2005-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/19/2020
dmi.bios.release: 0.4
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.4.77
dmi.board.vendor: Dell Inc.
dmi.chassis.asset.tag: 2345678
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr0.4.77:bd10/19/2020:br0.4:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5520
dmi.product.sku: 0A21
dmi.sys.vendor: Dell Inc.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1890130
Title:
Add support for Intel Bluetooth Device Typhoon Peak (8087:0032)
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-firmware source package in Focal:
In Progress
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Won't Fix
Status in linux source package in Groovy:
In Progress
Status in linux-firmware source package in Groovy:
In Progress
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
In Progress
Status in linux-firmware source package in Hirsute:
Invalid
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification: linux-firmware]
[Impact]
To support new Intel Typhoon Peak Bluetooth, USB ID 8087:0032
specifically.
[Fix]
Kernel driver patchset
https://patchwork.kernel.org/project/bluetooth/list/?series=387475
targeting v5.11, as well as firmware intel/ibt-0041-0041.{ddc,sfi} from
linux-firmware commit 5cbf459c1ed9 and 7eb7fda50e9a.
[Test Case]
[Kernel-packages] [Bug 1905663] Re: Add dpcd backlight control for 0x4c83 0x4f41
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1905663 Title: Add dpcd backlight control for 0x4c83 0x4f41 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: In Progress Bug description: [Impact] There is a new OLED panel that is required to be listed in the EDID quirk to make its backlight work. [Fix] The commit adds its EDID to the quirk. https://lkml.org/lkml/2020/11/19/1564 [Test] Verified on Dell's platform with this panel. [Where problems could occur] Only if this panel switches to use PWM mode only, and doesn't support DPCD backlight. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904590] Re: Virtualbox does not work on 20.04-edge kernel due to DKMS build failure
FYI, from the Virtualbox changelog at
https://www.virtualbox.org/wiki/Changelog-6.1:
> VirtualBox 6.1.14:
> ...
> Linux host and guest: Linux kernel version 5.8 support
Therefore, it should be fixed after the VirtualBox package on Ubuntu
20.04 gets updated. After running into the same issue as you, I
installed VirtualBox 6.1.16 from the Virtualbox.org contrib PPA, and the
VMs run alright on my fresh 5.8.0-33-lowlatency kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1904590
Title:
Virtualbox does not work on 20.04-edge kernel due to DKMS build
failure
Status in dkms package in Ubuntu:
Confirmed
Status in virtualbox package in Ubuntu:
Confirmed
Bug description:
Building DKMS kernel modules for Virtualbox for kernel 5.8 (Ubuntu
kernel linux-image-generic-hwe-20.04-edge) fails and subsequently
Virtualbox does not work.
Ubuntu release:
~$ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Relevant Virtualbox packages/versions:
virtualbox6.1.10-dfsg-1~ubuntu1.20.04.1
virtualbox-dkms 6.1.10-dfsg-1~ubuntu1.20.04.1
virtualbox-guest-additions-iso6.1.10-1~ubuntu1.20.04.1
virtualbox-qt 6.1.10-dfsg-1~ubuntu1.20.04.1
Kernel packages:
~$ dpkg-query -f '${Package} ${Status}\n' -W "linux-image*" | awk '$NF ==
"installed"{print $1}'
linux-image-5.4.0-54-generic
linux-image-5.8.0-28-generic
linux-image-5.8.0-29-generic
linux-image-generic
linux-image-generic-hwe-20.04-edge
Kernel:
~$ uname -r
5.8.0-29-generic
I get an error when building DKMS for Virtualbox for kernel 5.8:
~$ sudo /usr/lib/dkms/dkms_autoinstaller start 5.8.0-29-generic
* dkms: running auto installation service for kernel 5.8.0-29-generic
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make -j8 KERNELRELEASE=5.8.0-29-generic -C
/lib/modules/5.8.0-29-generic/build
M=/var/lib/dkms/virtualbox/6.1.10/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.8.0-29-generic (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.10/build/make.log for more information.
Build log file:
~$ cat /var/lib/dkms/virtualbox/6.1.10/build/make.log
DKMS make.log for virtualbox-6.1.10 for kernel 5.8.0-29-generic (x86_64)
di 17 nov 2020 16:30:39 CET
make: Entering directory '/usr/src/linux-headers-5.8.0-29-generic'
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvGip.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvSem.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvTracer.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPLibAll.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/alloc-r0drv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/initterm-r0drv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/memobj-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/mpnotification-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/powernotification-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
In file included from ./include/asm-generic/percpu.h:7,
from ./arch/x86/include/asm/percpu.h:556,
from ./arch/x86/include/asm/preempt.h:6,
from ./include/linux/preempt.h:78,
from ./include/linux/spinlock.h:51,
from
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/../SUPDrvInternal.h:79,
from
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:32:
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c: In
function ‘supdrvOSChangeCR4’:
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:38:
error: ‘cpu_tlbstate’ undeclared (first use in this function); did you mean
‘cpuhp_state’?
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
| ^~~~
./include/linux/percpu-defs.h:318:9: note: in definition of macro
‘__pcpu_size_call_return’
318 | typeof(variable) pscr_ret__; \
| ^~~~
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:24:
note: in expansion of macro ‘this_cpu_read’
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
|^
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:38:
note: each undeclared identifier is reported only once for each function it
appears in
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
|
[Kernel-packages] [Bug 1904590] Re: Virtualbox does not work on 20.04-edge kernel due to DKMS build failure
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: virtualbox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1904590
Title:
Virtualbox does not work on 20.04-edge kernel due to DKMS build
failure
Status in dkms package in Ubuntu:
Confirmed
Status in virtualbox package in Ubuntu:
Confirmed
Bug description:
Building DKMS kernel modules for Virtualbox for kernel 5.8 (Ubuntu
kernel linux-image-generic-hwe-20.04-edge) fails and subsequently
Virtualbox does not work.
Ubuntu release:
~$ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Relevant Virtualbox packages/versions:
virtualbox6.1.10-dfsg-1~ubuntu1.20.04.1
virtualbox-dkms 6.1.10-dfsg-1~ubuntu1.20.04.1
virtualbox-guest-additions-iso6.1.10-1~ubuntu1.20.04.1
virtualbox-qt 6.1.10-dfsg-1~ubuntu1.20.04.1
Kernel packages:
~$ dpkg-query -f '${Package} ${Status}\n' -W "linux-image*" | awk '$NF ==
"installed"{print $1}'
linux-image-5.4.0-54-generic
linux-image-5.8.0-28-generic
linux-image-5.8.0-29-generic
linux-image-generic
linux-image-generic-hwe-20.04-edge
Kernel:
~$ uname -r
5.8.0-29-generic
I get an error when building DKMS for Virtualbox for kernel 5.8:
~$ sudo /usr/lib/dkms/dkms_autoinstaller start 5.8.0-29-generic
* dkms: running auto installation service for kernel 5.8.0-29-generic
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make -j8 KERNELRELEASE=5.8.0-29-generic -C
/lib/modules/5.8.0-29-generic/build
M=/var/lib/dkms/virtualbox/6.1.10/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.8.0-29-generic (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.10/build/make.log for more information.
Build log file:
~$ cat /var/lib/dkms/virtualbox/6.1.10/build/make.log
DKMS make.log for virtualbox-6.1.10 for kernel 5.8.0-29-generic (x86_64)
di 17 nov 2020 16:30:39 CET
make: Entering directory '/usr/src/linux-headers-5.8.0-29-generic'
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvGip.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvSem.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvTracer.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPLibAll.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/alloc-r0drv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/initterm-r0drv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/memobj-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/mpnotification-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/powernotification-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
In file included from ./include/asm-generic/percpu.h:7,
from ./arch/x86/include/asm/percpu.h:556,
from ./arch/x86/include/asm/preempt.h:6,
from ./include/linux/preempt.h:78,
from ./include/linux/spinlock.h:51,
from
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/../SUPDrvInternal.h:79,
from
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:32:
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c: In
function ‘supdrvOSChangeCR4’:
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:38:
error: ‘cpu_tlbstate’ undeclared (first use in this function); did you mean
‘cpuhp_state’?
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
| ^~~~
./include/linux/percpu-defs.h:318:9: note: in definition of macro
‘__pcpu_size_call_return’
318 | typeof(variable) pscr_ret__; \
| ^~~~
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:24:
note: in expansion of macro ‘this_cpu_read’
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
|^
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:38:
note: each undeclared identifier is reported only once for each function it
appears in
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
| ^~~~
./include/linux/percpu-defs.h:318:9: note: in definition of macro
‘__pcpu_size_call_return’
318 | typeof(variable) pscr_ret__; \
| ^~~~
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:24:
note: in expansion of macro
[Kernel-packages] [Bug 1904590] Re: Virtualbox does not work on 20.04-edge kernel due to DKMS build failure
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dkms (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1904590
Title:
Virtualbox does not work on 20.04-edge kernel due to DKMS build
failure
Status in dkms package in Ubuntu:
Confirmed
Status in virtualbox package in Ubuntu:
Confirmed
Bug description:
Building DKMS kernel modules for Virtualbox for kernel 5.8 (Ubuntu
kernel linux-image-generic-hwe-20.04-edge) fails and subsequently
Virtualbox does not work.
Ubuntu release:
~$ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Relevant Virtualbox packages/versions:
virtualbox6.1.10-dfsg-1~ubuntu1.20.04.1
virtualbox-dkms 6.1.10-dfsg-1~ubuntu1.20.04.1
virtualbox-guest-additions-iso6.1.10-1~ubuntu1.20.04.1
virtualbox-qt 6.1.10-dfsg-1~ubuntu1.20.04.1
Kernel packages:
~$ dpkg-query -f '${Package} ${Status}\n' -W "linux-image*" | awk '$NF ==
"installed"{print $1}'
linux-image-5.4.0-54-generic
linux-image-5.8.0-28-generic
linux-image-5.8.0-29-generic
linux-image-generic
linux-image-generic-hwe-20.04-edge
Kernel:
~$ uname -r
5.8.0-29-generic
I get an error when building DKMS for Virtualbox for kernel 5.8:
~$ sudo /usr/lib/dkms/dkms_autoinstaller start 5.8.0-29-generic
* dkms: running auto installation service for kernel 5.8.0-29-generic
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make -j8 KERNELRELEASE=5.8.0-29-generic -C
/lib/modules/5.8.0-29-generic/build
M=/var/lib/dkms/virtualbox/6.1.10/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.8.0-29-generic (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.10/build/make.log for more information.
Build log file:
~$ cat /var/lib/dkms/virtualbox/6.1.10/build/make.log
DKMS make.log for virtualbox-6.1.10 for kernel 5.8.0-29-generic (x86_64)
di 17 nov 2020 16:30:39 CET
make: Entering directory '/usr/src/linux-headers-5.8.0-29-generic'
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvGip.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvSem.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvTracer.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPLibAll.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/alloc-r0drv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/initterm-r0drv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/memobj-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/mpnotification-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/powernotification-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
In file included from ./include/asm-generic/percpu.h:7,
from ./arch/x86/include/asm/percpu.h:556,
from ./arch/x86/include/asm/preempt.h:6,
from ./include/linux/preempt.h:78,
from ./include/linux/spinlock.h:51,
from
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/../SUPDrvInternal.h:79,
from
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:32:
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c: In
function ‘supdrvOSChangeCR4’:
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:38:
error: ‘cpu_tlbstate’ undeclared (first use in this function); did you mean
‘cpuhp_state’?
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
| ^~~~
./include/linux/percpu-defs.h:318:9: note: in definition of macro
‘__pcpu_size_call_return’
318 | typeof(variable) pscr_ret__; \
| ^~~~
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:24:
note: in expansion of macro ‘this_cpu_read’
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
|^
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:38:
note: each undeclared identifier is reported only once for each function it
appears in
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
| ^~~~
./include/linux/percpu-defs.h:318:9: note: in definition of macro
‘__pcpu_size_call_return’
318 | typeof(variable) pscr_ret__; \
| ^~~~
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:24:
note: in expansion of macro
[Kernel-packages] [Bug 1898786] Re: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled
Hi @hloeung, these patches are available in 4.15.0-128-generic, and 5.4.0-58-generic. They are both re-spins of 4.15.0-126-generic and 5.4.0-56-generic, respectively. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898786 Title: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1898786 [Impact] Systems that utilise bcache can experience extremely high IO wait times when under constant IO pressure. The IO wait times seem to stay at a consistent 1 second, and never drop as long as the bcache shrinker is enabled. If you disable the shrinker, then IO wait drops significantly to normal levels. We did some perf analysis, and it seems we spend a huge amount of time in bch_mca_scan(), likely waiting for the mutex ">bucket_lock". Looking at the recent commits in Bionic, we found the following commit merged in upstream 5.1-rc1 and backported to 4.15.0-87-generic through upstream stable: commit 9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b Author: Coly Li Date: Wed Nov 13 16:03:24 2019 +0800 Subject: bcache: at least try to shrink 1 node in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b It mentions in the description that: > If sc->nr_to_scan is smaller than c->btree_pages, after the above > calculation, variable 'nr' will be 0 and nothing will be shrunk. It is > frequeently observed that only 1 or 2 is set to sc->nr_to_scan and make > nr to be zero. Then bch_mca_scan() will do nothing more then acquiring > and releasing mutex c->bucket_lock. This seems to be what is going on here, but the above commit only addresses when nr is 0. From what I can see, the problems we are experiencing are when nr is 1 or 2, and again, we just waste time in bch_mca_scan() waiting on c->bucket_lock, only to release c->bucket_lock since the shrinker loop never executes since there is no work to do. [Fix] The following commits fix the problem, and all landed in 5.6-rc1: commit 125d98edd11464c8e0ec9eaaba7d682d0f832686 Author: Coly Li Date: Fri Jan 24 01:01:40 2020 +0800 Subject: bcache: remove member accessed from struct btree Link: https://github.com/torvalds/linux/commit/125d98edd11464c8e0ec9eaaba7d682d0f832686 commit d5c9c470b01177e4d90cdbf178b8c7f37f5b8795 Author: Coly Li Date: Fri Jan 24 01:01:41 2020 +0800 Subject: bcache: reap c->btree_cache_freeable from the tail in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/d5c9c470b01177e4d90cdbf178b8c7f37f5b8795 commit e3de04469a49ee09c89e80bf821508df458ccee6 Author: Coly Li Date: Fri Jan 24 01:01:42 2020 +0800 Subject: bcache: reap from tail of c->btree_cache in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/e3de04469a49ee09c89e80bf821508df458ccee6 The first commit is a dependency of the other two. The first commit removes a "recently accessed" marker, used to indicate if a particular cache has been used recently, and if it has been, not consider it for cache eviction. The commit mentions that under heavy IO, all caches will end up being recently accessed, and nothing will ever be shrunk. The second commit changes a previous design decision of skipping the first 3 caches to shrink, since it is a common case to call bch_mca_scan() with nr being 1, or 2, just like 0 was common in the very first commit I mentioned. This time, if we land on 1 or 2, the loop exits and nothing happens, and we waste time waiting on locks, just like the very first commit I mentioned. The fix is to try shrink caches from the tail of the list, and not the beginning. The third commit fixes a minor issue where we don't want to re-arrange the linked list c->btree_cache, which is what the second commit ended up doing, and instead, just shrink the cache at the end of the linked list, and not change the order. One minor backport / context adjustment was required in the first commit for Bionic, and the rest are all clean cherry picks to Bionic and Focal. [Testcase] This is kind of hard to test, since the problem shows up in production environments that are under constant IO pressure, with many different items entering and leaving the cache. The Launchpad git server is currently suffering this issue, and has been sitting at a constant IO wait of 1 second / slightly over 1 second which was causing slow response times, which was leading to build failures when git clones ended up timing out. We installed a test kernel, which is available in the following PPA:
[Kernel-packages] [Bug 1898786] Re: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled
@mruffell, that's for Bionic, but for Focal is that still 5.4.0-56-generic? Or is there a new respun kernel to include these patches? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898786 Title: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1898786 [Impact] Systems that utilise bcache can experience extremely high IO wait times when under constant IO pressure. The IO wait times seem to stay at a consistent 1 second, and never drop as long as the bcache shrinker is enabled. If you disable the shrinker, then IO wait drops significantly to normal levels. We did some perf analysis, and it seems we spend a huge amount of time in bch_mca_scan(), likely waiting for the mutex ">bucket_lock". Looking at the recent commits in Bionic, we found the following commit merged in upstream 5.1-rc1 and backported to 4.15.0-87-generic through upstream stable: commit 9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b Author: Coly Li Date: Wed Nov 13 16:03:24 2019 +0800 Subject: bcache: at least try to shrink 1 node in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b It mentions in the description that: > If sc->nr_to_scan is smaller than c->btree_pages, after the above > calculation, variable 'nr' will be 0 and nothing will be shrunk. It is > frequeently observed that only 1 or 2 is set to sc->nr_to_scan and make > nr to be zero. Then bch_mca_scan() will do nothing more then acquiring > and releasing mutex c->bucket_lock. This seems to be what is going on here, but the above commit only addresses when nr is 0. From what I can see, the problems we are experiencing are when nr is 1 or 2, and again, we just waste time in bch_mca_scan() waiting on c->bucket_lock, only to release c->bucket_lock since the shrinker loop never executes since there is no work to do. [Fix] The following commits fix the problem, and all landed in 5.6-rc1: commit 125d98edd11464c8e0ec9eaaba7d682d0f832686 Author: Coly Li Date: Fri Jan 24 01:01:40 2020 +0800 Subject: bcache: remove member accessed from struct btree Link: https://github.com/torvalds/linux/commit/125d98edd11464c8e0ec9eaaba7d682d0f832686 commit d5c9c470b01177e4d90cdbf178b8c7f37f5b8795 Author: Coly Li Date: Fri Jan 24 01:01:41 2020 +0800 Subject: bcache: reap c->btree_cache_freeable from the tail in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/d5c9c470b01177e4d90cdbf178b8c7f37f5b8795 commit e3de04469a49ee09c89e80bf821508df458ccee6 Author: Coly Li Date: Fri Jan 24 01:01:42 2020 +0800 Subject: bcache: reap from tail of c->btree_cache in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/e3de04469a49ee09c89e80bf821508df458ccee6 The first commit is a dependency of the other two. The first commit removes a "recently accessed" marker, used to indicate if a particular cache has been used recently, and if it has been, not consider it for cache eviction. The commit mentions that under heavy IO, all caches will end up being recently accessed, and nothing will ever be shrunk. The second commit changes a previous design decision of skipping the first 3 caches to shrink, since it is a common case to call bch_mca_scan() with nr being 1, or 2, just like 0 was common in the very first commit I mentioned. This time, if we land on 1 or 2, the loop exits and nothing happens, and we waste time waiting on locks, just like the very first commit I mentioned. The fix is to try shrink caches from the tail of the list, and not the beginning. The third commit fixes a minor issue where we don't want to re-arrange the linked list c->btree_cache, which is what the second commit ended up doing, and instead, just shrink the cache at the end of the linked list, and not change the order. One minor backport / context adjustment was required in the first commit for Bionic, and the rest are all clean cherry picks to Bionic and Focal. [Testcase] This is kind of hard to test, since the problem shows up in production environments that are under constant IO pressure, with many different items entering and leaving the cache. The Launchpad git server is currently suffering this issue, and has been sitting at a constant IO wait of 1 second / slightly over 1 second which was causing slow response times, which was leading to build failures when git clones ended up timing out. We installed a test kernel, which is available in the following PPA: https://launchpad.net/~mruffell/+archive/ubuntu/sf294907-test Once the test
[Kernel-packages] [Bug 1898421] Re: Suspend - takes 30 seconds to fully suspend
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898421 Title: Suspend - takes 30 seconds to fully suspend Status in linux package in Ubuntu: Expired Bug description: Using `systemctl suspend` or suspending through the power menu takes 30 seconds for the system to fully suspend. Expected: The system suspends in under 2 seconds (e.g. check Arch Linux) Actual: The system takes 30 seconds to suspend (31.44 seconds using a stopwatch) Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal DMESG: [ 8521.093270] PM: suspend entry (deep) [ 8521.104938] Filesystems sync: 0.011 seconds [ 8521.182123] Freezing user space processes ... (elapsed 0.004 seconds) done. [ 8521.187004] OOM killer disabled. [ 8521.187005] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 8521.188754] printk: Suspending console(s) (use no_console_suspend to debug) [ 8521.219072] sd 1:0:0:0: [sda] Synchronizing SCSI cache [ 8521.219621] sd 1:0:0:0: [sda] Stopping disk [ 8521.958776] ACPI: Preparing to enter system sleep state S3 [ 8521.960793] PM: Saving platform NVS memory [ 8521.961025] Disabling non-boot CPUs ... [ 8521.961558] IRQ 26: no longer affine to CPU1 [ 8521.962593] smpboot: CPU 1 is now offline [ 8521.964649] IRQ 18: no longer affine to CPU2 [ 8521.965669] smpboot: CPU 2 is now offline [ 8521.967970] IRQ 27: no longer affine to CPU3 [ 8521.968991] smpboot: CPU 3 is now offline [ 8521.970958] ACPI: Low-level resume complete [ 8521.970958] PM: Restoring platform NVS memory [ 8521.976827] Enabling non-boot CPUs ... [ 8521.976893] x86: Booting SMP configuration: [ 8521.976894] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 8521.983510] CPU1 is up [ 8521.983545] smpboot: Booting Node 0 Processor 2 APIC 0x3 [ 8521.990199] CPU2 is up [ 8521.990234] smpboot: Booting Node 0 Processor 3 APIC 0x1 [ 8521.996937] CPU3 is up [ 8521.999566] ACPI: Waking up from system sleep state S3 [ 8522.039068] usb usb3: root hub lost power or was reset [ 8522.039085] usb usb4: root hub lost power or was reset [ 8522.039093] usb usb5: root hub lost power or was reset [ 8522.039149] usb usb6: root hub lost power or was reset [ 8522.039172] usb usb7: root hub lost power or was reset [ 8522.039207] usb usb8: root hub lost power or was reset [ 8522.046933] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 8522.053105] [drm] PCIE GART of 1024M enabled (table at 0x00162000). [ 8522.053201] radeon :01:00.0: WB enabled [ 8522.053204] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x2d5e699f [ 8522.053207] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x6b3686a1 [ 8522.053999] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 and cpu addr 0x556b4497 [ 8522.054407] sd 1:0:0:0: [sda] Starting disk [ 8522.070310] [drm] ring test on 0 succeeded in 2 usecs [ 8522.070320] [drm] ring test on 3 succeeded in 6 usecs [ 8522.139382] mt7601u 1-5:1.0: Error: MCU response pre-completed! [ 8522.167009] mt7601u 1-5:1.0: EEPROM ver:0c fae:00 [ 8522.246061] [drm] ring test on 5 succeeded in 2 usecs [ 8522.246069] [drm] UVD initialized successfully. [ 8522.246206] [drm] ib test on ring 0 succeeded in 0 usecs [ 8522.246333] [drm] ib test on ring 3 succeeded in 0 usecs [ 8522.372750] ata1: SATA link down (SStatus 0 SControl 300) [ 8522.420793] ata4: SATA link down (SStatus 0 SControl 300) [ 8522.420965] ata5: SATA link down (SStatus 0 SControl 300) [ 8522.420984] ata6: SATA link down (SStatus 0 SControl 300) [ 8522.421015] ata3: SATA link down (SStatus 0 SControl 300) [ 8522.534422] usb 4-2: reset low-speed USB device number 3 using uhci_hcd [ 8522.586417] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 8522.589674] ata2.00: configured for UDMA/133 [ 8522.589762] ata2.00: Enabling discard_zeroes_data [ 8522.910492] [drm] ib test on ring 5 succeeded [ 8523.114411] usb 4-1: reset low-speed USB device number 2 using uhci_hcd [ 8523.467722] OOM killer enabled. [ 8523.467723] Restarting tasks ... [ 8523.469565] pci :00:1e.0: PCI bridge to [bus 03] [ 8523.469623] pci :00:1e.0: PCI bridge to [bus 03] [ 8523.469671] pci :00:1e.0: PCI bridge to [bus 03] [ 8523.469723] pci :00:1e.0: PCI bridge to [bus 03] [ 8523.469769] pci :00:1e.0: PCI bridge to [bus 03] [ 8523.469816] pci :00:1e.0: PCI bridge to [bus 03] [ 8523.486043] rfkill: input handler enabled [ 8523.494520] done. [ 8523.496289] PM: suspend exit [ 8523.511552] rfkill: input
[Kernel-packages] [Bug 1899766] Re: Xorg freeze after selecting large cursor
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1899766 Title: Xorg freeze after selecting large cursor Status in nvidia-graphics-drivers-435 package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: After selecting the largest cursor in accessibility settings, the whole system froze. I had to use Magic SysRq to reboot the system. After reboot, the login screen was OK but after logging in it would immediately freeze again. Workaround: from login screen, switch to a VT with Ctrl-F2, log in and run dconf reset /org/gnome/desktop/interface/cursor-size I was playing with the cursor size because I see different cursor sizes in different apps and it was annoying me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:25:23 2020 DistUpgraded: 2020-05-02 16:08:06,720 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2018-12-11 (672 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-02 (164 days ago) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1899766/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899766] Re: Xorg freeze after selecting large cursor
[Expired for nvidia-graphics-drivers-435 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1899766 Title: Xorg freeze after selecting large cursor Status in nvidia-graphics-drivers-435 package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: After selecting the largest cursor in accessibility settings, the whole system froze. I had to use Magic SysRq to reboot the system. After reboot, the login screen was OK but after logging in it would immediately freeze again. Workaround: from login screen, switch to a VT with Ctrl-F2, log in and run dconf reset /org/gnome/desktop/interface/cursor-size I was playing with the cursor size because I see different cursor sizes in different apps and it was annoying me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:25:23 2020 DistUpgraded: 2020-05-02 16:08:06,720 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2018-12-11 (672 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-02 (164 days ago) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1899766/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899797] Re: dns does not resolve some names after updating kernel from 4.15.0-117 to a newer sub_version like -118 or -121
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899797 Title: dns does not resolve some names after updating kernel from 4.15.0-117 to a newer sub_version like -118 or -121 Status in linux package in Ubuntu: Expired Status in systemd package in Ubuntu: Invalid Bug description: This morning i've got a kernel update. After that I could not send mails using thunderbird contacting my mail provider kontent.com. The last working system was: Linux server 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I tried 4.15.0-118 and 4.15.0-121 but using these I could not resolve: smtp.kontent.com - but I could resolve www.google.de. So it seems that using the newer kernels 118 and 121 I can not resolve some but not all addresses. I returned to kernel 4.15.0-117 and everything works fine again. systemd-resolve --status Global DNS Servers: 172.30.30.1<--- this is an local router next to my "server" DNS Domain: ami.intranet DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (enp0s25) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.30.30.1 DNS Domain: ~. ami.intranet andreas@server:~$ host smtp.kontent.com smtp.kontent.com has address 81.88.40.61 doning the same with a newer kernel results in a "SERVERFAIL 2 error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902848] Re: Support Intel AX210 wifi [8086:2725] Subsystem [8086:4020]
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ To support next generation of Intel AX210 WiFi family. PCI ID
+ [8086:2725] Subsystem [8086:4020] specifically.
+
+ So far only patchset
+ https://lore.kernel.org/linux-wireless/20201202124151.55050-1-l...@coelho.fi
+ is required on v5.10-rc6, and itself is also in mainline kernel for
+ v5.10-rc7 at this moment. To enable this card with oem-5.10 kernel in
+ Focal, firmware blob is also required and hence SRU sent.
+
+ [Fix]
+
+ Firmware iwlwifi-ty-a0-gf-a0-59.ucode from commit 4f41e9d6437d ("iwlwifi:
+ update and add new FWs from core56-54 release").
+
+ [Test Case]
+
+ 1. Boot with kernel from mainline tip or v5.10-rc7 or newer.
+ 2. Check with `sudo dmesg | grep iwlwifi`.
+
+ [Where problems could occur]
+
+ New device firmware for initial AX210 hardware support. As this is the
+ first revision of the firmware for bringing up corresponding iwlwifi
+ device in system, it may also introduce new issues that breaks existing
+ user experience. However, without corresponding firmware, the Wi-Fi
+ function would be completely unusable, so the risk should be justified.
+
+ == Original Bug Description ==
+
Firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware
/linux-firmware.git/commit/iwlwifi-
ty-a0-gf-a0-59.ucode?id=4f41e9d6437d03e7ce9279076107dd08f46656f3, which
is already in mainline master.
Kernel: https://lore.kernel.org/linux-
wireless/iwlwifi.20201202143859.a06ba7540449.I7390305d088a49c1043c9b489154fe057989c18f@changeid/T/#u,
which will be included in v5.10-rc7 or newer.
04:00.0 Network controller [0280]: Intel Corporation Device [8086:2725] (rev
1a)
Subsystem: Intel Corporation Device [8086:0020]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR-
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
Bluetooth part in bug 1890130.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0',
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer']
failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read
kernel buffer failed: Operation not permitted
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-10-13 (22 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 100: ID 8087:0032 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Intel Corporation Rocket Lake Client Platform
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1-generic
root=UUID=221267f2-0315-4b8c-98c3-6e791d5615fc ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.10.0-1.2-generic 5.10.0-rc2
RelatedPackageVersions:
linux-restricted-modules-5.10.0-1-generic N/A
linux-backports-modules-5.10.0-1-generic N/A
linux-firmware1.190
RfKill:
Tags: focal
Uname: Linux 5.10.0-1-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: False
acpidump:
Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon:
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
Error executing command as another user: Not authorized
This incident has been reported.
dmi.bios.date: 08/20/2020
dmi.bios.vendor: Intel Corporation
dmi.bios.version: RKLSFWI1.R00.1344.A00.2008202030
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: RocketLake S UDIMM 6L RVP
dmi.board.vendor: Intel Corporation
dmi.board.version: 1
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 0.1
dmi.ec.firmware.release: 1.4
dmi.modalias:
dmi:bvnIntelCorporation:bvrRKLSFWI1.R00.1344.A00.2008202030:bd08/20/2020:efr1.4:svnIntelCorporation:pnRocketLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnRocketLakeSUDIMM6LRVP:rvr1:cvnIntelCorporation:ct3:cvr0.1:
dmi.product.family: Rocket Lake Client System
dmi.product.name: Rocket Lake Client Platform
dmi.product.sku: 0025
dmi.product.version: 0.1
dmi.sys.vendor: Intel Corporation
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
[Kernel-packages] [Bug 1906101] Re: no sound via speakers or headphone port on Carbon X1 6th
Can you please attach dmesg without any parameter/workaround? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1906101 Title: no sound via speakers or headphone port on Carbon X1 6th Status in alsa-lib package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I recently upgraded from 18.04 to 20.04. The sound worked without problems before upgrade, but now I don'get any sound at all from the speakers or the headphone jack. This seems similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 (although that bug is reported as resolved). I tried adding model=generic dmic_detect=0 to my alsa-base.conf, as reported in that ticket, but it did not help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.8 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Nov 28 18:36:36 2020 InstallationDate: Installed on 2018-07-27 (855 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-11-24 (4 days ago) dmi.bios.date: 10/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET75W (1.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET75W(1.50):bd10/13/2020:svnLENOVO:pn20KGCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGCTO1WW dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: misha 2223 F pulseaudio /dev/snd/pcmC0D0p: misha 2223 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 HibernationDevice: resume=UUID=85cedc6b-f3ef-4152-a471-35fa0ee621a1 InstallationDate: Installed on 2018-07-27 (859 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KGCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=7d9c3e7d-d2d0-45a2-a598-2ee37d17a0fa ro resume=UUID=85cedc6b-f3ef-4152-a471-35fa0ee621a1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-11-24 (7 days ago) UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET75W (1.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET75W(1.50):bd10/13/2020:svnLENOVO:pn20KGCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGCTO1WW dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1906101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908175] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908175 Title: Touchpad and Keyboard Status in linux package in Ubuntu: Confirmed Bug description: Built in touchpad and keyboard on laptop do not work on Ubuntu. Installed Ubuntu on USB. Opened Ubuntu and touchpad and keyboard were not responsive. External mouse and keyboard work fine, but want to use built in touchpad/keyboard. Computer is a Microsoft Surface Laptop with Windows 10. Attempting to install latest Ubuntu. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu11446 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 03:27:16 2020 LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Microsoft Corporation Surface Laptop 3 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=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2020 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 7.124.140 dmi.board.name: Surface Laptop 3 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr7.124.140:bd06/23/2020:svnMicrosoftCorporation:pnSurfaceLaptop3:pvr124I00036T000M030D0B07F1C05P48S01E0Y0K0U02:rvnMicrosoftCorporation:rnSurfaceLaptop3:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Laptop 3 dmi.product.sku: Surface_Laptop_3_1867:1868 dmi.product.version: 124I:00036T:000M:030D:0B:07F:1C:05P:48S:01E:0Y:0K:0U:02 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908175/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908175] [NEW] Touchpad and Keyboard
Public bug reported: Built in touchpad and keyboard on laptop do not work on Ubuntu. Installed Ubuntu on USB. Opened Ubuntu and touchpad and keyboard were not responsive. External mouse and keyboard work fine, but want to use built in touchpad/keyboard. Computer is a Microsoft Surface Laptop with Windows 10. Attempting to install latest Ubuntu. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu11446 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 03:27:16 2020 LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Microsoft Corporation Surface Laptop 3 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=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2020 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 7.124.140 dmi.board.name: Surface Laptop 3 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr7.124.140:bd06/23/2020:svnMicrosoftCorporation:pnSurfaceLaptop3:pvr124I00036T000M030D0B07F1C05P48S01E0Y0K0U02:rvnMicrosoftCorporation:rnSurfaceLaptop3:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Laptop 3 dmi.product.sku: Surface_Laptop_3_1867:1868 dmi.product.version: 124I:00036T:000M:030D:0B:07F:1C:05P:48S:01E:0Y:0K:0U:02 dmi.sys.vendor: Microsoft Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908175 Title: Touchpad and Keyboard Status in linux package in Ubuntu: New Bug description: Built in touchpad and keyboard on laptop do not work on Ubuntu. Installed Ubuntu on USB. Opened Ubuntu and touchpad and keyboard were not responsive. External mouse and keyboard work fine, but want to use built in touchpad/keyboard. Computer is a Microsoft Surface Laptop with Windows 10. Attempting to install latest Ubuntu. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu11446 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 03:27:16 2020 LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Microsoft Corporation Surface Laptop 3 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=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2020 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 7.124.140 dmi.board.name: Surface Laptop 3 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr7.124.140:bd06/23/2020:svnMicrosoftCorporation:pnSurfaceLaptop3:pvr124I00036T000M030D0B07F1C05P48S01E0Y0K0U02:rvnMicrosoftCorporation:rnSurfaceLaptop3:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Laptop 3 dmi.product.sku: Surface_Laptop_3_1867:1868 dmi.product.version: 124I:00036T:000M:030D:0B:07F:1C:05P:48S:01E:0Y:0K:0U:02 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908175/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1907886] Re: avinfo is missing
** Changed in: bluez (Ubuntu) Status: New => Triaged ** Changed in: bluez (Ubuntu) Importance: Undecided => Low ** Tags added: focal groovy ** Tags removed: groovy ** Tags added: hirsute -- 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/1907886 Title: avinfo is missing Status in bluez package in Ubuntu: Triaged Bug description: The "avinfo" command line tools available in bluez/tools (https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/tools) is not available in the package. The package bluez-tools (https://packages.ubuntu.com/groovy/bluez- tools) seems to map another project external to bluez (https://github.com/khvzak/bluez-tools) and not the "tools" folder of bluez. "avinfo" is used for example in order to check which codecs are supported by a headphone set (see https://github.com/EHfive /pulseaudio-modules-bt/issues/31#issuecomment-462717049). Maybe have "bluez-tools" map the "tools" folder of bluez, and move the other project to another package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1907886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907870] Re: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9
Also, while the monitor is plugged in please run: xrandr --verbose > xrandrv.txt and attach the resulting text file here. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907870 Title: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via HDMI, the screen is detected (i can see it in display settings) but the external monitor remains black. Seams like a bad frequency or resolution. I tried adding a new mode to xrandr with no luck. Also i tried different versions of kernels from 5.4 to 5.9. I am using Ubuntu 20.10 This is my lspci 0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:14.5 SD Host controller: Intel Corporation Device 02f5 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) inxi -Gx output: Graphics: Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 1-2:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.1 direct render: Yes xrandr output (with hdmi cable connected to external monitor): Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.06*+ 40.04 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 50.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00
[Kernel-packages] [Bug 1907870] Re: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9
Please also run: grep . /sys/class/drm/*/modes > drmmodes.txt and attach the resulting text file here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907870 Title: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via HDMI, the screen is detected (i can see it in display settings) but the external monitor remains black. Seams like a bad frequency or resolution. I tried adding a new mode to xrandr with no luck. Also i tried different versions of kernels from 5.4 to 5.9. I am using Ubuntu 20.10 This is my lspci 0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:14.5 SD Host controller: Intel Corporation Device 02f5 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) inxi -Gx output: Graphics: Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 1-2:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.1 direct render: Yes xrandr output (with hdmi cable connected to external monitor): Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.06*+ 40.04 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 50.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.8166.6760.0059.94 720x400 70.08 DP-1 disconnected (normal left
[Kernel-packages] [Bug 1907870] Re: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9
Please try selecting 'Ubuntu on Wayland' from the login screen, before you enter your password. ** Also affects: xorg-server (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/1907870 Title: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via HDMI, the screen is detected (i can see it in display settings) but the external monitor remains black. Seams like a bad frequency or resolution. I tried adding a new mode to xrandr with no luck. Also i tried different versions of kernels from 5.4 to 5.9. I am using Ubuntu 20.10 This is my lspci 0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:14.5 SD Host controller: Intel Corporation Device 02f5 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) inxi -Gx output: Graphics: Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 1-2:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.1 direct render: Yes xrandr output (with hdmi cable connected to external monitor): Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.06*+ 40.04 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 50.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.8166.67
[Kernel-packages] [Bug 1833855] Re: i915: EDID not detected on VGA resulting in low resolution 1024x768
The instructions in comment #16 don't require making a bootable disk or 20.10. You just install those packages in your 20.04 system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833855 Title: i915: EDID not detected on VGA resulting in low resolution 1024x768 Status in linux package in Ubuntu: Incomplete Bug description: hi! some problem. i have an video intel graphic card Q965 but i dont have any hi-resolution like 1080. i'm in vga mode only. Can you help me? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 23 09:58:42 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82Q963/Q965 Integrated Graphics Controller [8086:2992] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell 82Q963/Q965 Integrated Graphics Controller [1028:01da] Subsystem: Dell 82Q963/Q965 Integrated Graphics Controller [1028:01da] InstallationDate: Installed on 2019-06-18 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. OptiPlex 745 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=017d360b-c7a7-47e3-8d37-669b93a45647 ro quiet splash video=hyperv_fb:1280x720 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/01/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.4 dmi.board.name: 0GW726 dmi.board.vendor: Dell Inc. dmi.chassis.type: 16 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.4:bd03/01/2010:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0GW726:rvr:cvnDellInc.:ct16:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.98+git1906111830.5db0f7~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1906191930.9c19d0~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1906191930.9c19d0~oibaf~b version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907852] Re: package libnvidia-gl-455 (not installed) failed to install/upgrade: new libnvidia-gl-455:i386 package pre-installation script subprocess returned error exit status
Hello Sanjay, from your logs: diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux- gnu/libGL.so.1.distrib by nvidia-340 I don't know nvidia drivers well, but this looks a bit like an older driver is still installed while trying to install a new one. Does this sound familiar? Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1907852 Title: package libnvidia-gl-455 (not installed) failed to install/upgrade: new libnvidia-gl-455:i386 package pre-installation script subprocess returned error exit status 2 Status in nvidia-graphics-drivers-455 package in Ubuntu: New Bug description: STUCK WHILE BOOTING SYSTEM. CAN'T ABLE TO CHANGE THE PROPITIATORY DRIVER FOR NVIDIA GEFORCED GT 740 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-gl-455 (not installed) ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Dec 12 00:49:41 2020 ErrorMessage: new libnvidia-gl-455:i386 package pre-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2020-12-10 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-455 Title: package libnvidia-gl-455 (not installed) failed to install/upgrade: new libnvidia-gl-455:i386 package pre-installation script subprocess returned error exit status 2 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-455/+bug/1907852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907852] Re: package libnvidia-gl-455 (not installed) failed to install/upgrade: new libnvidia-gl-455:i386 package pre-installation script subprocess returned error exit status
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1907852 Title: package libnvidia-gl-455 (not installed) failed to install/upgrade: new libnvidia-gl-455:i386 package pre-installation script subprocess returned error exit status 2 Status in nvidia-graphics-drivers-455 package in Ubuntu: New Bug description: STUCK WHILE BOOTING SYSTEM. CAN'T ABLE TO CHANGE THE PROPITIATORY DRIVER FOR NVIDIA GEFORCED GT 740 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-gl-455 (not installed) ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Dec 12 00:49:41 2020 ErrorMessage: new libnvidia-gl-455:i386 package pre-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2020-12-10 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-455 Title: package libnvidia-gl-455 (not installed) failed to install/upgrade: new libnvidia-gl-455:i386 package pre-installation script subprocess returned error exit status 2 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-455/+bug/1907852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907852] Re: package libnvidia-gl-455 (not installed) failed to install/upgrade: new libnvidia-gl-455:i386 package pre-installation script subprocess returned error exit status
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1907852 Title: package libnvidia-gl-455 (not installed) failed to install/upgrade: new libnvidia-gl-455:i386 package pre-installation script subprocess returned error exit status 2 Status in nvidia-graphics-drivers-455 package in Ubuntu: New Bug description: STUCK WHILE BOOTING SYSTEM. CAN'T ABLE TO CHANGE THE PROPITIATORY DRIVER FOR NVIDIA GEFORCED GT 740 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-gl-455 (not installed) ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Dec 12 00:49:41 2020 ErrorMessage: new libnvidia-gl-455:i386 package pre-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2020-12-10 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-455 Title: package libnvidia-gl-455 (not installed) failed to install/upgrade: new libnvidia-gl-455:i386 package pre-installation script subprocess returned error exit status 2 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-455/+bug/1907852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904906] Comment bridged from LTC Bugzilla
--- Comment From daniel.axte...@ibm.com 2020-12-14 19:40 EDT--- Hi, Thanks for your patience. I tested 5.10.0-8-generic. /boot/config-5.10.0-8-generic contains: # CONFIG_RCU_SCALE_TEST is not set It boots fine in a P9 kvm guest, both when loaded by kexec and when loaded by grub. There is no secure-boot in these tests. Please let me know if you need anything else. Kind regards, Daniel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: Canonical requests to test the secure boot for the 5.10 kernel but kernel fails to boot with secure boot disabled. The 5.10 kernel can be found in: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap They can be installed by installing the linux-generic-wip package with this PPA enabled. As usual, they are only signed using a key specific to that PPA. This key can be retrieved from the signing tarballs for the kernels, e.g.: http://ppa.launchpad.net/canonical-kernel- team/bootstrap/ubuntu/dists/hirsute/main/signed/linux-5.10-ppc64el/5.10.0-2.3/signed.tar.gz Our tester installed the 5.10 kernel via aptitude. If booting directly from the bootmenu, it stucks at: "kexec_core: Starting new kernel" If booting recovery kernel for 5.10.0, it proceeds farther and after kexec_core, it failed at: " [0.029830] LSM: Security Framework initializing [0.029916] Yama: b " Two attempts with a different scenario; running with 5.8 kernel and boot via commandline for 5.10: kexec -l /boot/vmlinux-5.10.0-0-generic --initrd=/boot/initrd.img-5.10.0-0-generic --append="root=UUID=49d000cb-dba2-4d70-809e-38f2b31d0f09 ro quiet splash" kexec -e Both attempts also failed while rebooting, once with the same error as the error from booting with bootmenu; the other failure occurred a lot earlier. Wondering what new CONFIGs and/or features for the 5.10 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908157] Re: package nvidia-dkms-455 455.45.01-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-455 package post-installation script subprocess returned error e
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1908157 Title: package nvidia-dkms-455 455.45.01-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-455 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-455 package in Ubuntu: New Bug description: updating nvidia drivers and it errored out ProblemType: Package DistroRelease: Ubuntu 20.10 Package: nvidia-dkms-455 455.45.01-0ubuntu0.20.10.1 Uname: Linux 5.9.12-050912-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Dec 14 18:53:42 2020 ErrorMessage: installed nvidia-dkms-455 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-11-08 (36 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: linux-image-unsigned-5.10.1-051001-generic linux-base linux-image-5.8.0-34-generic linux-base RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.1 SourcePackage: nvidia-graphics-drivers-455 Title: package nvidia-dkms-455 455.45.01-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-455 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1908157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908157] [NEW] package nvidia-dkms-455 455.45.01-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-455 package post-installation script subprocess returned error
Public bug reported: updating nvidia drivers and it errored out ProblemType: Package DistroRelease: Ubuntu 20.10 Package: nvidia-dkms-455 455.45.01-0ubuntu0.20.10.1 Uname: Linux 5.9.12-050912-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Dec 14 18:53:42 2020 ErrorMessage: installed nvidia-dkms-455 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-11-08 (36 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: linux-image-unsigned-5.10.1-051001-generic linux-base linux-image-5.8.0-34-generic linux-base RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.1 SourcePackage: nvidia-graphics-drivers-455 Title: package nvidia-dkms-455 455.45.01-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-455 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-455 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy package-from-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1908157 Title: package nvidia-dkms-455 455.45.01-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-455 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-455 package in Ubuntu: New Bug description: updating nvidia drivers and it errored out ProblemType: Package DistroRelease: Ubuntu 20.10 Package: nvidia-dkms-455 455.45.01-0ubuntu0.20.10.1 Uname: Linux 5.9.12-050912-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Dec 14 18:53:42 2020 ErrorMessage: installed nvidia-dkms-455 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-11-08 (36 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: linux-image-unsigned-5.10.1-051001-generic linux-base linux-image-5.8.0-34-generic linux-base RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.1 SourcePackage: nvidia-graphics-drivers-455 Title: package nvidia-dkms-455 455.45.01-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-455 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1908157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908148] Re: Proot Errors / Operation not permitted / kernel contains bug
*** This bug is a duplicate of bug 1908145 ***
https://bugs.launchpad.net/bugs/1908145
** This bug has been marked a duplicate of bug 1908145
Proot Errors / Operation not permitted / kernel contains bug
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1908148
Title:
Proot Errors / Operation not permitted / kernel contains bug
Status in linux package in Ubuntu:
Incomplete
Bug description:
WAS TRYING TO RUN: $ pkg install proot proot-distro tsu fakeroot parted
RESULTING: CHecking availability of current mirror: ok
Ign:1 https://grimler.se/termux-packages-24 stable InRelease
Ign:2 https://dl.binary.com/grimler/game-package-24 games InRelease
Hit:3 https://grimler.se/termux-packages-24 stable InRelease
Ign:4 https://dl.binary.com/grimler/science-packages-24 science InRelease
Get:6 https://dl.binary.com/grimler/game-packages-24 games Release [5344 B]
Hit:6 https://dl.binary.com/grimler/game-packages-24 games Release
Get:8 https://dl.binary.com/grimler/science-packages-24 science Release [6191
B]
Hit:8 https://dl.binary.com/grimler/science-packages-24 science Release
Reading package lists... Done
Building dependency tree
Reading state information... Done
27 packages can be upgraded. Run 'apt-list --upgradable' to see them.
Reading package lists... Done
Building dependency tree
Reading state information... Done
tsu is already the newest version (8.5.1-2).
The following additional packages will be installed:
libtalloc libuuid ncurses-utils
The following NEW packages will be installed:
fakeroot libtalloc libuuid ncurses-utils parted proot proot-distro
0 upgraded, 7 newly installed, 0 to remove and 27 not upgraded.
Need to get 464 kB of archives.
After this operation, 1827 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://grimler.se/termux-packages-24 stable/main x86_64 fakeroot
x86_64 1.25.3 [27.9 kB]
Get:2 https://grimler.se/termux-packages-24 stable/main x86_64 libtalloc
x86_64 2.3.1 [33.4 kB]
Get:3 https://grimler.se/termux-packages-24 stable/main x86_64 libuuid x86_64
1.0.3-4 [7096 B]
Get:4 https://grimler.se/termux-packages-24 stable/main x86_64 ncurses-utils
x86_64 6.2.20200725 [87.8 kB]
Get:5 https://grimler.se/termux-packages-24 stable/main x86_64 parted x86_64
3.2-5 [203 kB]
Get:6 https://grimler.se/termux-packages-24 stable/main x86_64 proot x86_64
5.1.107-35 [89.4 kB]
Get:7 https://grimler.se/termux-packages-24 stable/main x86_64 prrot-distro
all 1.3.3 [15.2 kB]
Fetched 464 kB in 7s (63.6 kB/s)
Selecting previously unselected package fakeroot.
(Reading database... 11655 files and directories currently installed.)
Preparing to unpack .../0-fakeroot_1.25.3_x86%5f64.deb ...
Unpacking fakeroot (1.25.3) ...
Selecting previously unselected package libtalloc.
Preparing to unpack .../1-libtalloc_2.3.1_x86%5f64.deb ...
Unpacking libtalloc (2.3.1) ...
Selecting previously unselected package libuuid.
Preparing to unpack .../2-libuuid_1.0.3-4_x86%5f64.deb ...
Unpacking libuuid (1.0.3-4) ...
Selecting previously unselected package ncurses-utils.
Preparing to unpack .../3-ncurses-utils_6.2.20200725_x86%5f64.deb ...
Unpacking ncurses-utils (6.2.20200725) ...
Selecting previously unselected package parted.
Preparing to unpack .../4-parted_3.2-5_x86%5f64.deb ...
Unpacking parted (3.2-5) ...
Selecting previously unselected packaged proot.
Preparing to unpack .../5-proot_5.1.107-35_x86%5f64.deb ...
Unpacking proot (5.1.107-35) ...
Selecting previously unselected package proot-distro.
Preparing to unpack .../6-proot-distro_1.3.3_all.deb ...
Unpacking proot-distro (1.3.3) ...
Setting up libuuid (1.0.3-4) ...
Setting up parted (3.2-5) ...
Setting up ncurses-utils (6.2.20200725) ...
Setting up fakeroot (1.25.3) ...
Fakeroot does not give you any real root permissoins. This utility is
primarily intended to be used for development purposes. More info
about usage at https://wiki.debian.org/FakeRoot.
Programs requiring real root permissions will not run under fakeroot.
Do not post bug reports about this.
Setting up libtalloc (2.3.1) ...
Setting up proot (5.1.107-35) ...
Setting up proot-distro (1.3.3) ...
$ proot -0 login
proot error: ptrace(TRACEME): Operation not permitted
proot error: execve("/data/data/com.termux/files/usr/bin/login"): Operation
not permitted
proot info: It seems your kernel contains this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1202161
To workaround it, see the env. variable PROOT_NO_SECCOMP to 1.
fatal error: see 'proot --help'.ubu
$ ubuntu-bug linux
ubuntu-bug: command not found
$ cat /proc/version_signature > version.log
cat: /proc/version_signature: No such file or directory
$ sudo lspci -vnvn > lspci-vnvn.log
$ (no results gathered)
$lspci
[Kernel-packages] [Bug 1908150] Re: Groovy update: upstream stable patchset 2020-12-14
Per @colin-king, we're opting to omit the v5.9 backport of: db865272d9c4 cpufreq: Avoid configuring old governors as default with intel_pstate While we evaluate the impact of: 33aa46f252c7 cpufreq: intel_pstate: Use passive mode by default without HWP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908150 Title: Groovy update: upstream stable patchset 2020-12-14 Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-12-14 Ported from the following upstream stable releases: v5.4.75, v5.9.5 from git://git.kernel.org/ xen/events: avoid removing an event channel while handling it xen/events: add a proper barrier to 2-level uevent unmasking xen/events: fix race in evtchn_fifo_unmask() xen/events: add a new "late EOI" evtchn framework xen/blkback: use lateeoi irq binding xen/netback: use lateeoi irq binding xen/scsiback: use lateeoi irq binding xen/pvcallsback: use lateeoi irq binding xen/pciback: use lateeoi irq binding xen/events: switch user event channels to lateeoi model xen/events: use a common cpu hotplug hook for event channels xen/events: defer eoi in case of excessive number of events xen/events: block rogue events for some time firmware: arm_scmi: Fix ARCH_COLD_RESET firmware: arm_scmi: Expand SMC/HVC message pool to more than one tee: client UUID: Skip REE kernel login method as well firmware: arm_scmi: Add missing Rx size re-initialisation x86/unwind/orc: Fix inactive tasks with stack pointer in %sp on GCC 10 compiled kernels x86/alternative: Don't call text_poke() in lazy TLB mode ionic: no rx flush in deinit RDMA/mlx5: Fix devlink deadlock on net namespace deletion mlxsw: core: Fix use-after-free in mlxsw_emad_trans_finish() tracing, synthetic events: Replace buggy strcat() with seq_buf operations afs: Fix a use after free in afs_xattr_get_acl() afs: Fix afs_launder_page to not clear PG_writeback RDMA/qedr: Fix memory leak in iWARP CM ata: sata_nv: Fix retrieving of active qcs arm64: efi: increase EFI PE/COFF header padding to 64 KB afs: Fix to take ref on page when PG_private is set afs: Fix page leak on afs_write_begin() failure afs: Fix where page->private is set during write afs: Wrap page->private manipulations in inline functions afs: Alter dirty range encoding in page->private mm: add thp_order mm: add thp_size afs: Fix afs_invalidatepage to adjust the dirty region afs: Fix dirty-region encoding on ppc32 with 64K pages interconnect: qcom: sdm845: Enable keepalive for the MM1 BCM usb: host: ehci-tegra: Fix error handling in tegra_ehci_probe() futex: Fix incorrect should_fail_futex() handling powerpc/vmemmap: Fix memory leak with vmemmap list allocation failures. powerpc/powernv/smp: Fix spurious DBG() warning RDMA/core: Change how failing destroy is handled during uobj abort f2fs: allocate proper size memory for zstd decompress powerpc/watchpoint/ptrace: Fix SETHWDEBUG when CONFIG_HAVE_HW_BREAKPOINT=N UBUNTU: [Config] update config for ARCH_WANT_IRQS_OFF_ACTIVATE_MM mm: fix exec activate_mm vs TLB shootdown and lazy tlb switching race powerpc: select ARCH_WANT_IRQS_OFF_ACTIVATE_MM sparc64: remove mm_cpumask clearing to fix kthread_use_mm race f2fs: add trace exit in exception path f2fs: do sanity check on zoned block device path f2fs: fix uninit-value in f2fs_lookup f2fs: fix to check segment boundary during SIT page readahead s390/startup: avoid save_area_sync overflow f2fs: compress: fix to disallow enabling compress on non-empty file um: change sigio_spinlock to a mutex f2fs: handle errors of f2fs_get_meta_page_nofail afs: Don't assert on unpurgeable server records powerpc/64s: handle ISA v3.1 local copy-paste context switches ARM: 8997/2: hw_breakpoint: Handle inexact watchpoint addresses NFS4: Fix oops when copy_file_range is attempted with NFS4.0 source xfs: Set xfs_buf type flag when growing summary/bitmap files xfs: Set xfs_buf's b_ops member when zeroing bitmap/summary files xfs: log new intent items created as part of finishing recovered intent items power: supply: bq27xxx: report "not charging" on all types xfs: change the order in which child and parent defer ops are finished xfs: fix realtime bitmap/summary file
[Kernel-packages] [Bug 1904632] Re: Ubuntu 18.04 Azure VM host kernel panic
Hi Marcelo,
This issue can also been seen on the latest Ubuntu 18.04 image. It is also seen
in the 5.10-rc7 Linux kernel as well as 5.4.
The issue can be reproduced 100% of the time using a more simple setup as
described below. A basic "hello world" C program compiled for 32 bit crashes
the Azure Linux host if a standard VM is first started as described below using
qemu-kvm.
// the Azure host kernel panic reproduction with 32 bit hello world. Includes
the kernel panic traceback at the end.
// Install a standard ubuntu image on the host like below (if the 11/25/20 is
no longer available, the current one will do).
root@jnpronevm1:~# wget
https://cloud-images.ubuntu.com/bionic/20201125/bionic-server-cloudimg-amd64.img
--2020-11-30 19:43:20--
https://cloud-images.ubuntu.com/bionic/20201125/bionic-server-cloudimg-amd64.img
Resolving cloud-images.ubuntu.com (cloud-images.ubuntu.com)... 91.189.88.247,
91.189.88.248, 2001:67c:1360:8001::33, ...
Connecting to cloud-images.ubuntu.com
(cloud-images.ubuntu.com)|91.189.88.247|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 360775680 (344M) [application/octet-stream]
Saving to: ‘bionic-server-cloudimg-amd64.img.1’
bionic-server-cloudim 100%[==>] 344.06M 20.4MB/s
in 18s
2020-11-30 19:43:39 (19.2 MB/s) - ‘bionic-server-cloudimg-amd64.img.1’
saved [360775680/360775680]
// make sure qemu-kvm is installed and kvm acceleration can be used.
root@jnpronevm1:~#
root@jnpronevm1:~# kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used
root@jnpronevm1:~# cat hello.c
#include
int main()
{
printf("Hello world\n");
}
// compile about in 32 bit mode, 64 bit does not show the issue
root@jnpronevm1:~# gcc -m32 hello.c -o hello
// start the VM from the above downloaded image.
root@jnpronevm1:~#/usr/bin/qemu-system-x86_64 -daemonize -name u1 -machine
pc-i440fx-bionic,accel=kvm -m 1024 -smp 2,sockets=1 -uuid
772495e6-8658-4306-ba5f-f59c15f42f69 -device
piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
file=bionic-server-cloudimg-amd64.img,if=none,id=drive-virtio-disk0,format=raw,cache=writeback
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-chardev
socket,id=charserial0,host=127.0.0.1,port=8601,telnet,server,nowait,logfile=/var/log/console.log
-vnc 127.0.0.1:0 -vga cirrus
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.8001H:ECX.svm [bit 2]
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.8001H:ECX.svm [bit 2]
root@jnpronevm1:~# ps aux | grep qemu
root 2966 45.6 0.1 1655976 41064 ? Sl 20:02 0:02
/usr/bin/qemu-system-x86_64 -daemonize -name u1 -machine
pc-i440fx-bionic,accel=kvm -m 1024 -smp 2,sockets=1 -uuid
772495e6-8658-4306-ba5f-f59c15f42f69 -device
piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
file=bionic-server-cloudimg-amd64.img,if=none,id=drive-virtio-disk0,format=raw,cache=writeback
-device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-chardev
socket,id=charserial0,host=127.0.0.1,port=8601,telnet,server,nowait,logfile=/var/log/console.log
-vnc 127.0.0.1:0 -vga cirrus
root 2979 0.0 0.0 14864 1064 pts/0 S+ 20:02 0:00 grep qemu
root@jnpronevm1:~# ./hello
The host VM hung up due to kernel panic after above step.
### the host vm hit kernel panic after running hello program.
[ 7858.522920] PANIC: double fault, error_code: 0x0
[ 7858.525679] Kernel panic - not syncing: Machine halted.
[ 7858.525679] CPU: 5 PID: 4746 Comm: hello Not tainted 4.15.18+test #1
[ 7858.525679] Hardware name: Microsoft Corporation Virtual Machine/Virtual
Machine, BIOS 090008 12/07/2018
[ 7858.525679] Call Trace:
[ 7858.525679] <#DF>
[ 7858.525679] dump_stack+0x63/0x8b
[ 7858.525679] panic+0xe4/0x244
[ 7858.525679] df_debug+0x2d/0x30
[ 7858.525679] do_double_fault+0x9a/0x130
[ 7858.525679] double_fault+0x1e/0x30
[ 7858.525679] RIP: 0010:0x1a80
[ 7858.525679] RSP: 0018:e200 EFLAGS: 00010086
[ 7858.525679] RAX: 00c5 RBX: 0001 RCX: ffc98f2c
[ 7858.525679] RDX: 07d4 RSI: f7ef2d80 RDI: f7ef2000
[ 7858.525679] RBP: ffc98ed8 R08: R09:
[ 7858.525679] R10: R11: R12:
[ 7858.525679] R13: R14: R15:
[ 7858.525679]
[ 7858.525679] Kernel Offset: 0xf00 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 7858.525679] ---[ end Kernel panic - not syncing: Machine halted.
[ 7858.525679] WARNING: CPU: 5 PID: 4746 at kernel/sched/core.c:1192
set_task_cpu+0x162/0x170
[ 7858.525679] Modules linked in: xt_owner iptable_security
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype xt_CHECKSUM
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4
[Kernel-packages] [Bug 1908150] Re: Groovy update: upstream stable patchset 2020-12-14
** Description changed: - - SRU Justification - - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: - -upstream stable patchset 2020-12-14 -from git://git.kernel.org/ + SRU Justification + + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: + + upstream stable patchset 2020-12-14 + + Ported from the following upstream stable releases: + v5.4.75, v5.9.5 + + from git://git.kernel.org/ + + xen/events: avoid removing an event channel while handling it + xen/events: add a proper barrier to 2-level uevent unmasking + xen/events: fix race in evtchn_fifo_unmask() + xen/events: add a new "late EOI" evtchn framework + xen/blkback: use lateeoi irq binding + xen/netback: use lateeoi irq binding + xen/scsiback: use lateeoi irq binding + xen/pvcallsback: use lateeoi irq binding + xen/pciback: use lateeoi irq binding + xen/events: switch user event channels to lateeoi model + xen/events: use a common cpu hotplug hook for event channels + xen/events: defer eoi in case of excessive number of events + xen/events: block rogue events for some time + firmware: arm_scmi: Fix ARCH_COLD_RESET + firmware: arm_scmi: Expand SMC/HVC message pool to more than one + tee: client UUID: Skip REE kernel login method as well + firmware: arm_scmi: Add missing Rx size re-initialisation + x86/unwind/orc: Fix inactive tasks with stack pointer in %sp on GCC 10 compiled kernels + x86/alternative: Don't call text_poke() in lazy TLB mode + ionic: no rx flush in deinit + RDMA/mlx5: Fix devlink deadlock on net namespace deletion + mlxsw: core: Fix use-after-free in mlxsw_emad_trans_finish() + tracing, synthetic events: Replace buggy strcat() with seq_buf operations + afs: Fix a use after free in afs_xattr_get_acl() + afs: Fix afs_launder_page to not clear PG_writeback + RDMA/qedr: Fix memory leak in iWARP CM + ata: sata_nv: Fix retrieving of active qcs + arm64: efi: increase EFI PE/COFF header padding to 64 KB + afs: Fix to take ref on page when PG_private is set + afs: Fix page leak on afs_write_begin() failure + afs: Fix where page->private is set during write + afs: Wrap page->private manipulations in inline functions + afs: Alter dirty range encoding in page->private + mm: add thp_order + mm: add thp_size + afs: Fix afs_invalidatepage to adjust the dirty region + afs: Fix dirty-region encoding on ppc32 with 64K pages + interconnect: qcom: sdm845: Enable keepalive for the MM1 BCM + usb: host: ehci-tegra: Fix error handling in tegra_ehci_probe() + futex: Fix incorrect should_fail_futex() handling + powerpc/vmemmap: Fix memory leak with vmemmap list allocation failures. + powerpc/powernv/smp: Fix spurious DBG() warning + RDMA/core: Change how failing destroy is handled during uobj abort + f2fs: allocate proper size memory for zstd decompress + powerpc/watchpoint/ptrace: Fix SETHWDEBUG when CONFIG_HAVE_HW_BREAKPOINT=N + UBUNTU: [Config] update config for ARCH_WANT_IRQS_OFF_ACTIVATE_MM + mm: fix exec activate_mm vs TLB shootdown and lazy tlb switching race + powerpc: select ARCH_WANT_IRQS_OFF_ACTIVATE_MM + sparc64: remove mm_cpumask clearing to fix kthread_use_mm race + f2fs: add trace exit in exception path + f2fs: do sanity check on zoned block device path + f2fs: fix uninit-value in f2fs_lookup + f2fs: fix to check segment boundary during SIT page readahead + s390/startup: avoid save_area_sync overflow + f2fs: compress: fix to disallow enabling compress on non-empty file + um: change sigio_spinlock to a mutex + f2fs: handle errors of f2fs_get_meta_page_nofail + afs: Don't assert on unpurgeable server records + powerpc/64s: handle ISA v3.1 local copy-paste context switches + ARM: 8997/2: hw_breakpoint: Handle inexact watchpoint addresses + NFS4: Fix oops when copy_file_range is attempted with NFS4.0 source + xfs: Set xfs_buf type flag when growing summary/bitmap files + xfs: Set xfs_buf's b_ops member when zeroing bitmap/summary files + xfs: log new intent items created as part of finishing recovered intent items + power: supply: bq27xxx: report "not charging" on all types + xfs: change the order in which child and parent defer ops are finished + xfs: fix realtime bitmap/summary file truncation when
[Kernel-packages] [Bug 1908150] [NEW] Groovy update: upstream stable patchset 2020-12-14
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-12-14 Ported from the following upstream stable releases: v5.4.75, v5.9.5 from git://git.kernel.org/ xen/events: avoid removing an event channel while handling it xen/events: add a proper barrier to 2-level uevent unmasking xen/events: fix race in evtchn_fifo_unmask() xen/events: add a new "late EOI" evtchn framework xen/blkback: use lateeoi irq binding xen/netback: use lateeoi irq binding xen/scsiback: use lateeoi irq binding xen/pvcallsback: use lateeoi irq binding xen/pciback: use lateeoi irq binding xen/events: switch user event channels to lateeoi model xen/events: use a common cpu hotplug hook for event channels xen/events: defer eoi in case of excessive number of events xen/events: block rogue events for some time firmware: arm_scmi: Fix ARCH_COLD_RESET firmware: arm_scmi: Expand SMC/HVC message pool to more than one tee: client UUID: Skip REE kernel login method as well firmware: arm_scmi: Add missing Rx size re-initialisation x86/unwind/orc: Fix inactive tasks with stack pointer in %sp on GCC 10 compiled kernels x86/alternative: Don't call text_poke() in lazy TLB mode ionic: no rx flush in deinit RDMA/mlx5: Fix devlink deadlock on net namespace deletion mlxsw: core: Fix use-after-free in mlxsw_emad_trans_finish() tracing, synthetic events: Replace buggy strcat() with seq_buf operations afs: Fix a use after free in afs_xattr_get_acl() afs: Fix afs_launder_page to not clear PG_writeback RDMA/qedr: Fix memory leak in iWARP CM ata: sata_nv: Fix retrieving of active qcs arm64: efi: increase EFI PE/COFF header padding to 64 KB afs: Fix to take ref on page when PG_private is set afs: Fix page leak on afs_write_begin() failure afs: Fix where page->private is set during write afs: Wrap page->private manipulations in inline functions afs: Alter dirty range encoding in page->private mm: add thp_order mm: add thp_size afs: Fix afs_invalidatepage to adjust the dirty region afs: Fix dirty-region encoding on ppc32 with 64K pages interconnect: qcom: sdm845: Enable keepalive for the MM1 BCM usb: host: ehci-tegra: Fix error handling in tegra_ehci_probe() futex: Fix incorrect should_fail_futex() handling powerpc/vmemmap: Fix memory leak with vmemmap list allocation failures. powerpc/powernv/smp: Fix spurious DBG() warning RDMA/core: Change how failing destroy is handled during uobj abort f2fs: allocate proper size memory for zstd decompress powerpc/watchpoint/ptrace: Fix SETHWDEBUG when CONFIG_HAVE_HW_BREAKPOINT=N UBUNTU: [Config] update config for ARCH_WANT_IRQS_OFF_ACTIVATE_MM mm: fix exec activate_mm vs TLB shootdown and lazy tlb switching race powerpc: select ARCH_WANT_IRQS_OFF_ACTIVATE_MM sparc64: remove mm_cpumask clearing to fix kthread_use_mm race f2fs: add trace exit in exception path f2fs: do sanity check on zoned block device path f2fs: fix uninit-value in f2fs_lookup f2fs: fix to check segment boundary during SIT page readahead s390/startup: avoid save_area_sync overflow f2fs: compress: fix to disallow enabling compress on non-empty file um: change sigio_spinlock to a mutex f2fs: handle errors of f2fs_get_meta_page_nofail afs: Don't assert on unpurgeable server records powerpc/64s: handle ISA v3.1 local copy-paste context switches ARM: 8997/2: hw_breakpoint: Handle inexact watchpoint addresses NFS4: Fix oops when copy_file_range is attempted with NFS4.0 source xfs: Set xfs_buf type flag when growing summary/bitmap files xfs: Set xfs_buf's b_ops member when zeroing bitmap/summary files xfs: log new intent items created as part of finishing recovered intent items power: supply: bq27xxx: report "not charging" on all types xfs: change the order in which child and parent defer ops are finished xfs: fix realtime bitmap/summary file truncation when growing rt volume ath10k: fix retry packets update in station dump x86/kaslr: Initialize mem_limit to the real maximum address drm/ast: Separate DRM driver from PCI code drm/amdgpu: restore ras flags when user resets eeprom(v2) video: fbdev: pvr2fb: initialize variables ath10k: start recovery process when payload length exceeds max htc length for sdio ath10k: fix VHT NSS calculation when STBC is enabled drm/scheduler: Scheduler priority fixes (v2) drm/brige/megachips: Add checking if ge_b850v3_lvds_init() is working correctly ASOC: SOF: Intel: hda-codec: move unused label to correct position ASoC: SOF: fix a runtime pm issue in SOF when HDMI codec doesn't work selftests/x86/fsgsbase: Reap a forgotten child
[Kernel-packages] [Bug 1908148] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1908148
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1908148
Title:
Proot Errors / Operation not permitted / kernel contains bug
Status in linux package in Ubuntu:
Incomplete
Bug description:
WAS TRYING TO RUN: $ pkg install proot proot-distro tsu fakeroot parted
RESULTING: CHecking availability of current mirror: ok
Ign:1 https://grimler.se/termux-packages-24 stable InRelease
Ign:2 https://dl.binary.com/grimler/game-package-24 games InRelease
Hit:3 https://grimler.se/termux-packages-24 stable InRelease
Ign:4 https://dl.binary.com/grimler/science-packages-24 science InRelease
Get:6 https://dl.binary.com/grimler/game-packages-24 games Release [5344 B]
Hit:6 https://dl.binary.com/grimler/game-packages-24 games Release
Get:8 https://dl.binary.com/grimler/science-packages-24 science Release [6191
B]
Hit:8 https://dl.binary.com/grimler/science-packages-24 science Release
Reading package lists... Done
Building dependency tree
Reading state information... Done
27 packages can be upgraded. Run 'apt-list --upgradable' to see them.
Reading package lists... Done
Building dependency tree
Reading state information... Done
tsu is already the newest version (8.5.1-2).
The following additional packages will be installed:
libtalloc libuuid ncurses-utils
The following NEW packages will be installed:
fakeroot libtalloc libuuid ncurses-utils parted proot proot-distro
0 upgraded, 7 newly installed, 0 to remove and 27 not upgraded.
Need to get 464 kB of archives.
After this operation, 1827 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://grimler.se/termux-packages-24 stable/main x86_64 fakeroot
x86_64 1.25.3 [27.9 kB]
Get:2 https://grimler.se/termux-packages-24 stable/main x86_64 libtalloc
x86_64 2.3.1 [33.4 kB]
Get:3 https://grimler.se/termux-packages-24 stable/main x86_64 libuuid x86_64
1.0.3-4 [7096 B]
Get:4 https://grimler.se/termux-packages-24 stable/main x86_64 ncurses-utils
x86_64 6.2.20200725 [87.8 kB]
Get:5 https://grimler.se/termux-packages-24 stable/main x86_64 parted x86_64
3.2-5 [203 kB]
Get:6 https://grimler.se/termux-packages-24 stable/main x86_64 proot x86_64
5.1.107-35 [89.4 kB]
Get:7 https://grimler.se/termux-packages-24 stable/main x86_64 prrot-distro
all 1.3.3 [15.2 kB]
Fetched 464 kB in 7s (63.6 kB/s)
Selecting previously unselected package fakeroot.
(Reading database... 11655 files and directories currently installed.)
Preparing to unpack .../0-fakeroot_1.25.3_x86%5f64.deb ...
Unpacking fakeroot (1.25.3) ...
Selecting previously unselected package libtalloc.
Preparing to unpack .../1-libtalloc_2.3.1_x86%5f64.deb ...
Unpacking libtalloc (2.3.1) ...
Selecting previously unselected package libuuid.
Preparing to unpack .../2-libuuid_1.0.3-4_x86%5f64.deb ...
Unpacking libuuid (1.0.3-4) ...
Selecting previously unselected package ncurses-utils.
Preparing to unpack .../3-ncurses-utils_6.2.20200725_x86%5f64.deb ...
Unpacking ncurses-utils (6.2.20200725) ...
Selecting previously unselected package parted.
Preparing to unpack .../4-parted_3.2-5_x86%5f64.deb ...
Unpacking parted (3.2-5) ...
Selecting previously unselected packaged proot.
Preparing to unpack .../5-proot_5.1.107-35_x86%5f64.deb ...
Unpacking proot (5.1.107-35) ...
Selecting previously unselected package proot-distro.
Preparing to unpack .../6-proot-distro_1.3.3_all.deb ...
Unpacking proot-distro (1.3.3) ...
Setting up libuuid (1.0.3-4) ...
Setting up parted (3.2-5) ...
Setting up ncurses-utils (6.2.20200725) ...
Setting up fakeroot (1.25.3) ...
Fakeroot does not give you any real root permissoins. This utility is
primarily intended to be used for development purposes. More info
about usage at https://wiki.debian.org/FakeRoot.
Programs requiring real root permissions will not run under fakeroot.
Do not post bug reports about this.
Setting up libtalloc (2.3.1) ...
Setting up proot (5.1.107-35) ...
Setting up proot-distro (1.3.3) ...
$ proot -0 login
proot error: ptrace(TRACEME): Operation not permitted
proot error: execve("/data/data/com.termux/files/usr/bin/login"): Operation
not permitted
proot info: It seems your kernel contains this bug:
[Kernel-packages] [Bug 1908148] [NEW] Proot Errors / Operation not permitted / kernel contains bug
Public bug reported:
WAS TRYING TO RUN: $ pkg install proot proot-distro tsu fakeroot parted
RESULTING: CHecking availability of current mirror: ok
Ign:1 https://grimler.se/termux-packages-24 stable InRelease
Ign:2 https://dl.binary.com/grimler/game-package-24 games InRelease
Hit:3 https://grimler.se/termux-packages-24 stable InRelease
Ign:4 https://dl.binary.com/grimler/science-packages-24 science InRelease
Get:6 https://dl.binary.com/grimler/game-packages-24 games Release [5344 B]
Hit:6 https://dl.binary.com/grimler/game-packages-24 games Release
Get:8 https://dl.binary.com/grimler/science-packages-24 science Release [6191 B]
Hit:8 https://dl.binary.com/grimler/science-packages-24 science Release
Reading package lists... Done
Building dependency tree
Reading state information... Done
27 packages can be upgraded. Run 'apt-list --upgradable' to see them.
Reading package lists... Done
Building dependency tree
Reading state information... Done
tsu is already the newest version (8.5.1-2).
The following additional packages will be installed:
libtalloc libuuid ncurses-utils
The following NEW packages will be installed:
fakeroot libtalloc libuuid ncurses-utils parted proot proot-distro
0 upgraded, 7 newly installed, 0 to remove and 27 not upgraded.
Need to get 464 kB of archives.
After this operation, 1827 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://grimler.se/termux-packages-24 stable/main x86_64 fakeroot x86_64
1.25.3 [27.9 kB]
Get:2 https://grimler.se/termux-packages-24 stable/main x86_64 libtalloc x86_64
2.3.1 [33.4 kB]
Get:3 https://grimler.se/termux-packages-24 stable/main x86_64 libuuid x86_64
1.0.3-4 [7096 B]
Get:4 https://grimler.se/termux-packages-24 stable/main x86_64 ncurses-utils
x86_64 6.2.20200725 [87.8 kB]
Get:5 https://grimler.se/termux-packages-24 stable/main x86_64 parted x86_64
3.2-5 [203 kB]
Get:6 https://grimler.se/termux-packages-24 stable/main x86_64 proot x86_64
5.1.107-35 [89.4 kB]
Get:7 https://grimler.se/termux-packages-24 stable/main x86_64 prrot-distro all
1.3.3 [15.2 kB]
Fetched 464 kB in 7s (63.6 kB/s)
Selecting previously unselected package fakeroot.
(Reading database... 11655 files and directories currently installed.)
Preparing to unpack .../0-fakeroot_1.25.3_x86%5f64.deb ...
Unpacking fakeroot (1.25.3) ...
Selecting previously unselected package libtalloc.
Preparing to unpack .../1-libtalloc_2.3.1_x86%5f64.deb ...
Unpacking libtalloc (2.3.1) ...
Selecting previously unselected package libuuid.
Preparing to unpack .../2-libuuid_1.0.3-4_x86%5f64.deb ...
Unpacking libuuid (1.0.3-4) ...
Selecting previously unselected package ncurses-utils.
Preparing to unpack .../3-ncurses-utils_6.2.20200725_x86%5f64.deb ...
Unpacking ncurses-utils (6.2.20200725) ...
Selecting previously unselected package parted.
Preparing to unpack .../4-parted_3.2-5_x86%5f64.deb ...
Unpacking parted (3.2-5) ...
Selecting previously unselected packaged proot.
Preparing to unpack .../5-proot_5.1.107-35_x86%5f64.deb ...
Unpacking proot (5.1.107-35) ...
Selecting previously unselected package proot-distro.
Preparing to unpack .../6-proot-distro_1.3.3_all.deb ...
Unpacking proot-distro (1.3.3) ...
Setting up libuuid (1.0.3-4) ...
Setting up parted (3.2-5) ...
Setting up ncurses-utils (6.2.20200725) ...
Setting up fakeroot (1.25.3) ...
Fakeroot does not give you any real root permissoins. This utility is
primarily intended to be used for development purposes. More info about
usage at https://wiki.debian.org/FakeRoot.
Programs requiring real root permissions will not run under fakeroot. Do
not post bug reports about this.
Setting up libtalloc (2.3.1) ...
Setting up proot (5.1.107-35) ...
Setting up proot-distro (1.3.3) ...
$ proot -0 login
proot error: ptrace(TRACEME): Operation not permitted
proot error: execve("/data/data/com.termux/files/usr/bin/login"): Operation not
permitted
proot info: It seems your kernel contains this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1202161
To workaround it, see the env. variable PROOT_NO_SECCOMP to 1.
fatal error: see 'proot --help'.ubu
$ ubuntu-bug linux
ubuntu-bug: command not found
$ cat /proc/version_signature > version.log
cat: /proc/version_signature: No such file or directory
$ sudo lspci -vnvn > lspci-vnvn.log
$ (no results gathered)
$lspci -vnvn.log
lspci -vnvn.log: command not found
$ sudo lspci -vnvn
No superuser binary detected.
Are you rooted?
$ lsb_release -rd
No command lsb_release found, did you mean:
Command lrelease in package qt5-tools from the x11-repo repository
$ lrelease
The program lrelease is not installed. Install it by executnig:
pkg install qt5-tools, after running pkg in x11-repo
** 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/1908148
Title:
Proot Errors / Operation not
[Kernel-packages] [Bug 1908145] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1908145
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1908145
Title:
Proot Errors / Operation not permitted / kernel contains bug
Status in linux package in Ubuntu:
Incomplete
Bug description:
WAS TRYING TO RUN: $ pkg install proot proot-distro tsu fakeroot parted
RESULTING: CHecking availability of current mirror: ok
Ign:1 https://grimler.se/termux-packages-24 stable InRelease
Ign:2 https://dl.binary.com/grimler/game-package-24 games InRelease
Hit:3 https://grimler.se/termux-packages-24 stable InRelease
Ign:4 https://dl.binary.com/grimler/science-packages-24 science InRelease
Get:6 https://dl.binary.com/grimler/game-packages-24 games Release [5344 B]
Hit:6 https://dl.binary.com/grimler/game-packages-24 games Release
Get:8 https://dl.binary.com/grimler/science-packages-24 science Release [6191
B]
Hit:8 https://dl.binary.com/grimler/science-packages-24 science Release
Reading package lists... Done
Building dependency tree
Reading state information... Done
27 packages can be upgraded. Run 'apt-list --upgradable' to see them.
Reading package lists... Done
Building dependency tree
Reading state information... Done
tsu is already the newest version (8.5.1-2).
The following additional packages will be installed:
libtalloc libuuid ncurses-utils
The following NEW packages will be installed:
fakeroot libtalloc libuuid ncurses-utils parted proot proot-distro
0 upgraded, 7 newly installed, 0 to remove and 27 not upgraded.
Need to get 464 kB of archives.
After this operation, 1827 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://grimler.se/termux-packages-24 stable/main x86_64 fakeroot
x86_64 1.25.3 [27.9 kB]
Get:2 https://grimler.se/termux-packages-24 stable/main x86_64 libtalloc
x86_64 2.3.1 [33.4 kB]
Get:3 https://grimler.se/termux-packages-24 stable/main x86_64 libuuid x86_64
1.0.3-4 [7096 B]
Get:4 https://grimler.se/termux-packages-24 stable/main x86_64 ncurses-utils
x86_64 6.2.20200725 [87.8 kB]
Get:5 https://grimler.se/termux-packages-24 stable/main x86_64 parted x86_64
3.2-5 [203 kB]
Get:6 https://grimler.se/termux-packages-24 stable/main x86_64 proot x86_64
5.1.107-35 [89.4 kB]
Get:7 https://grimler.se/termux-packages-24 stable/main x86_64 prrot-distro
all 1.3.3 [15.2 kB]
Fetched 464 kB in 7s (63.6 kB/s)
Selecting previously unselected package fakeroot.
(Reading database... 11655 files and directories currently installed.)
Preparing to unpack .../0-fakeroot_1.25.3_x86%5f64.deb ...
Unpacking fakeroot (1.25.3) ...
Selecting previously unselected package libtalloc.
Preparing to unpack .../1-libtalloc_2.3.1_x86%5f64.deb ...
Unpacking libtalloc (2.3.1) ...
Selecting previously unselected package libuuid.
Preparing to unpack .../2-libuuid_1.0.3-4_x86%5f64.deb ...
Unpacking libuuid (1.0.3-4) ...
Selecting previously unselected package ncurses-utils.
Preparing to unpack .../3-ncurses-utils_6.2.20200725_x86%5f64.deb ...
Unpacking ncurses-utils (6.2.20200725) ...
Selecting previously unselected package parted.
Preparing to unpack .../4-parted_3.2-5_x86%5f64.deb ...
Unpacking parted (3.2-5) ...
Selecting previously unselected packaged proot.
Preparing to unpack .../5-proot_5.1.107-35_x86%5f64.deb ...
Unpacking proot (5.1.107-35) ...
Selecting previously unselected package proot-distro.
Preparing to unpack .../6-proot-distro_1.3.3_all.deb ...
Unpacking proot-distro (1.3.3) ...
Setting up libuuid (1.0.3-4) ...
Setting up parted (3.2-5) ...
Setting up ncurses-utils (6.2.20200725) ...
Setting up fakeroot (1.25.3) ...
Fakeroot does not give you any real root permissoins. This utility is
primarily intended to be used for development purposes. More info
about usage at https://wiki.debian.org/FakeRoot.
Programs requiring real root permissions will not run under fakeroot.
Do not post bug reports about this.
Setting up libtalloc (2.3.1) ...
Setting up proot (5.1.107-35) ...
Setting up proot-distro (1.3.3) ...
$ proot -0 login
proot error: ptrace(TRACEME): Operation not permitted
proot error: execve("/data/data/com.termux/files/usr/bin/login"): Operation
not permitted
proot info: It seems your kernel contains this bug:
[Kernel-packages] [Bug 1908139] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908139 Title: ThinkPad T14s external display not working on ThinkPad USB-C Dock Gen2 Status in linux package in Ubuntu: Confirmed Bug description: laptop: ThinkPad T14s Gen 1 - AMD Ryzen 7 PRO 4750U docking station: ThinkPad USB-C Dock 2. Gen. external display: NE MultiSync EA275UHD OS: Ubuntu 20.10 - kernel 5.8.0 Plugging the external display into one of the docking station's two DisplayPort connectors leads to the screen resolution changing on the laptop's builtin display and the external display waking up but showing no picture and displaying "no-signal" after a bit. Plugging the external display into the docking station's HDMI connector leads to no visible reaction on either the external nor the builtin display. Plugging the external display into the laptop's builtin HDMI connector works as expected. The external display is recognized and shows an image. I have recorded the output on `dmesg` during the steps mentioned above and inserted explanations using `echo MSG >/dev/kmsg`. The output follows at the end of the message. I believe `ubuntu-bug` should also attach the full log. All above modes of connection work as expected with the same laptop, dock, and display on Windows 10 (installed as dual boot along side Ubuntu). All above modes of connection also work as expected with an older laptop (ThinkPad T470s - Ubuntu 20.04 - kernel 5.4.0), and the same dock and display. This leads me to believe that this is not a hardware issue. The following bug seems related, but seems to have been observed on faulty hardware according to its author. Therefore, I decided to open a separate bug report. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899336 ``` [ 343.372511] plugging DisplayPort into dock port 1 [ 352.666113] [drm] DP Alt mode state on HPD: 1 [ 352.749192] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 75] [ 352.858482] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.888400] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.892555] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.896719] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.900876] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.905596] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.910323] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.914485] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 377.353566] plugged in - no signal [ 396.728970] unplugging [ 403.001418] [drm] DM_MST: stopping TM on aconnector: 2105a317 [id: 75] [ 415.576397] unplugged [ 431.500729] plugging DisplayPort into dock port 2 [ 437.607724] [drm] DP Alt mode state on HPD: 1 [ 437.681116] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 75] [ 437.790303] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.820138] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.824305] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.828462] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.832619] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.837029] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.841984] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.846144] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 458.999849] plugged in - no signal [ 465.702949] unplugging [ 476.127418] [drm] DM_MST: stopping TM on aconnector: 2105a317 [id: 75] [ 476.956491] [drm] Failed to add display topology, DTM TA is not initialized. [ 488.792533] unplugged [ 529.801179] plugging HDMI into dock [ 536.721076] [drm] DP Alt mode state on HPD: 1 [ 536.792947] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 75] [ 536.901958] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.906123] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.910288] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.914611] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.919568] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.923725] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.927888] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.932047] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.936451] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.941486] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.945651] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.949808] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 537.010093] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 271ba325 port 1: DPCD read on addr 0x60 for 1 bytes NAKed [ 592.844147] plugged in - display does not react [
[Kernel-packages] [Bug 1908144] Re: disable building bpf selftests
** Description changed:
Building tools/testing/selftests/bpf/ requires dependencies which cannot
be easily satisfied by our build process. The problem is well-described
by the pending upstream patch:
https://lore.kernel.org/bpf/20201210185233.28091-1-broo...@kernel.org/
From: Mark Brown
Subject: [PATCH] selftests: Skip BPF seftests by default
To effect the same for {groovy, hirsute} we must instead make a
debian/rules change via "UBUNTU: disable building bpf selftests (no
VMLINUX_BTF)".
But lets also pick up the upstream change above, as well as my related
"clarify" change, also pending upstream.
These three patches should be applied to {groovy, hirsute}:
- UBUNTU: SAUCE: selftests/bpf: clarify build error if no vmlinux
- UBUNTU: SAUCE: selftests: Skip BPF seftests by default
- UBUNTU: disable building bpf selftests (no VMLINUX_BTF)
+ UBUNTU: SAUCE: selftests/bpf: clarify build error if no vmlinux
+ UBUNTU: SAUCE: selftests: Skip BPF seftests by default
+ UBUNTU: disable building bpf selftests (no VMLINUX_BTF)
+
+ [Impact]
+
+ * No end-user effect; selftests are not packaged.
+ * Allows us to build-test upstream changes to selftests/.
+
+ [Test Case]
+
+ * fdr compileselftests
+
+ [Regression Potential]
+
+ * Low: disables building a subtree that has always to build in {g,h}.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1908144
Title:
disable building bpf selftests
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Groovy:
In Progress
Status in linux source package in Hirsute:
In Progress
Bug description:
Building tools/testing/selftests/bpf/ requires dependencies which
cannot be easily satisfied by our build process. The problem is well-
described by the pending upstream patch:
https://lore.kernel.org/bpf/20201210185233.28091-1-broo...@kernel.org/
From: Mark Brown
Subject: [PATCH] selftests: Skip BPF seftests by default
To effect the same for {groovy, hirsute} we must instead make a
debian/rules change via "UBUNTU: disable building bpf selftests (no
VMLINUX_BTF)".
But lets also pick up the upstream change above, as well as my related
"clarify" change, also pending upstream.
These three patches should be applied to {groovy, hirsute}:
UBUNTU: SAUCE: selftests/bpf: clarify build error if no vmlinux
UBUNTU: SAUCE: selftests: Skip BPF seftests by default
UBUNTU: disable building bpf selftests (no VMLINUX_BTF)
[Impact]
* No end-user effect; selftests are not packaged.
* Allows us to build-test upstream changes to selftests/.
[Test Case]
* fdr compileselftests
[Regression Potential]
* Low: disables building a subtree that has always to build in {g,h}.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908144/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908145] [NEW] Proot Errors / Operation not permitted / kernel contains bug
Public bug reported:
WAS TRYING TO RUN: $ pkg install proot proot-distro tsu fakeroot parted
RESULTING: CHecking availability of current mirror: ok
Ign:1 https://grimler.se/termux-packages-24 stable InRelease
Ign:2 https://dl.binary.com/grimler/game-package-24 games InRelease
Hit:3 https://grimler.se/termux-packages-24 stable InRelease
Ign:4 https://dl.binary.com/grimler/science-packages-24 science InRelease
Get:6 https://dl.binary.com/grimler/game-packages-24 games Release [5344 B]
Hit:6 https://dl.binary.com/grimler/game-packages-24 games Release
Get:8 https://dl.binary.com/grimler/science-packages-24 science Release [6191 B]
Hit:8 https://dl.binary.com/grimler/science-packages-24 science Release
Reading package lists... Done
Building dependency tree
Reading state information... Done
27 packages can be upgraded. Run 'apt-list --upgradable' to see them.
Reading package lists... Done
Building dependency tree
Reading state information... Done
tsu is already the newest version (8.5.1-2).
The following additional packages will be installed:
libtalloc libuuid ncurses-utils
The following NEW packages will be installed:
fakeroot libtalloc libuuid ncurses-utils parted proot proot-distro
0 upgraded, 7 newly installed, 0 to remove and 27 not upgraded.
Need to get 464 kB of archives.
After this operation, 1827 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://grimler.se/termux-packages-24 stable/main x86_64 fakeroot x86_64
1.25.3 [27.9 kB]
Get:2 https://grimler.se/termux-packages-24 stable/main x86_64 libtalloc x86_64
2.3.1 [33.4 kB]
Get:3 https://grimler.se/termux-packages-24 stable/main x86_64 libuuid x86_64
1.0.3-4 [7096 B]
Get:4 https://grimler.se/termux-packages-24 stable/main x86_64 ncurses-utils
x86_64 6.2.20200725 [87.8 kB]
Get:5 https://grimler.se/termux-packages-24 stable/main x86_64 parted x86_64
3.2-5 [203 kB]
Get:6 https://grimler.se/termux-packages-24 stable/main x86_64 proot x86_64
5.1.107-35 [89.4 kB]
Get:7 https://grimler.se/termux-packages-24 stable/main x86_64 prrot-distro all
1.3.3 [15.2 kB]
Fetched 464 kB in 7s (63.6 kB/s)
Selecting previously unselected package fakeroot.
(Reading database... 11655 files and directories currently installed.)
Preparing to unpack .../0-fakeroot_1.25.3_x86%5f64.deb ...
Unpacking fakeroot (1.25.3) ...
Selecting previously unselected package libtalloc.
Preparing to unpack .../1-libtalloc_2.3.1_x86%5f64.deb ...
Unpacking libtalloc (2.3.1) ...
Selecting previously unselected package libuuid.
Preparing to unpack .../2-libuuid_1.0.3-4_x86%5f64.deb ...
Unpacking libuuid (1.0.3-4) ...
Selecting previously unselected package ncurses-utils.
Preparing to unpack .../3-ncurses-utils_6.2.20200725_x86%5f64.deb ...
Unpacking ncurses-utils (6.2.20200725) ...
Selecting previously unselected package parted.
Preparing to unpack .../4-parted_3.2-5_x86%5f64.deb ...
Unpacking parted (3.2-5) ...
Selecting previously unselected packaged proot.
Preparing to unpack .../5-proot_5.1.107-35_x86%5f64.deb ...
Unpacking proot (5.1.107-35) ...
Selecting previously unselected package proot-distro.
Preparing to unpack .../6-proot-distro_1.3.3_all.deb ...
Unpacking proot-distro (1.3.3) ...
Setting up libuuid (1.0.3-4) ...
Setting up parted (3.2-5) ...
Setting up ncurses-utils (6.2.20200725) ...
Setting up fakeroot (1.25.3) ...
Fakeroot does not give you any real root permissoins. This utility is
primarily intended to be used for development purposes. More info about
usage at https://wiki.debian.org/FakeRoot.
Programs requiring real root permissions will not run under fakeroot. Do
not post bug reports about this.
Setting up libtalloc (2.3.1) ...
Setting up proot (5.1.107-35) ...
Setting up proot-distro (1.3.3) ...
$ proot -0 login
proot error: ptrace(TRACEME): Operation not permitted
proot error: execve("/data/data/com.termux/files/usr/bin/login"): Operation not
permitted
proot info: It seems your kernel contains this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1202161
To workaround it, see the env. variable PROOT_NO_SECCOMP to 1.
fatal error: see 'proot --help'.ubu
$ ubuntu-bug linux
ubuntu-bug: command not found
$ cat /proc/version_signature > version.log
cat: /proc/version_signature: No such file or directory
$ sudo lspci -vnvn > lspci-vnvn.log
$ (no results gathered)
$lspci -vnvn.log
lspci -vnvn.log: command not found
$ sudo lspci -vnvn
No superuser binary detected.
Are you rooted?
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1908145
Title:
Proot Errors / Operation not permitted / kernel contains bug
Status in linux package in Ubuntu:
Incomplete
Bug description:
WAS TRYING TO RUN: $ pkg install proot proot-distro tsu fakeroot parted
RESULTING: CHecking availability of current mirror: ok
Ign:1
[Kernel-packages] [Bug 1908144] [NEW] disable building bpf selftests
Public bug reported:
Building tools/testing/selftests/bpf/ requires dependencies which cannot
be easily satisfied by our build process. The problem is well-described
by the pending upstream patch:
https://lore.kernel.org/bpf/20201210185233.28091-1-broo...@kernel.org/
From: Mark Brown
Subject: [PATCH] selftests: Skip BPF seftests by default
To effect the same for {groovy, hirsute} we must instead make a
debian/rules change via "UBUNTU: disable building bpf selftests (no
VMLINUX_BTF)".
But lets also pick up the upstream change above, as well as my related
"clarify" change, also pending upstream.
These three patches should be applied to {groovy, hirsute}:
UBUNTU: SAUCE: selftests/bpf: clarify build error if no vmlinux
UBUNTU: SAUCE: selftests: Skip BPF seftests by default
UBUNTU: disable building bpf selftests (no VMLINUX_BTF)
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Affects: linux (Ubuntu Groovy)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Affects: linux (Ubuntu Hirsute)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Description changed:
Building tools/testing/selftests/bpf/ requires dependencies which cannot
be easily satisfied by our build process. The problem is well-described
by the pending upstream patch:
https://lore.kernel.org/bpf/20201210185233.28091-1-broo...@kernel.org/
From: Mark Brown
Subject: [PATCH] selftests: Skip BPF seftests by default
To effect the same for {groovy, hirsute} we must instead make a
debian/rules change via "UBUNTU: disable building bpf selftests (no
VMLINUX_BTF)".
But lets also pick up the upstream change above, as well as my related
"clarify" change, also pending upstream.
- UBUNTU: SAUCE: selftests/bpf: clarify build error if no vmlinux
- UBUNTU: SAUCE: selftests: Skip BPF seftests by default
- UBUNTU: disable building bpf selftests (no VMLINUX_BTF)
+ These three patches should be applied to {groovy, hirsute}:
+
+ UBUNTU: SAUCE: selftests/bpf: clarify build error if no vmlinux
+ UBUNTU: SAUCE: selftests: Skip BPF seftests by default
+ UBUNTU: disable building bpf selftests (no VMLINUX_BTF)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1908144
Title:
disable building bpf selftests
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Groovy:
In Progress
Status in linux source package in Hirsute:
In Progress
Bug description:
Building tools/testing/selftests/bpf/ requires dependencies which
cannot be easily satisfied by our build process. The problem is well-
described by the pending upstream patch:
https://lore.kernel.org/bpf/20201210185233.28091-1-broo...@kernel.org/
From: Mark Brown
Subject: [PATCH] selftests: Skip BPF seftests by default
To effect the same for {groovy, hirsute} we must instead make a
debian/rules change via "UBUNTU: disable building bpf selftests (no
VMLINUX_BTF)".
But lets also pick up the upstream change above, as well as my related
"clarify" change, also pending upstream.
These three patches should be applied to {groovy, hirsute}:
UBUNTU: SAUCE: selftests/bpf: clarify build error if no vmlinux
UBUNTU: SAUCE: selftests: Skip BPF seftests by default
UBUNTU: disable building bpf selftests (no VMLINUX_BTF)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908144/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908139] [NEW] ThinkPad T14s external display not working on ThinkPad USB-C Dock Gen2
Public bug reported: laptop: ThinkPad T14s Gen 1 - AMD Ryzen 7 PRO 4750U docking station: ThinkPad USB-C Dock 2. Gen. external display: NE MultiSync EA275UHD OS: Ubuntu 20.10 - kernel 5.8.0 Plugging the external display into one of the docking station's two DisplayPort connectors leads to the screen resolution changing on the laptop's builtin display and the external display waking up but showing no picture and displaying "no-signal" after a bit. Plugging the external display into the docking station's HDMI connector leads to no visible reaction on either the external nor the builtin display. Plugging the external display into the laptop's builtin HDMI connector works as expected. The external display is recognized and shows an image. I have recorded the output on `dmesg` during the steps mentioned above and inserted explanations using `echo MSG >/dev/kmsg`. The output follows at the end of the message. I believe `ubuntu-bug` should also attach the full log. All above modes of connection work as expected with the same laptop, dock, and display on Windows 10 (installed as dual boot along side Ubuntu). All above modes of connection also work as expected with an older laptop (ThinkPad T470s - Ubuntu 20.04 - kernel 5.4.0), and the same dock and display. This leads me to believe that this is not a hardware issue. The following bug seems related, but seems to have been observed on faulty hardware according to its author. Therefore, I decided to open a separate bug report. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899336 ``` [ 343.372511] plugging DisplayPort into dock port 1 [ 352.666113] [drm] DP Alt mode state on HPD: 1 [ 352.749192] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 75] [ 352.858482] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.888400] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.892555] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.896719] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.900876] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.905596] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.910323] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.914485] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 377.353566] plugged in - no signal [ 396.728970] unplugging [ 403.001418] [drm] DM_MST: stopping TM on aconnector: 2105a317 [id: 75] [ 415.576397] unplugged [ 431.500729] plugging DisplayPort into dock port 2 [ 437.607724] [drm] DP Alt mode state on HPD: 1 [ 437.681116] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 75] [ 437.790303] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.820138] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.824305] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.828462] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.832619] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.837029] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.841984] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.846144] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 458.999849] plugged in - no signal [ 465.702949] unplugging [ 476.127418] [drm] DM_MST: stopping TM on aconnector: 2105a317 [id: 75] [ 476.956491] [drm] Failed to add display topology, DTM TA is not initialized. [ 488.792533] unplugged [ 529.801179] plugging HDMI into dock [ 536.721076] [drm] DP Alt mode state on HPD: 1 [ 536.792947] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 75] [ 536.901958] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.906123] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.910288] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.914611] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.919568] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.923725] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.927888] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.932047] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.936451] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.941486] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.945651] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.949808] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 537.010093] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 271ba325 port 1: DPCD read on addr 0x60 for 1 bytes NAKed [ 592.844147] plugged in - display does not react [ 597.998141] unplugging [ 604.657060] [drm] DM_MST: stopping TM on aconnector: 2105a317 [id: 75] [ 612.058516] unplugged [ 630.409181] plugging HDMI into laptop [ 637.125592] [drm] Failed to add display topology, DTM TA is not initialized. [ 639.077839] [drm] Failed to add display topology, DTM TA is not initialized. [ 639.192248] [drm] Failed to add display topology, DTM TA is not initialized. [ 683.221820] plugged in - working [ 690.347738] unplugging [ 694.212298] [drm] Failed to add display topology, DTM TA is
[Kernel-packages] [Bug 1908081] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1908081 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908081 Title: [linux-image-5.8.0-33.generic] Bogus possible_crtcs: [ENCODER:58:TMDS-58] possible_crtcs=0xf (full crtc mask=0x7) Status in linux package in Ubuntu: Incomplete Bug description: Hi, kernel: Linux ideapad 5.8.0-33-generic #36-Ubuntu SMP Wed Dec 9 09:14:40 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Version of Ubuntu: Ubuntu 20.10 up to date at 14 dec 2020 The kernel linux-image-5.8.0-33.generic show a panic on boot. dic 12 11:48:11 ideapad kernel: amdgpu :03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 dic 12 11:48:11 ideapad kernel: [ cut here ] dic 12 11:48:11 ideapad kernel: Bogus possible_crtcs: [ENCODER:58:TMDS-58] possible_crtcs=0xf (full crtc mask=0x7) dic 12 11:48:11 ideapad kernel: WARNING: CPU: 0 PID: 169 at drivers/gpu/drm/drm_mode_config.c:616 drm_mode_config_validate+0xdb/0x100 [drm] dic 12 11:48:11 ideapad kernel: Modules linked in: hid_rmi rmi_core videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc hi> dic 12 11:48:11 ideapad kernel: CPU: 0 PID: 169 Comm: systemd-udevd Tainted: G O 5.8.0-33-generic #36-Ubuntu dic 12 11:48:11 ideapad kernel: Hardware name: LENOVO 81LW/LNVNB161216, BIOS ARCN34WW 06/03/2020 dic 12 11:48:11 ideapad kernel: RIP: 0010:drm_mode_config_validate+0xdb/0x100 [drm] dic 12 11:48:11 ideapad kernel: Code: 39 d6 75 e5 41 8b 4d 48 41 85 c8 74 09 44 89 c0 f7 d0 85 c8 74 16 49 8b 55 38 41 8b 75 18 48 c7 c7 f0 c8 30 c0 > dic 12 11:48:11 ideapad kernel: RSP: 0018:b17280363aa0 EFLAGS: 00010286 dic 12 11:48:11 ideapad kernel: RAX: RBX: 99c5360192d8 RCX: 0388 dic 12 11:48:11 ideapad kernel: RDX: 0001 RSI: 0082 RDI: 0246 dic 12 11:48:11 ideapad kernel: RBP: b17280363ab8 R08: R09: 0388 dic 12 11:48:11 ideapad kernel: R10: 00aa R11: 99cb9440 R12: 0001 dic 12 11:48:11 ideapad kernel: R13: 99c525d88400 R14: 00020016 R15: 99c536019000 dic 12 11:48:11 ideapad kernel: FS: 7fbbc9f868c0() GS:99c538a0() knlGS: dic 12 11:48:11 ideapad kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) dic 12 11:48:11 ideapad kernel: CS: 0010 DS: ES: CR0: 80050033 dic 12 11:48:11 ideapad kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) dic 12 11:48:11 ideapad kernel: CR2: 7fbbc9f6c154 CR3: 0001a61ee000 CR4: 003406f0 dic 12 11:48:11 ideapad kernel: Call Trace: dic 12 11:48:11 ideapad kernel: drm_dev_register+0x16c/0x1c0 [drm] dic 12 11:48:11 ideapad kernel: amdgpu_pci_probe+0x107/0x180 [amdgpu] dic 12 11:48:11 ideapad kernel: usb 3-2: New USB device found, idVendor=0bda, idProduct=c024, bcdDevice= 1.10 dic 12 11:48:11 ideapad kernel: local_pci_probe+0x48/0x80 dic 12 11:48:11 ideapad kernel: ata2.00: ATAPI: PLDSDVD-RW DA8AESH, XL6M, max UDMA/133 dic 12 11:48:11 ideapad kernel: usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 dic 12 11:48:11 ideapad kernel: usb 3-2: Product: Bluetooth Radio dic 12 11:48:11 ideapad kernel: usb 3-2: Manufacturer: Realtek dic 12 11:48:11 ideapad kernel: usb 3-2: SerialNumber: 00e04c01 dic 12 11:48:11 ideapad kernel: pci_call_probe+0x53/0xe0 dic 12 11:48:11 ideapad kernel: pci_device_probe+0xad/0xf0 dic 12 11:48:11 ideapad kernel: really_probe+0x177/0x430 dic 12 11:48:11 ideapad kernel: driver_probe_device+0xe9/0x160 dic 12 11:48:11 ideapad kernel: device_driver_attach+0xab/0xb0 dic 12 11:48:11 ideapad kernel: __driver_attach+0x8f/0x150 dic 12 11:48:11 ideapad kernel: ? device_driver_attach+0xb0/0xb0 dic 12 11:48:11 ideapad kernel: bus_for_each_dev+0x7e/0xc0 dic 12 11:48:11 ideapad kernel: driver_attach+0x1e/0x20 dic 12 11:48:11 ideapad kernel: bus_add_driver+0x135/0x1f0 dic 12 11:48:11 ideapad kernel: driver_register+0x91/0xf0 dic 12 11:48:11 ideapad kernel: __pci_register_driver+0x54/0x60 dic 12 11:48:11 ideapad kernel: amdgpu_init+0x83/0x1000 [amdgpu] dic 12 11:48:11 ideapad kernel: ata1.00: ATA-10: WDC
[Kernel-packages] [Bug 1908081] Re: [linux-image-5.8.0-33.generic] Bogus possible_crtcs: [ENCODER:58:TMDS-58] possible_crtcs=0xf (full crtc mask=0x7)
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908081 Title: [linux-image-5.8.0-33.generic] Bogus possible_crtcs: [ENCODER:58:TMDS-58] possible_crtcs=0xf (full crtc mask=0x7) Status in linux package in Ubuntu: New Bug description: Hi, kernel: Linux ideapad 5.8.0-33-generic #36-Ubuntu SMP Wed Dec 9 09:14:40 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Version of Ubuntu: Ubuntu 20.10 up to date at 14 dec 2020 The kernel linux-image-5.8.0-33.generic show a panic on boot. dic 12 11:48:11 ideapad kernel: amdgpu :03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 dic 12 11:48:11 ideapad kernel: [ cut here ] dic 12 11:48:11 ideapad kernel: Bogus possible_crtcs: [ENCODER:58:TMDS-58] possible_crtcs=0xf (full crtc mask=0x7) dic 12 11:48:11 ideapad kernel: WARNING: CPU: 0 PID: 169 at drivers/gpu/drm/drm_mode_config.c:616 drm_mode_config_validate+0xdb/0x100 [drm] dic 12 11:48:11 ideapad kernel: Modules linked in: hid_rmi rmi_core videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc hi> dic 12 11:48:11 ideapad kernel: CPU: 0 PID: 169 Comm: systemd-udevd Tainted: G O 5.8.0-33-generic #36-Ubuntu dic 12 11:48:11 ideapad kernel: Hardware name: LENOVO 81LW/LNVNB161216, BIOS ARCN34WW 06/03/2020 dic 12 11:48:11 ideapad kernel: RIP: 0010:drm_mode_config_validate+0xdb/0x100 [drm] dic 12 11:48:11 ideapad kernel: Code: 39 d6 75 e5 41 8b 4d 48 41 85 c8 74 09 44 89 c0 f7 d0 85 c8 74 16 49 8b 55 38 41 8b 75 18 48 c7 c7 f0 c8 30 c0 > dic 12 11:48:11 ideapad kernel: RSP: 0018:b17280363aa0 EFLAGS: 00010286 dic 12 11:48:11 ideapad kernel: RAX: RBX: 99c5360192d8 RCX: 0388 dic 12 11:48:11 ideapad kernel: RDX: 0001 RSI: 0082 RDI: 0246 dic 12 11:48:11 ideapad kernel: RBP: b17280363ab8 R08: R09: 0388 dic 12 11:48:11 ideapad kernel: R10: 00aa R11: 99cb9440 R12: 0001 dic 12 11:48:11 ideapad kernel: R13: 99c525d88400 R14: 00020016 R15: 99c536019000 dic 12 11:48:11 ideapad kernel: FS: 7fbbc9f868c0() GS:99c538a0() knlGS: dic 12 11:48:11 ideapad kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) dic 12 11:48:11 ideapad kernel: CS: 0010 DS: ES: CR0: 80050033 dic 12 11:48:11 ideapad kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) dic 12 11:48:11 ideapad kernel: CR2: 7fbbc9f6c154 CR3: 0001a61ee000 CR4: 003406f0 dic 12 11:48:11 ideapad kernel: Call Trace: dic 12 11:48:11 ideapad kernel: drm_dev_register+0x16c/0x1c0 [drm] dic 12 11:48:11 ideapad kernel: amdgpu_pci_probe+0x107/0x180 [amdgpu] dic 12 11:48:11 ideapad kernel: usb 3-2: New USB device found, idVendor=0bda, idProduct=c024, bcdDevice= 1.10 dic 12 11:48:11 ideapad kernel: local_pci_probe+0x48/0x80 dic 12 11:48:11 ideapad kernel: ata2.00: ATAPI: PLDSDVD-RW DA8AESH, XL6M, max UDMA/133 dic 12 11:48:11 ideapad kernel: usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 dic 12 11:48:11 ideapad kernel: usb 3-2: Product: Bluetooth Radio dic 12 11:48:11 ideapad kernel: usb 3-2: Manufacturer: Realtek dic 12 11:48:11 ideapad kernel: usb 3-2: SerialNumber: 00e04c01 dic 12 11:48:11 ideapad kernel: pci_call_probe+0x53/0xe0 dic 12 11:48:11 ideapad kernel: pci_device_probe+0xad/0xf0 dic 12 11:48:11 ideapad kernel: really_probe+0x177/0x430 dic 12 11:48:11 ideapad kernel: driver_probe_device+0xe9/0x160 dic 12 11:48:11 ideapad kernel: device_driver_attach+0xab/0xb0 dic 12 11:48:11 ideapad kernel: __driver_attach+0x8f/0x150 dic 12 11:48:11 ideapad kernel: ? device_driver_attach+0xb0/0xb0 dic 12 11:48:11 ideapad kernel: bus_for_each_dev+0x7e/0xc0 dic 12 11:48:11 ideapad kernel: driver_attach+0x1e/0x20 dic 12 11:48:11 ideapad kernel: bus_add_driver+0x135/0x1f0 dic 12 11:48:11 ideapad kernel: driver_register+0x91/0xf0 dic 12 11:48:11 ideapad kernel: __pci_register_driver+0x54/0x60 dic 12 11:48:11 ideapad kernel: amdgpu_init+0x83/0x1000 [amdgpu] dic 12 11:48:11 ideapad kernel: ata1.00: ATA-10: WDC WD10SPZX-24Z10, 04.01A04, max UDMA/133 dic 12 11:48:11 ideapad kernel: ? 0xc0a6a000 dic 12 11:48:11 ideapad kernel: do_one_initcall+0x4a/0x200 dic 12 11:48:11 ideapad kernel: ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA dic 12 11:48:11 ideapad kernel: ? _cond_resched+0x1a/0x50 dic 12 11:48:11 ideapad kernel: ata1.00: configured for UDMA/133 dic 12 11:48:11 ideapad kernel: ? kmem_cache_alloc_trace+0x1a1/0x240 dic 12 11:48:11 ideapad kernel: ata2.00: configured for UDMA/133 dic 12 11:48:11 ideapad kernel: scsi 0:0:0:0: Direct-Access
[Kernel-packages] [Bug 1908099] Re: nvidia-dkms-390 fails to build on unstable / 5.10
** Tags added: patch -- 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/1908099 Title: nvidia-dkms-390 fails to build on unstable / 5.10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-390 source package in Hirsute: New Bug description: [Impact] nvidia-graphics-drivers-390 fails to build against linux 5.10: ERROR (dkms apport): kernel package linux-headers-5.10.0-6-generic is not supported Error! Bad return status for module build on kernel: 5.10.0-6-generic (x86_64) Consult /var/lib/dkms/nvidia/390.138/build/make.log for more information. dpkg: error processing package nvidia-dkms-390 (--configure): installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.10.0-6-generic Errors were encountered while processing: nvidia-dkms-390 E: Sub-process /usr/bin/dpkg returned an error code (1) [Test case] sudo apt install nvidia-dkms-390 [Fix] Fix build errors adding the proper #ifdef to support the new 5.10 includes, function prototypes and data structs. [Regression potential] All the new code is conditional (#ifdef) and it's applied only with 5.10, so there is no risk to break the other kernels (5.8). Moreover, it's worth considering that hirsute should move soon to 5.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1908099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908081] [NEW] [linux-image-5.8.0-33.generic] Bogus possible_crtcs: [ENCODER:58:TMDS-58] possible_crtcs=0xf (full crtc mask=0x7)
You have been subscribed to a public bug: Hi, kernel: Linux ideapad 5.8.0-33-generic #36-Ubuntu SMP Wed Dec 9 09:14:40 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Version of Ubuntu: Ubuntu 20.10 up to date at 14 dec 2020 The kernel linux-image-5.8.0-33.generic show a panic on boot. dic 12 11:48:11 ideapad kernel: amdgpu :03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 dic 12 11:48:11 ideapad kernel: [ cut here ] dic 12 11:48:11 ideapad kernel: Bogus possible_crtcs: [ENCODER:58:TMDS-58] possible_crtcs=0xf (full crtc mask=0x7) dic 12 11:48:11 ideapad kernel: WARNING: CPU: 0 PID: 169 at drivers/gpu/drm/drm_mode_config.c:616 drm_mode_config_validate+0xdb/0x100 [drm] dic 12 11:48:11 ideapad kernel: Modules linked in: hid_rmi rmi_core videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc hi> dic 12 11:48:11 ideapad kernel: CPU: 0 PID: 169 Comm: systemd-udevd Tainted: G O 5.8.0-33-generic #36-Ubuntu dic 12 11:48:11 ideapad kernel: Hardware name: LENOVO 81LW/LNVNB161216, BIOS ARCN34WW 06/03/2020 dic 12 11:48:11 ideapad kernel: RIP: 0010:drm_mode_config_validate+0xdb/0x100 [drm] dic 12 11:48:11 ideapad kernel: Code: 39 d6 75 e5 41 8b 4d 48 41 85 c8 74 09 44 89 c0 f7 d0 85 c8 74 16 49 8b 55 38 41 8b 75 18 48 c7 c7 f0 c8 30 c0 > dic 12 11:48:11 ideapad kernel: RSP: 0018:b17280363aa0 EFLAGS: 00010286 dic 12 11:48:11 ideapad kernel: RAX: RBX: 99c5360192d8 RCX: 0388 dic 12 11:48:11 ideapad kernel: RDX: 0001 RSI: 0082 RDI: 0246 dic 12 11:48:11 ideapad kernel: RBP: b17280363ab8 R08: R09: 0388 dic 12 11:48:11 ideapad kernel: R10: 00aa R11: 99cb9440 R12: 0001 dic 12 11:48:11 ideapad kernel: R13: 99c525d88400 R14: 00020016 R15: 99c536019000 dic 12 11:48:11 ideapad kernel: FS: 7fbbc9f868c0() GS:99c538a0() knlGS: dic 12 11:48:11 ideapad kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) dic 12 11:48:11 ideapad kernel: CS: 0010 DS: ES: CR0: 80050033 dic 12 11:48:11 ideapad kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) dic 12 11:48:11 ideapad kernel: CR2: 7fbbc9f6c154 CR3: 0001a61ee000 CR4: 003406f0 dic 12 11:48:11 ideapad kernel: Call Trace: dic 12 11:48:11 ideapad kernel: drm_dev_register+0x16c/0x1c0 [drm] dic 12 11:48:11 ideapad kernel: amdgpu_pci_probe+0x107/0x180 [amdgpu] dic 12 11:48:11 ideapad kernel: usb 3-2: New USB device found, idVendor=0bda, idProduct=c024, bcdDevice= 1.10 dic 12 11:48:11 ideapad kernel: local_pci_probe+0x48/0x80 dic 12 11:48:11 ideapad kernel: ata2.00: ATAPI: PLDSDVD-RW DA8AESH, XL6M, max UDMA/133 dic 12 11:48:11 ideapad kernel: usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 dic 12 11:48:11 ideapad kernel: usb 3-2: Product: Bluetooth Radio dic 12 11:48:11 ideapad kernel: usb 3-2: Manufacturer: Realtek dic 12 11:48:11 ideapad kernel: usb 3-2: SerialNumber: 00e04c01 dic 12 11:48:11 ideapad kernel: pci_call_probe+0x53/0xe0 dic 12 11:48:11 ideapad kernel: pci_device_probe+0xad/0xf0 dic 12 11:48:11 ideapad kernel: really_probe+0x177/0x430 dic 12 11:48:11 ideapad kernel: driver_probe_device+0xe9/0x160 dic 12 11:48:11 ideapad kernel: device_driver_attach+0xab/0xb0 dic 12 11:48:11 ideapad kernel: __driver_attach+0x8f/0x150 dic 12 11:48:11 ideapad kernel: ? device_driver_attach+0xb0/0xb0 dic 12 11:48:11 ideapad kernel: bus_for_each_dev+0x7e/0xc0 dic 12 11:48:11 ideapad kernel: driver_attach+0x1e/0x20 dic 12 11:48:11 ideapad kernel: bus_add_driver+0x135/0x1f0 dic 12 11:48:11 ideapad kernel: driver_register+0x91/0xf0 dic 12 11:48:11 ideapad kernel: __pci_register_driver+0x54/0x60 dic 12 11:48:11 ideapad kernel: amdgpu_init+0x83/0x1000 [amdgpu] dic 12 11:48:11 ideapad kernel: ata1.00: ATA-10: WDC WD10SPZX-24Z10, 04.01A04, max UDMA/133 dic 12 11:48:11 ideapad kernel: ? 0xc0a6a000 dic 12 11:48:11 ideapad kernel: do_one_initcall+0x4a/0x200 dic 12 11:48:11 ideapad kernel: ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA dic 12 11:48:11 ideapad kernel: ? _cond_resched+0x1a/0x50 dic 12 11:48:11 ideapad kernel: ata1.00: configured for UDMA/133 dic 12 11:48:11 ideapad kernel: ? kmem_cache_alloc_trace+0x1a1/0x240 dic 12 11:48:11 ideapad kernel: ata2.00: configured for UDMA/133 dic 12 11:48:11 ideapad kernel: scsi 0:0:0:0: Direct-Access ATA WDC WD10SPZX-24Z 1A04 PQ: 0 ANSI: 5 dic 12 11:48:11 ideapad kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 dic 12 11:48:11 ideapad kernel: sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) dic 12 11:48:11 ideapad kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks dic 12 11:48:11 ideapad kernel: sd 0:0:0:0: [sda] Write Protect is off dic 12 11:48:11 ideapad kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 dic 12 11:48:11
[Kernel-packages] [Bug 1902531] Re: [linux-azure] IP forwarding issue in netvsc
** Description changed: + [Impact] + We identified an issue with the Linux netvsc driver when used in IP forwarding mode. The problem is that the RSS hash value is not propagated to the outgoing packet, and so such packets go out on channel 0. This produces an imbalance across outgoing channels, and a possible overload on the single host-side CPU that is processing channel 0. The problem does not occur when Accelerated Networking is used because the packets go out through the Mellanox driver. Because it is tied to IP forwarding, the problem is presumably most likely to be visible in a virtual appliance device that is doing network load balancing or other kinds of packet filtering and redirection. We would like to request fixes to this issue in 16.04, 18.04 and 20.04. Two fixes are already in the upstream v5.5+, so they’re already in 5.8.0-1011.11. For 5.4.0-1031.32, the 2 fixes can apply cleanly: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e For 5.0.0-1036.38, we need 1 more patch applied first, so the list is: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b441f79532ec13dc82d05c55badc4da1f62a6141 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e For 4.15.0-1098.109~16.04.1, the 2 patches can not apply cleanly, so Dexuan backported them here: https://github.com/dcui/linux/commit/4ed58762a56cccfd006e633fac63311176508795 https://github.com/dcui/linux/commit/40ad7849a6365a5a485f05453e10e3541025e25a (The 2 patches are on the branch https://github.com/dcui/linux/commits/decui/ubuntu_16.04/linux-azure/Ubuntu-azure-4.15.0-1098.109_16.04.1) + + + [Test Case] + + As described in https://bugs.launchpad.net/ubuntu/+source/linux- + azure/+bug/1902531/comments/6 + + + [Where problems could occur] + + A potential regression would affect Azure instance using netvsc without + accelerated networking. -- 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/1902531 Title: [linux-azure] IP forwarding issue in netvsc Status in linux-azure package in Ubuntu: New Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: In Progress Status in linux-azure source package in Focal: In Progress Status in linux-azure-4.15 source package in Focal: Invalid Bug description: [Impact] We identified an issue with the Linux netvsc driver when used in IP forwarding mode. The problem is that the RSS hash value is not propagated to the outgoing packet, and so such packets go out on channel 0. This produces an imbalance across outgoing channels, and a possible overload on the single host-side CPU that is processing channel 0. The problem does not occur when Accelerated Networking is used because the packets go out through the Mellanox driver. Because it is tied to IP forwarding, the problem is presumably most likely to be visible in a virtual appliance device that is doing network load balancing or other kinds of packet filtering and redirection. We would like to request fixes to this issue in 16.04, 18.04 and 20.04. Two fixes are already in the upstream v5.5+, so they’re already in 5.8.0-1011.11. For 5.4.0-1031.32, the 2 fixes can apply cleanly: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e For 5.0.0-1036.38, we need 1 more patch applied first, so the list is: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b441f79532ec13dc82d05c55badc4da1f62a6141 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e For 4.15.0-1098.109~16.04.1, the 2 patches can not apply cleanly, so Dexuan backported them here: https://github.com/dcui/linux/commit/4ed58762a56cccfd006e633fac63311176508795 https://github.com/dcui/linux/commit/40ad7849a6365a5a485f05453e10e3541025e25a (The 2 patches are on the branch https://github.com/dcui/linux/commits/decui/ubuntu_16.04/linux-azure/Ubuntu-azure-4.15.0-1098.109_16.04.1) [Test Case] As described in https://bugs.launchpad.net/ubuntu/+source/linux-
[Kernel-packages] [Bug 1908048] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443540/+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/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GemiBook Pro dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443539/+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/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GemiBook Pro dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443544/+files/acpidump.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/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GemiBook Pro dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907285] Re: Drop i915 PSR workarounds
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907285 Title: Drop i915 PSR workarounds Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Bug description: [Impact] Disabling PSR helps some platforms but breaks others. So let's not play this whack-a-mole game. In addition to that, PSR can provide significant power saving, let Intel SoC reach PC10 or even SLP_S0 withouth turning screen off. [Fix] Drop PSR workaround and stick to upstream code. [Test] Monitor numbers in /sys/kernel/debug/pmc_core/* With PSR enabled, some Tiger Lake laptops can reach SLP_S0 without turning screen off. [Regression Potential] Panels that don't work well with PSR may break again. If that ever happens, we can introduce a blacklist on panels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443543/+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/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GemiBook Pro dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443542/+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/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GemiBook Pro dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443541/+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/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GemiBook Pro dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443534/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GemiBook Pro dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443537/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GemiBook Pro dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443528/+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/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GemiBook Pro dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443536/+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/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GemiBook Pro dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443533/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GemiBook Pro dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443538/+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/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GemiBook Pro dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443531/+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/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GemiBook Pro dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443535/+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/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GemiBook Pro dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443530/+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/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GemiBook Pro dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443532/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GemiBook Pro dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443529/+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/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GemiBook Pro dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] Re: mircoSD could not operate
apport information ** Tags added: apport-collected focal ** Description changed: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.13 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: nakasima 1564 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-12-13 (1 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera + Bus 001 Device 003: ID 8087:0029 Intel Corp. + Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite + ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-58-generic N/A + linux-backports-modules-5.4.0-58-generic N/A + linux-firmware1.187.6 + Tags: focal + Uname: Linux 5.4.0-58-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 09/30/2020 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: JXX-BI-14.1-W133GWR200-035-D + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: To be filled by O.E.M. + dmi.board.vendor: To be filled by O.E.M. + dmi.board.version: To be filled by O.E.M. + dmi.chassis.asset.tag: To be filled by O.E.M. + dmi.chassis.type: 10 + dmi.chassis.vendor: To be filled by O.E.M. + dmi.chassis.version: To be filled by O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJXX-BI-14.1-W133GWR200-035-D:bd09/30/2020:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnGemiBookPro:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: GemiBook Pro + dmi.product.sku: To be filled by O.E.M. + dmi.product.version: To be filled by O.E.M. + dmi.sys.vendor: CHUWI�Innovation�And�Technology(ShenZhen)co.,Ltd ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1908048/+attachment/5443527/+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/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1564 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: b'CHUWI\xa0Innovation\xa0And\xa0Technology(ShenZhen)co.,Ltd' GemiBook Pro Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=UUID=d3aeb647-8a72-438f-ae6c-e31104261cc3 ro ipv6.disable=1 quite ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A
[Kernel-packages] [Bug 1907992] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443519/+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/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443517/+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/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443514/+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/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443515/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443516/+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/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443518/+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/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443520/+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/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443512/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443513/+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/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443521/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: ubuntu-mate Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443509/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443506/+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/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443505/+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/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443510/+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/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443508/+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/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443507/+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/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443511/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1907992/+attachment/5443504/+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/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark _MarkForUpload: True dmi.bios.date: 06/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP500LN.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP500LN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP500LN dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1907992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907992] Re: Kernel update to 5.4.0-58 breaks system
UPDATE: I updated my Dev VM with has similar configuration to 5.4.0-58 and this works without obvious problems. While trying the reproduce the failure on the ASUS laptop I found that that there is no problem when network is disconnected. Problem appears, when network is connected in power-down. Several stop jobs start bailing and the shut down takes several minutes. No possibility to generate or view logs in this state. Therefore apport-collect was done after reboot to 5.4.0-48 (four eight!) ** Tags added: apport-collected ** Description changed: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.13 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: sven 1771 F pulseaudio + /dev/snd/controlC0: sven 1771 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: MATE + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-01-25 (324 days ago) + InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) + MachineType: ASUSTeK COMPUTER INC. TP500LN + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer + ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-48-generic N/A + linux-backports-modules-5.4.0-48-generic N/A + linux-firmware1.187.6 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: focal + Uname: Linux 5.4.0-48-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip kismet kvm libvirt lpadmin lxd plugdev sambashare sudo users video wireshark + _MarkForUpload: True + dmi.bios.date: 06/11/2014 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: TP500LN.203 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: TP500LN + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP500LN.203:bd06/11/2014:svnASUSTeKCOMPUTERINC.:pnTP500LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP500LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: TP + dmi.product.name: TP500LN + dmi.product.sku: ASUS-NotebookSKU + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. + modified.conffile..etc.default.apport: + # set this to 0 to disable apport, or to 1 to enable it + # you can temporarily override this with + # sudo service apport start force_start=1 + enabled=0 + mtime.conffile..etc.default.apport: 2020-01-29T20:18:17.309547 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907992 Title: Kernel update to 5.4.0-58 breaks system Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After update from kernel 5.4.0-56 to 5.4.0-58 system will no longer respond after lightdm login. If you are able to request a shutdown, you get the message that caja is not responding. Fault was observed on two different laptops (Lenovo B560 and Asus TP-500LN). Forced power down followed by reboot with 5.4.0-48 and reboot with 5.4.0-56 fixed the problem. Reproducible. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sven 1771 F pulseaudio /dev/snd/controlC0: sven 1771 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (324 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. TP500LN NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=531ea3ab-2c4c-4276-af3c-8586a9389f68 ro quiet splash nomodset pci=noaer ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.6
[Kernel-packages] [Bug 1908108] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1908108 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908108 Title: tg3: transmit timed out, resetting Status in linux package in Ubuntu: Incomplete Bug description: On a deploy of kubernetes, we're seeing a machine have issues with its tg3 driven nics. We see: Dec 14 07:44:08 juju-fcf29c-0-lxd-1 kernel: [ 1496.772960] tg3 :02:00.1 eth1: transmit timed out, resetting Around that time, we have issues with services losing network connections. A juju crashdump with logs is available here: https://oil-jenkins.canonical.com/artifacts/c15028dc-46fa-4f08-8895-55e9d500c362/generated/generated/kubernetes/juju-crashdump-kubernetes-2020-12-14-07.48.49.tar.gz syslog is at kubernetes-master_0/var/log/syslog this is on focal: [0.00] kernel: Linux version 5.4.0-58-generic (buildd@lcy01-amd64-004) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 (Ubuntu 5.4.0-58.64-generic 5.4.73) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
Another thing to note, when I get flickering monitor loss unplugging and plugging in the dock seems to resolve. Same thing going on in the logs then: [221027.376079] [drm:intel_fbc_enable [i915]] Enabling FBC on pipe A [221027.387002] [drm:__intel_fbc_disable [i915]] Disabling FBC on pipe A [221027.387064] [drm:drm_atomic_state_default_clear [drm]] Clearing atomic state 665ad61a [221027.387095] [drm:__drm_atomic_state_free [drm]] Freeing atomic state 665ad61a [221027.391513] [drm:drm_mode_addfb2 [drm]] [FB:252] [221027.391551] [drm:drm_atomic_state_init [drm]] Allocated atomic state 665ad61a [221027.391579] [drm:drm_atomic_get_crtc_state [drm]] Added [CRTC:91:pipe A] 2b78400a state to 665ad61a [221027.391601] [drm:drm_atomic_get_plane_state [drm]] Added [PLANE:31:plane 1A] 8e58a6fb state to 665ad61a [221027.391623] [drm:drm_atomic_set_fb_for_plane [drm]] Set [FB:252] for [PLANE:31:plane 1A] state 8e58a6fb [221027.391645] [drm:drm_atomic_check_only [drm]] checking 665ad61a [221027.391764] [drm:intel_plane_atomic_calc_changes [i915]] [CRTC:91:pipe A] with [PLANE:31:plane 1A] visible 1 -> 1, off 0, on 0, ms 0 [221027.391841] [drm:intel_atomic_get_global_obj_state [i915]] Added new global object d2037ee9 state b32f3203 to 665ad61a [221027.391870] [drm:drm_atomic_nonblocking_commit [drm]] committing 665ad61a nonblocking [221027.391994] [drm:intel_fbc_enable [i915]] reserved 49152000 bytes of contiguous stolen space for FBC, threshold: 1 I also have a corrupt cursor issue over time - I'll see if I can get a photo of that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 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.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908108] [NEW] tg3: transmit timed out, resetting
Public bug reported: On a deploy of kubernetes, we're seeing a machine have issues with its tg3 driven nics. We see: Dec 14 07:44:08 juju-fcf29c-0-lxd-1 kernel: [ 1496.772960] tg3 :02:00.1 eth1: transmit timed out, resetting Around that time, we have issues with services losing network connections. A juju crashdump with logs is available here: https://oil-jenkins.canonical.com/artifacts/c15028dc-46fa-4f08-8895-55e9d500c362/generated/generated/kubernetes/juju-crashdump-kubernetes-2020-12-14-07.48.49.tar.gz syslog is at kubernetes-master_0/var/log/syslog this is on focal: [0.00] kernel: Linux version 5.4.0-58-generic (buildd@lcy01-amd64-004) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 (Ubuntu 5.4.0-58.64-generic 5.4.73) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: On a deploy of kubernetes, we're seeing a machine have issues with its tg3 driven nics. We see: Dec 14 07:44:08 juju-fcf29c-0-lxd-1 kernel: [ 1496.772960] tg3 :02:00.1 eth1: transmit timed out, resetting Around that time, we have issues with services losing network connections. + A juju crashdump with logs is available here: + https://oil-jenkins.canonical.com/artifacts/c15028dc-46fa-4f08-8895-55e9d500c362/generated/generated/kubernetes/juju-crashdump-kubernetes-2020-12-14-07.48.49.tar.gz + + syslog is at kubernetes-master_0/var/log/syslog this is on focal: [0.00] kernel: Linux version 5.4.0-58-generic (buildd@lcy01-amd64-004) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 (Ubuntu 5.4.0-58.64-generic 5.4.73) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908108 Title: tg3: transmit timed out, resetting Status in linux package in Ubuntu: New Bug description: On a deploy of kubernetes, we're seeing a machine have issues with its tg3 driven nics. We see: Dec 14 07:44:08 juju-fcf29c-0-lxd-1 kernel: [ 1496.772960] tg3 :02:00.1 eth1: transmit timed out, resetting Around that time, we have issues with services losing network connections. A juju crashdump with logs is available here: https://oil-jenkins.canonical.com/artifacts/c15028dc-46fa-4f08-8895-55e9d500c362/generated/generated/kubernetes/juju-crashdump-kubernetes-2020-12-14-07.48.49.tar.gz syslog is at kubernetes-master_0/var/log/syslog this is on focal: [0.00] kernel: Linux version 5.4.0-58-generic (buildd@lcy01-amd64-004) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 (Ubuntu 5.4.0-58.64-generic 5.4.73) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908099] Re: nvidia-dkms-390 fails to build on unstable / 5.10
debdiff that fixes the 5.10 build errors reported in attach. ** Patch added: "hirsute-nvidia-dkms-390.debdiff" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1908099/+attachment/5443484/+files/hirsute-nvidia-dkms-390.debdiff -- 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/1908099 Title: nvidia-dkms-390 fails to build on unstable / 5.10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-390 source package in Hirsute: New Bug description: [Impact] nvidia-graphics-drivers-390 fails to build against linux 5.10: ERROR (dkms apport): kernel package linux-headers-5.10.0-6-generic is not supported Error! Bad return status for module build on kernel: 5.10.0-6-generic (x86_64) Consult /var/lib/dkms/nvidia/390.138/build/make.log for more information. dpkg: error processing package nvidia-dkms-390 (--configure): installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.10.0-6-generic Errors were encountered while processing: nvidia-dkms-390 E: Sub-process /usr/bin/dpkg returned an error code (1) [Test case] sudo apt install nvidia-dkms-390 [Fix] Fix build errors adding the proper #ifdef to support the new 5.10 includes, function prototypes and data structs. [Regression potential] All the new code is conditional (#ifdef) and it's applied only with 5.10, so there is no risk to break the other kernels (5.8). Moreover, it's worth considering that hirsute should move soon to 5.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1908099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908106] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908106 Title: The ath10k_pci driver crashes all the time now Status in linux package in Ubuntu: Confirmed Bug description: The ath10k_pci driver is crashing constantly now. It started happening a few months ago, but with the most recent Ubuntu update to the 5.4.0-58 kernel, it's so bad that I can't use it reliably for very long at all. It doesn't seem to fail from any particular kind of load on the network stack. Just seems to be random. I've attached the syslog with some context around the errors, separated by "sudo systemctl restart NetworkManager" attempts as well as a reboot or two. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ddt1553 F pulseaudio /dev/snd/controlC0: ddt1553 F pulseaudio /dev/snd/pcmC0D0p: ddt1553 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 09:01:54 2020 InstallationDate: Installed on 2020-03-23 (266 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 003: ID 0c45:6708 Microdia Integrated_Webcam_FHD Bus 001 Device 002: ID 187c:0550 Alienware Corporation AW-ELC Bus 001 Device 004: ID 0cf3:e301 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware 15 R4 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=875cff72-a3db-4709-ac4d-ce80b29b9970 ro i915.alpha_support=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-12 (216 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 15 R4 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware15R4:pvr1.7.0:rvnAlienware:rnAlienware15R4:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 15 R4 dmi.product.sku: 0876 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908106] [NEW] The ath10k_pci driver crashes all the time now
Public bug reported: The ath10k_pci driver is crashing constantly now. It started happening a few months ago, but with the most recent Ubuntu update to the 5.4.0-58 kernel, it's so bad that I can't use it reliably for very long at all. It doesn't seem to fail from any particular kind of load on the network stack. Just seems to be random. I've attached the syslog with some context around the errors, separated by "sudo systemctl restart NetworkManager" attempts as well as a reboot or two. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ddt1553 F pulseaudio /dev/snd/controlC0: ddt1553 F pulseaudio /dev/snd/pcmC0D0p: ddt1553 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 09:01:54 2020 InstallationDate: Installed on 2020-03-23 (266 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 003: ID 0c45:6708 Microdia Integrated_Webcam_FHD Bus 001 Device 002: ID 187c:0550 Alienware Corporation AW-ELC Bus 001 Device 004: ID 0cf3:e301 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware 15 R4 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=875cff72-a3db-4709-ac4d-ce80b29b9970 ro i915.alpha_support=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-12 (216 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 15 R4 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware15R4:pvr1.7.0:rvnAlienware:rnAlienware15R4:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 15 R4 dmi.product.sku: 0876 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1908106/+attachment/5443485/+files/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908106 Title: The ath10k_pci driver crashes all the time now Status in linux package in Ubuntu: Confirmed Bug description: The ath10k_pci driver is crashing constantly now. It started happening a few months ago, but with the most recent Ubuntu update to the 5.4.0-58 kernel, it's so bad that I can't use it reliably for very long at all. It doesn't seem to fail from any particular kind of load on the network stack. Just seems to be random. I've attached the syslog with some context around the errors, separated by "sudo systemctl restart NetworkManager" attempts as well as a reboot or two. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ddt1553 F pulseaudio /dev/snd/controlC0: ddt1553 F pulseaudio /dev/snd/pcmC0D0p: ddt1553 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 09:01:54 2020 InstallationDate: Installed on 2020-03-23 (266 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 003: ID 0c45:6708 Microdia Integrated_Webcam_FHD Bus 001 Device 002: ID 187c:0550 Alienware Corporation AW-ELC Bus 001 Device 004: ID 0cf3:e301 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware 15 R4 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1908099] Re: nvidia-dkms-390 fails to build on unstable / 5.10
make.log in attach. ** Attachment added: "make.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1908099/+attachment/5443483/+files/make.log -- 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/1908099 Title: nvidia-dkms-390 fails to build on unstable / 5.10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-390 source package in Hirsute: New Bug description: [Impact] nvidia-graphics-drivers-390 fails to build against linux 5.10: ERROR (dkms apport): kernel package linux-headers-5.10.0-6-generic is not supported Error! Bad return status for module build on kernel: 5.10.0-6-generic (x86_64) Consult /var/lib/dkms/nvidia/390.138/build/make.log for more information. dpkg: error processing package nvidia-dkms-390 (--configure): installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.10.0-6-generic Errors were encountered while processing: nvidia-dkms-390 E: Sub-process /usr/bin/dpkg returned an error code (1) [Test case] sudo apt install nvidia-dkms-390 [Fix] Fix build errors adding the proper #ifdef to support the new 5.10 includes, function prototypes and data structs. [Regression potential] All the new code is conditional (#ifdef) and it's applied only with 5.10, so there is no risk to break the other kernels (5.8). Moreover, it's worth considering that hirsute should move soon to 5.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1908099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908099] [NEW] nvidia-dkms-390 fails to build on unstable / 5.10
Public bug reported: [Impact] nvidia-graphics-drivers-390 fails to build against linux 5.10: ERROR (dkms apport): kernel package linux-headers-5.10.0-6-generic is not supported Error! Bad return status for module build on kernel: 5.10.0-6-generic (x86_64) Consult /var/lib/dkms/nvidia/390.138/build/make.log for more information. dpkg: error processing package nvidia-dkms-390 (--configure): installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.10.0-6-generic Errors were encountered while processing: nvidia-dkms-390 E: Sub-process /usr/bin/dpkg returned an error code (1) [Test case] sudo apt install nvidia-dkms-390 [Fix] Fix build errors adding the proper #ifdef to support the new 5.10 includes, function prototypes and data structs. [Regression potential] All the new code is conditional (#ifdef) and it's applied only with 5.10, so there is no risk to break the other kernels (5.8). Moreover, it's worth considering that hirsute should move soon to 5.10. ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-390 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-390 (Ubuntu Hirsute) Importance: Undecided Status: New -- 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/1908099 Title: nvidia-dkms-390 fails to build on unstable / 5.10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-390 source package in Hirsute: New Bug description: [Impact] nvidia-graphics-drivers-390 fails to build against linux 5.10: ERROR (dkms apport): kernel package linux-headers-5.10.0-6-generic is not supported Error! Bad return status for module build on kernel: 5.10.0-6-generic (x86_64) Consult /var/lib/dkms/nvidia/390.138/build/make.log for more information. dpkg: error processing package nvidia-dkms-390 (--configure): installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.10.0-6-generic Errors were encountered while processing: nvidia-dkms-390 E: Sub-process /usr/bin/dpkg returned an error code (1) [Test case] sudo apt install nvidia-dkms-390 [Fix] Fix build errors adding the proper #ifdef to support the new 5.10 includes, function prototypes and data structs. [Regression potential] All the new code is conditional (#ifdef) and it's applied only with 5.10, so there is no risk to break the other kernels (5.8). Moreover, it's worth considering that hirsute should move soon to 5.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1908099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904757] Re: No sound after upgrade to linux-image-5.4.0-54-generic
Please run `apport-collect 1904757`. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904757 Title: No sound after upgrade to linux-image-5.4.0-54-generic Status in linux package in Ubuntu: Incomplete Bug description: Hi Everyone, Just a heads up here... I'm working on Zorin OS 15.3, which is based on Ubuntu Bionic. I upgrade from the linux-image-5.4.0-53-generic kernel to the linux- image-5.4.0-54-generic kernel. After the upgrade to the 5.4.0-54 kernel sound stopped working. Settings showed a "Dummy Output" device and no others. A quick lsmod for snd_hda_intel showed the driver was not loaded. I was not able to load the Intel driver manually. I think there may be some sound driver problems with linux- image-5.4.0-54-generic. The user wanted her sound so I had to remove the 5.4.0-54 kernel. I won't be able to help troubleshoot it. If someone could make a quick pass on the module build results to ensure the drivers are being built for 5.4.0-54, it would be appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906705] Re: The newest ubuntu-kernel 5.4.0-56-generic does not boot on my machine.
Can you please attach `journalctl -b -1` on the next boot of failed boot? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906705 Title: The newest ubuntu-kernel 5.4.0-56-generic does not boot on my machine. Status in linux package in Ubuntu: Incomplete Bug description: The newest ubuntu-kernel 5.4.0-56-generic does not boot on my machine. All older Kubuntu 20.04LTS kernel booted without problems Ryzen 3950X CPU, Asus B450 Booard, Asus 2070super GPU sudo lspci -vvnn > lspci-vvnn.log see attachment ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jseger 2001 F pulseaudio /dev/snd/pcmC0D7p: jseger 2001 F...m pulseaudio /dev/snd/controlC1: jseger 2001 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Dec 3 20:06:40 2020 InstallationDate: Installed on 2020-04-16 (231 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-10 (206 days ago) dmi.bios.date: 06/17/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3103 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3103:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-IGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902457] Re: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade
https://lore.kernel.org/alsa-devel/9i9clq.gp190fsjbr...@canonical.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902457 Title: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Groovy, my sound cards no longer work. Alsa-info says "no soundcards detected" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (465 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 8: Dev 7, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 7, If 0, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-26-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-26-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: False dmi.bios.date: 10/09/2018 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: 8GCN32WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA C930-13IKB dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:br1.32:efr1.32:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB: dmi.product.family: YOGA C930-13IKB dmi.product.name: 81C4 dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB dmi.product.version: Lenovo YOGA C930-13IKB dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (487 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: linux (not installed) Tags: groovy Uname: Linux 5.10.0-051000rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to groovy on 2020-10-30 (24 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (496 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-31-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 RelatedPackageVersions: linux-restricted-modules-5.8.0-31-generic N/A linux-backports-modules-5.8.0-31-generic N/A linux-firmware1.190.1 Tags: groovy Uname: Linux 5.8.0-31-generic x86_64 UpgradeStatus:
[Kernel-packages] [Bug 1907445] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
Still without WiFi, how can I restart wifi service? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1907445 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: Wifi disappear on Macbook Pro 15" ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-32-generic Date: Tue Dec 8 18:14:41 2020 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-05-07 (215 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.3 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1907445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] Re: mircoSD could not operate
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908048] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1908048 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908048 Title: mircoSD could not operate Status in linux package in Ubuntu: Incomplete Bug description: Dear. everyone. I purchased CHWUI gemibook pro ( Intel J4125 CPU ). and I install ubuntu-20.04.1. maybe work fine. gemibook pro has microSD slot. I attached 128GB microSD to gemibook microSD slot. I use command fdisk -l, fdisk /dev/mmcblk2 etc. but sometime work, sometime do not work. this 128GB microSD is able to read/write other notePC. I want to understand that this problem HW or SW, so I send bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
