[Kernel-packages] [Bug 2056303] Re: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c
buntu 6.5.0-21.21~22.04.1-generic 6.5.8 ** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+attachment/5753222/+files/version.log ** Description changed: On one Lenovo machine, using a hwe-22.04 kernel, I get several messages from UBSAN while booting. Previously, on the non-hwe kernel for Jammy, the screen went black shortly after logging in, and that doesn't seem to happen any more, so there is improvement, but it seems still something is going wrong. Attached are the dmesg (where the UBSAN errors are listed), and the output from lspci and the version. + + In the dmesg there is this line, + + [ 19.151801] kfd kfd: amdgpu: STONEY not supported in kfd + + which somewhere was indicated that it would be improved in the hwe + kernel (that's why I tried it). Apparently the issue isn't fully fixex, + but the error seems to be handled better. (Source: + https://forums.linuxmint.com/viewtopic.php?t=410244 ) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056303 Title: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c Status in linux package in Ubuntu: New Bug description: On one Lenovo machine, using a hwe-22.04 kernel, I get several messages from UBSAN while booting. Previously, on the non-hwe kernel for Jammy, the screen went black shortly after logging in, and that doesn't seem to happen any more, so there is improvement, but it seems still something is going wrong. Attached are the dmesg (where the UBSAN errors are listed), and the output from lspci and the version. In the dmesg there is this line, [ 19.151801] kfd kfd: amdgpu: STONEY not supported in kfd which somewhere was indicated that it would be improved in the hwe kernel (that's why I tried it). Apparently the issue isn't fully fixex, but the error seems to be handled better. (Source: https://forums.linuxmint.com/viewtopic.php?t=410244 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056303] Re: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+attachment/5753221/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056303 Title: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c Status in linux package in Ubuntu: New Bug description: On one Lenovo machine, using a hwe-22.04 kernel, I get several messages from UBSAN while booting. Previously, on the non-hwe kernel for Jammy, the screen went black shortly after logging in, and that doesn't seem to happen any more, so there is improvement, but it seems still something is going wrong. Attached are the dmesg (where the UBSAN errors are listed), and the output from lspci and the version. In the dmesg there is this line, [ 19.151801] kfd kfd: amdgpu: STONEY not supported in kfd which somewhere was indicated that it would be improved in the hwe kernel (that's why I tried it). Apparently the issue isn't fully fixex, but the error seems to be handled better. (Source: https://forums.linuxmint.com/viewtopic.php?t=410244 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056303] [NEW] several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c
Public bug reported: On one Lenovo machine, using a hwe-22.04 kernel, I get several messages from UBSAN while booting. Previously, on the non-hwe kernel for Jammy, the screen went black shortly after logging in, and that doesn't seem to happen any more, so there is improvement, but it seems still something is going wrong. Attached are the dmesg (where the UBSAN errors are listed), and the output from lspci and the version. In the dmesg there is this line, [ 19.151801] kfd kfd: amdgpu: STONEY not supported in kfd which somewhere was indicated that it would be improved in the hwe kernel (that's why I tried it). Apparently the issue isn't fully fixex, but the error seems to be handled better. (Source: https://forums.linuxmint.com/viewtopic.php?t=410244 ) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/2056303/+attachment/5753220/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056303 Title: several UBSAN: array-index-out-of-bounds in .../hwmgr/processpptables.c Status in linux package in Ubuntu: New Bug description: On one Lenovo machine, using a hwe-22.04 kernel, I get several messages from UBSAN while booting. Previously, on the non-hwe kernel for Jammy, the screen went black shortly after logging in, and that doesn't seem to happen any more, so there is improvement, but it seems still something is going wrong. Attached are the dmesg (where the UBSAN errors are listed), and the output from lspci and the version. In the dmesg there is this line, [ 19.151801] kfd kfd: amdgpu: STONEY not supported in kfd which somewhere was indicated that it would be improved in the hwe kernel (that's why I tried it). Apparently the issue isn't fully fixex, but the error seems to be handled better. (Source: https://forums.linuxmint.com/viewtopic.php?t=410244 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032164] Re: A general-proteciton exception during guest migration to unsupported PKRU machine
Is there an alternative patch in development? This bug (or at least it seems to be this bug) still affects us. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032164 Title: A general-proteciton exception during guest migration to unsupported PKRU machine Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Triaged Bug description: [Impact] When a host that supports PKRU initiates a guest that lacks PKRU support, the flag is enabled on the guest's fpstate. This information is then passed to userspace through the vcpu ioctl KVM_GET_XSAVE. However, a problem arises when the user opts to migrate the mentioned guest to another machine that does not support PKRU. In this scenario, the new host attempts to restore the guest's fpu registers. Nevertheless, due to the absence of PKRU support on the new host, a general-protection exception takes place, leading to a guest crash. [Fix] The problem is resolved by the following upstream commit: ad856280ddea x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 Additionally, a subsequent fix tackles the migration problem stemming from the earlier commit: a1020a25e697 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES [Test Plan] 1. Set up two machines: one with PKRU support and the other without. 2. Initiate a guest that lacks PKRU support on the machine with PKRU support. 3. Utilize libvirt to migrate the aforementioned guest to a different machine that lacks PKRU support. 4. The error emerges on the destination machine: KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=86cf7970 EBX= ECX=0001 EDX=005b0036 ESI=0087 EDI=0087 EBP=87c03e38 ESP=87c03e18 EIP=86cf7d5e EFL=0246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2023-07-09T03:03:14.911750Z qemu-system-x86_64: terminating on signal 15 from pid 4134 (/usr/sbin/libvirtd) 2023-07-09 03:03:15.312+: shutting down, reason=destroyed [Where problems could occur] The introduced commits will impact the guest migration process, potentially leading to failures and preventing the guest from operating successfully on the migration destination. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024935] [NEW] cpu 2.7x slower on ubuntu server 23.04 riscv64 Nezha/Sipeed images compared to 22.10 on mangopi mq-pro
Public bug reported:
I think I found a bug/regression with the ubuntu server 23.04 riscv64
Nezha/Sipeed kernels.
Somehow, the CPU speed on my mangopi mq pro seems to have decreased by 2.7x
compared to the 22.10 image.
The allwinner D1 should run at 1Ghz, and execute a single add per cycle.
On 22.10 I was able to confirm that executing `1024*1024*1024` add instructions
took roughly a second, but on 23.04 it took 2.7 seconds (both fresh installs,
with the same code [1]).
There were no resource hungry background processes running, when I
checked top.
I also binary patched the opensbi image afterward, to disable mcountinhibit for
`rdcycle`, and confirmed that even the hardware cycle counter was slower than
1Ghz. [2]
One second had 410398820 cycles instead of something closer to the expected
1073741824.
On suggestion from the #ubuntu webchat, I also tested adding
`mitigations=off` to the linux cmd options, but that didn't change
anything.
[1]
// test.c
#include
#include
int main(void)
{
for (int i = 0; i < 10; ++i) {
clock_t beg = clock();
extern void foo(void);
foo();
printf("%f\n", (clock() - beg) * 1.0/CLOCKS_PER_SEC);
}
}
// test.S
.text
.global foo
foo:
li t0, (1024*1024*1024/(8*32))
1:
.rept 32
add a1, a1, a0
add a2, a2, a1
add a3, a3, a2
add a4, a4, a3
add a5, a5, a4
add a6, a6, a5
add a7, a7, a6
add a0, a0, a7
.endr
addit0, t0, -1
bnezt0, 1b
ret
$ gcc -Ofast -march=rv64gc test.* && ./a.out
[2] https://github.com/camel-cdr/rvv-d1/#extra-enable-rdcycle
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-5.19.0-1009-allwinner 5.19.0-1009.9
ProcVersionSignature: User Name 5.19.0-1009.9-allwinner 5.19.17
Uname: Linux 5.19.0-1009-allwinner riscv64
ApportVersion: 2.26.1-0ubuntu2
Architecture: riscv64
CasperMD5CheckResult: unknown
CloudArchitecture: riscv64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20230415.2
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
Date: Fri Jun 23 20:10:14 2023
ProcCpuinfoMinimal:
processor : 0
hart : 0
isa: rv64imafdc
mmu: sv39
uarch : thead,c906
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=st-256color
XDG_RUNTIME_DIR=
SourcePackage: linux-allwinner
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: linux-allwinner (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug cloud-image lunar riscv64
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-allwinner in Ubuntu.
https://bugs.launchpad.net/bugs/2024935
Title:
cpu 2.7x slower on ubuntu server 23.04 riscv64 Nezha/Sipeed images
compared to 22.10 on mangopi mq-pro
Status in linux-allwinner package in Ubuntu:
New
Bug description:
I think I found a bug/regression with the ubuntu server 23.04 riscv64
Nezha/Sipeed kernels.
Somehow, the CPU speed on my mangopi mq pro seems to have decreased by 2.7x
compared to the 22.10 image.
The allwinner D1 should run at 1Ghz, and execute a single add per cycle.
On 22.10 I was able to confirm that executing `1024*1024*1024` add
instructions took roughly a second, but on 23.04 it took 2.7 seconds (both
fresh installs, with the same code [1]).
There were no resource hungry background processes running, when I
checked top.
I also binary patched the opensbi image afterward, to disable mcountinhibit
for `rdcycle`, and confirmed that even the hardware cycle counter was slower
than 1Ghz. [2]
One second had 410398820 cycles instead of something closer to the expected
1073741824.
On suggestion from the #ubuntu webchat, I also tested adding
`mitigations=off` to the linux cmd options, but that didn't change
anything.
[1]
// test.c
#include
#include
int main(void)
{
for (int i = 0; i < 10; ++i) {
clock_t beg = clock();
extern void foo(void);
foo();
printf("%f\n", (clock() - beg) * 1.0/CLOCKS_PER_SEC);
}
}
// test.S
.text
.global foo
foo:
li t0, (1024*1024*1024/(8*32))
1:
.rept 32
add a1, a1, a0
add a2, a2, a1
add a3, a3, a2
add a4, a4, a3
add a5, a5, a4
add a6, a6, a5
add a7, a7, a6
add a0, a0, a7
.endr
addit0, t0, -1
bnezt0, 1b
ret
$ gcc -Ofast -march=rv64gc test.* && ./a.out
[2] https://github.com/camel-cdr/rvv-d1/#extra-enable-rdcycle
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-5.19.0-1009-allwinner 5.19.0-1009.9
ProcVersionSignature: User Name
[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images
installed mentioned kernel version an did a memory hot-plugging test which was sucessfull kernel version: root@ubuntu:/boot# uname -a Linux ubuntu 5.4.0-1040-kvm #41-Ubuntu SMP Fri May 14 20:43:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux module in kernel configuration is set: root@ubuntu:/boot# grep -i CONFIG_ACPI_HOTPLUG_MEMORY /boot/config-5.4.0-1040-kvm CONFIG_ACPI_HOTPLUG_MEMORY=y memory before memory hot-plugging: root@ubuntu:/boot# free -k totalusedfree shared buff/cache available Mem:4027608 149232 3621316 480 257060 3828108 Swap: 0 0 0 memory after memory hot-plugging: root@ubuntu:/boot# free -k totalusedfree shared buff/cache available Mem: 10319064 249788 9802568 480 266708 9960284 Swap: 0 0 0 ** 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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux-kvm source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Status in linux-kvm source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux-kvm source package in Hirsute: Fix Released Bug description: SRU Justification [Impact] Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU [Test Plan] Boot a kernel with CONFIG_ACPI_HOTPLUG_MEMORY enabled. Check that requested memory has been added. [Where problems could occur] Adding memory could fail, or cause other configurations issues. Regressions seem unlikely since this config option is enabled in all cloud kernels except linux-azure. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images
root@ubuntu:~# cat /etc/apt/sources.list.d/ubuntu-focal-proposed.list # Enable Ubuntu proposed archive deb http://archive.ubuntu.com/ubuntu/ focal-proposed restricted main multiverse universe root@ubuntu:~# apt policy linux-image-kvm linux-image-kvm: Installed: 5.4.0.1033.31 Candidate: 5.4.0.1039.37 Version table: 5.4.0.1040.38 400 400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 5.4.0.1039.37 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages *** 5.4.0.1033.31 100 100 /var/lib/dpkg/status 5.4.0.1009.9 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux-kvm source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Status in linux-kvm source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux-kvm source package in Hirsute: Fix Released Bug description: SRU Justification [Impact] Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU [Test Plan] Boot a kernel with CONFIG_ACPI_HOTPLUG_MEMORY enabled. Check that requested memory has been added. [Where problems could occur] Adding memory could fail, or cause other configurations issues. Regressions seem unlikely since this config option is enabled in all cloud kernels except linux-azure. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images
updated kernel: ... Setting up linux-image-5.4.0-1039-kvm (5.4.0-1039.40) ... I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.0-1039-kvm I: /boot/initrd.img is now a symlink to initrd.img-5.4.0-1039-kvm ... unfortunately the kernel config is still not set: root@ubuntu:~# grep -i CONFIG_ACPI_HOTPLUG_MEMORY /boot/config-5.4.0-1039-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set ** Tags removed: verification-done-focal ** Tags added: verification-failed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux-kvm source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Status in linux-kvm source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux-kvm source package in Hirsute: Fix Released Bug description: SRU Justification [Impact] Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU [Test Plan] Boot a kernel with CONFIG_ACPI_HOTPLUG_MEMORY enabled. Check that requested memory has been added. [Where problems could occur] Adding memory could fail, or cause other configurations issues. Regressions seem unlikely since this config option is enabled in all cloud kernels except linux-azure. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images
** 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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux-kvm source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Status in linux-kvm source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux-kvm source package in Hirsute: Fix Released Bug description: SRU Justification [Impact] Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU [Test Plan] Boot a kernel with CONFIG_ACPI_HOTPLUG_MEMORY enabled. Check that requested memory has been added. [Where problems could occur] Adding memory could fail, or cause other configurations issues. Regressions seem unlikely since this config option is enabled in all cloud kernels except linux-azure. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images
We tested the kernel release 5.4.0-1040-kvm and it looks much more better now. Memory gets added automaticly to the system. Also all events are visible now: monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[14203.153504] add /devices/system/memory/memory56 (memory) KERNEL[14203.153549] add /devices/system/memory/memory57 (memory) KERNEL[14203.153557] add /devices/system/memory/memory58 (memory) KERNEL[14203.153564] add /devices/system/memory/memory59 (memory) KERNEL[14203.153571] add /devices/system/memory/memory60 (memory) KERNEL[14203.153578] add /devices/system/memory/memory61 (memory) KERNEL[14203.153585] add /devices/system/memory/memory62 (memory) KERNEL[14203.153592] add /devices/system/memory/memory63 (memory) KERNEL[14203.158264] online /devices/system/memory/memory56 (memory) UDEV [14203.158904] add /devices/system/memory/memory56 (memory) KERNEL[14203.159596] online /devices/system/memory/memory58 (memory) UDEV [14203.159619] add /devices/system/memory/memory58 (memory) UDEV [14203.160208] online /devices/system/memory/memory58 (memory) KERNEL[14203.160232] online /devices/system/memory/memory60 (memory) UDEV [14203.160391] add /devices/system/memory/memory60 (memory) UDEV [14203.160688] online /devices/system/memory/memory56 (memory) UDEV [14203.161505] online /devices/system/memory/memory60 (memory) KERNEL[14203.161745] online /devices/system/memory/memory62 (memory) UDEV [14203.161818] add /devices/system/memory/memory62 (memory) KERNEL[14203.162450] online /devices/system/memory/memory63 (memory) UDEV [14203.162561] add /devices/system/memory/memory63 (memory) UDEV [14203.162769] online /devices/system/memory/memory62 (memory) UDEV [14203.163352] online /devices/system/memory/memory63 (memory) KERNEL[14203.172589] online /devices/system/memory/memory61 (memory) UDEV [14203.172722] add /devices/system/memory/memory61 (memory) UDEV [14203.173936] online /devices/system/memory/memory61 (memory) KERNEL[14203.180667] online /devices/system/memory/memory59 (memory) UDEV [14203.180817] add /devices/system/memory/memory59 (memory) UDEV [14203.182015] online /devices/system/memory/memory59 (memory) KERNEL[14203.188645] online /devices/system/memory/memory57 (memory) UDEV [14203.188715] add /devices/system/memory/memory57 (memory) UDEV [14203.189542] online /devices/system/memory/memory57 (memory) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux-kvm source package in Focal: In Progress Status in linux source package in Groovy: Fix Released Status in linux-kvm source package in Groovy: In Progress Status in linux source package in Hirsute: Fix Released Status in linux-kvm source package in Hirsute: In Progress Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101
[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images
qemu -name $ -m 1024,slots=255,maxmem=256G -M pc-i440fx-2.7 -enable-kvm -no-user-config -nodefaults -rtc base=utc -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0,max-bytes=1024,period=1000,bus=pci.0,addr=0x3 -netdev tap,ifname=$,id=hostnet6,vhost=on,vhostforce=on,vnet_hdr=on,script=no,downscript=no -device virtio-net-pci,netdev=hostnet6,id=net6,mac=$,bus=pci.0,addr=0x6 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc $ -vga qxl -cpu Haswell,+ssbd,+spec-ctrl,+vmx,+md-clear,+pdpe1gb,+stibp,-vmx-entry-load-perf-global-ctrl,-vmx-exit-load-perf-global-ctrl -smp 4,sockets=32,cores=1,maxcpus=64,threads=2 -object iothread,id=iothread5 -drive file=$,if=none,id=drive-virtio-disk5,format=raw,snapshot=off,aio=native,cache=none -device virtio-blk-pci,serial=$,bus=pci.0,addr=0x5,drive=drive-virtio-disk5,iothread=iothread5,num-queues=2,id=virtio-disk5,bootindex=1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux-kvm source package in Focal: In Progress Status in linux source package in Groovy: Fix Released Status in linux-kvm source package in Groovy: In Progress Status in linux source package in Hirsute: Fix Released Status in linux-kvm source package in Hirsute: In Progress Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images
Well for memory hotplug the -m paramter is important. Here is how i started the VM: qemu -name myfancyvm -m 1024,slots=255,maxmem=256G... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux-kvm source package in Focal: In Progress Status in linux source package in Groovy: Fix Released Status in linux-kvm source package in Groovy: In Progress Status in linux source package in Hirsute: Fix Released Status in linux-kvm source package in Hirsute: In Progress Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489834/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489832/+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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489833/+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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489831/+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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489830/+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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489829/+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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489828/+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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489827/+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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489826/+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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images
apport information ** Tags added: apport-collected focal uec-images ** Description changed: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 + --- + ProblemType: Bug + AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + CRDA: N/A + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: Error: command ['lsusb'] failed with exit code 1: + Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: + MachineType: QEMU Standard PC (i440FX + PIIX, 1996) + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 + ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-1038-kvm N/A + linux-backports-modules-5.4.0-1038-kvm N/A + linux-firmware N/A + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal uec-images + Uname: Linux 5.4.0-1038-kvm x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: False + dmi.bios.date: 04/01/2014 + dmi.bios.vendor: SeaBIOS + dmi.bios.version: 1.12.0-1 + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: pc-i440fx-2.7 + dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: + dmi.product.name: Standard PC (i440FX + PIIX, 1996) + dmi.product.version: pc-i440fx-2.7 + dmi.sys.vendor: QEMU ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1925008/+attachment/5489825/+files/AudioDevicesInUse.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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A
[Kernel-packages] [Bug 1890641] Re: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169
I had also the Prblem with the missing of /lib/firmware/rtl_nic/rtl8125a-3.fw Then i have found the rtl8125a-3.fw on git https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/rtl_nic then download and copy in the directory /lib/firmware/rtl_nic/ and the command $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.4.0-42-generic reboot and all is ok -- 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/1890641 Title: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 Status in linux-firmware package in Ubuntu: New Bug description: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 after running sudo apt upgrade in ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 22:38:31 2020 InstallationDate: Installed on 2019-06-16 (417 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-03-08 22:54:00.439353 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1890641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791893] Re: Trailing garbage data when sending on an AF_PACKET socket
No Problem in 4.15.0-32 and before. Problem since 4.15.0-33-generic with raw socket => EtherCAT/SOEM (Simple Open Ethercat Master). I can confirm it's fixed in 4.15.0-38-generic (SOEM ok). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791893 Title: Trailing garbage data when sending on an AF_PACKET socket Status in linux package in Ubuntu: Fix Released Bug description: When sending an Ethernet frame on an packet socket (AF_PACKET, SOCK_RAW), an additional 14 bytes of trailing data is sent on the interface. The extra 14 bytes are present regardless of the packet size. The extra data could be garbage/uninitialised kernel memory. Expected result: The raw Ethernet frame is sent on the interface. Actual result: The raw Ethernet frame plus an additional 14 bytes of unknown data is sent on the interface. Steps to reproduce: The attached test program inject.c can be used to reproduce the issue. # In window 1. Send an EAP packet without any payload. gcc inject.c -o inject sudo ./inject lo # Simultaneously in window 2. Tcpdump shows a payload of 14 bytes. sudo tcpdump -i lo -enlx 07:45:45.005652 02:00:00:00:00:01 > 02:00:00:00:00:00, ethertype EAPOL (0x888e), length 28: EAP packet (0) v64, len 0 0x: 4000 4000 Running strace on the "inject" program shows that send(2) is indeed called with the correct buffer size. The extra 14 bytes appear to be added by the kernel, and this might leak kernel memory. Ubuntu release: Ubuntu 18.04.1 LTS Package version: 4.15.0-33.36 The issue could not be reproduced on linux-image-4.15.0-22-generic or linux-image-4.15.0-23-generic. uname -a: Linux ubuntu 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johan 1763 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7d5f82e0-635f-4c53-a80d-11b0f47d27fd InstallationDate: Installed on 2018-01-08 (245 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: lxcbr0no wireless extensions. enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=54834e7a-dbec-4d9f-b662-6107cecc8a86 ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 RfKill: StagingDrivers: vboxvideo Tags: bionic staging Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-06-27 (76 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Hello, have a Telcast F7 should be also the Touchpad SYNA3602, but not working with Kernel 4.15035. Does anyone know when the patch comes in the current Ubuntu kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776155] Re: Touchpad detected as SYNA3602, does not work at all.
Does anyone know when the patch in the official Ubuntu 18.04 kernel comes? Thanks Olaf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776155 Title: Touchpad detected as SYNA3602, does not work at all. Status in linux package in Ubuntu: Confirmed Bug description: On my cheaper-end slimline laptop/netbook the touchpad is (I think wrongly) detected by Linux to be the SYNA 3602. Anyway it does not work at all, neither touchpad nor buttons. Freshly installed Ubuntu 18.04 system. External mouse works fine. It seems that there is a bug reported on a similar issue, although I can not confirm that my touchpad hardware is exactly the same: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688625 If so, there may be a whole new generation of slimline Windows 10 netbooks that have this problem. martin@alanah:~$ cat /proc/bus/input/devices I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0018 Vendor=0911 Product=5288 Version=0100 N: Name="SYNA3602:00 0911:5288 Touchpad" P: Phys=i2c-SYNA3602:00 S: Sysfs=/devices/pci:00/:00:16.1/i2c_designware.1/i2c-5/i2c-SYNA3602:00/0018:0911:5288.0001/input/input15 U: Uniq= H: Handlers=mouse0 event14 B: PROP=5 B: EV=1b B: KEY=e420 3 0 0 0 0 B: ABS=2608003 B: MSC=20 I: Bus=0003 Vendor=045e Product=00b9 Version=0111 N: Name="Microsoft Microsoft USB Wireless Mouse" P: Phys=usb-:00:15.0-1/input0 S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-1/1-1:1.0/0003:045E:00B9.0002/input/input16 U: Uniq= H: Handlers=mouse1 event15 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=1c3 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Mon Jun 11 07:57:56 2018 InstallationDate: Installed on 2018-04-25 (46 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1536 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-25 (48 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: Multicom Multicom U230 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c7a82fee-6e9d-491d-a38d-f5d6bdb4a930 ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: ORO10x.WP313P.NHNAUHL01 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrORO10x.WP313P.NHNAUHL01:bd09/15/2017:svnMulticom:pnMulticomU230:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: U-series dmi.product.name: Multicom U230 dmi.product.version: Default string dmi.sys.vendor: Multicom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777245] Re: X freezes with kernel 4.15.0-23-generic (AMDGPU)
@jsalisbury: I had the machine tested with this kernel: Linux xa-xubu 4.18.0-041800rc1-generic #201806162031 SMP Sun Jun 17 00:34:22 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux that I found via your link [0]. The result is that in this kernel, the problem is gone. So that sounds like good news! I think there was another commenter asking me to try a (probably different) upstream kernel, but it seems gone now. To them I can report that I didn't try building a kernel myself, but hopefully their proposal was close enough to using the Ubuntu mainline kernel that this test gives them the answer they are looking for. ** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) Status in linux package in Ubuntu: Confirmed Bug description: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. I filed this bug using apport-cli, running the older (working) kernel, not the newer (failing) one. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296] do_vfs_ioctl+0xa8/0x630 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300] ? __schedule+0x29f/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304] SyS_ioctl+0x79/0x90 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309] do_syscall_64+0x73/0x130 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 EFLAGS: 3246 ORIG_RAX: 0010 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 0002 RCX: 7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: c0286448 RDI: 000e Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 00010144 R09:
[Kernel-packages] [Bug 1777245] Re: X freezes with kernel 4.15.0-23-generic (AMDGPU)
Yes, the problem started after an upgrade. From what I can see in the logs it seems that first the machine was upgraded from Ubuntu 17.10 to 18.04, apparently without problem. Then a few days later, the working kernel Ubuntu 4.13.0-43.48-generic 4.13.16 was replaced by 4.15.0-23.25-generic 4.15.18 which fails. It will not be so easy to test another kernel, but I'll try. It will definitely be some days before I can report a result, I suspect. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) Status in linux package in Ubuntu: Incomplete Bug description: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. I filed this bug using apport-cli, running the older (working) kernel, not the newer (failing) one. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296] do_vfs_ioctl+0xa8/0x630 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300] ? __schedule+0x29f/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304] SyS_ioctl+0x79/0x90 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309] do_syscall_64+0x73/0x130 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 EFLAGS: 3246 ORIG_RAX: 0010 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 0002 RCX: 7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: c0286448 RDI: 000e Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 00010144 R09: 000a Jun 15 23:26:23 xa-xubu kernel: [ 2417.563328] R10: 0039 R11: 3246 R12: c0286448 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563330] R13: 000e R14: 55e820965f20 R15: 0 which seems to point to some in-kernel AMD GPU
[Kernel-packages] [Bug 1777245] Re: X freezes with kernel 4.15.0-23-generic (AMDGPU)
Oops, the above message was not supposed to be mailed 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/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) Status in linux package in Ubuntu: Confirmed Bug description: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. I filed this bug using apport-cli, running the older (working) kernel, not the newer (failing) one. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296] do_vfs_ioctl+0xa8/0x630 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300] ? __schedule+0x29f/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304] SyS_ioctl+0x79/0x90 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309] do_syscall_64+0x73/0x130 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 EFLAGS: 3246 ORIG_RAX: 0010 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 0002 RCX: 7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: c0286448 RDI: 000e Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 00010144 R09: 000a Jun 15 23:26:23 xa-xubu kernel: [ 2417.563328] R10: 0039 R11: 3246 R12: c0286448 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563330] R13: 000e R14: 55e820965f20 R15: 0 which seems to point to some in-kernel AMD GPU driver. Since the problem seems to disappear when switching back to the previous kernel, I filed this as a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64
[Kernel-packages] [Bug 1777245] Re: stom
On Sat 16 Jun 2018 at 14:31:49 +0200, Guus en Anneke wrote: > Hoi Olaf, > eerst startte ik op met > Ubuntu met Linux 4.15.0-23 generic(recovery mode) > Ik kreeg een lange lijst met data. Toen herstelmenu, waarna rare dingen, > gekleurde strepen van letters. > > Opnieuw opgestart met > Ubuntu met Linux 4.13.0-43 generic > Gister ook met deze opgestart. Was nummer 3 in het lijstje en leek op nr 1. > vandaar dat ik vandaag met nr 2 op ging starten om te zien wat die deed.Niet > goed dus. > Ik heb een bug ingediend bij Ubuntu; je kan 'm nalezen op https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777245 Daarin staat ook dat je 7 dagen geleden een nieuwe XUbuntu-versie hebt geinstalleerd (van 17.10 naar 18.04)... daar had ik beter even bij kunnen meekijken! Ik heb dat namelijk op mijn laptop ook gedaan en dat was niet geheel zonder problemen... Ik heb ook de 4.13.0-43 standaard gemaakt voor het opstarten (hopelijk). Wanneer er een nieuwe versie uitkomt, moet je die eens proberen. Ik merk het hier vanzelf want mijn laptop heeft dus dezelfde Ubuntu-versie. Ik zal laten weten wanneer het zover is. Voor de 4.15.0-23-versie heb ik een opstart-optie toegevoegd die ik ergens tegenkwam. Iemand met soortgelijke problemen had er baat bij; als je tijd over hebt moet je maar eens die versie proberen (ik denk niet dat je verschil ziet in het menu) en zien of het helpt. Ik hoor graag wat het effekt is (sukses of niet), dan kan ik dat bij de bugmelding toevoegen. Groetjes, -Olaf. -- ___ Olaf 'Rhialto' Seibert -- Wayland: Those who don't understand X \X/ rhialto/at/falu.nl -- are condemned to reinvent it. Poorly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) Status in linux package in Ubuntu: Confirmed Bug description: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. I filed this bug using apport-cli, running the older (working) kernel, not the newer (failing) one. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290]
[Kernel-packages] [Bug 1777245] Re: X freezes with kernel 4.15.0-23-generic (AMDGPU)
** Attachment added: "extract from kernel log for 4.15.0.23-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777245/+attachment/5153352/+files/dmesg-4.15.0-23-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) Status in linux package in Ubuntu: Confirmed Bug description: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. I filed this bug using apport-cli, running the older (working) kernel, not the newer (failing) one. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296] do_vfs_ioctl+0xa8/0x630 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300] ? __schedule+0x29f/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304] SyS_ioctl+0x79/0x90 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309] do_syscall_64+0x73/0x130 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 EFLAGS: 3246 ORIG_RAX: 0010 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 0002 RCX: 7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: c0286448 RDI: 000e Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 00010144 R09: 000a Jun 15 23:26:23 xa-xubu kernel: [ 2417.563328] R10: 0039 R11: 3246 R12: c0286448 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563330] R13: 000e R14: 55e820965f20 R15: 0 which seems to point to some in-kernel AMD GPU driver. Since the problem seems to disappear when switching back to the previous kernel, I filed this as a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu
[Kernel-packages] [Bug 1777245] Re: X freezes with kernel 4.15.0-23-generic (AMDGPU)
** Summary changed: - X freezes + X freezes with kernel 4.15.0-23-generic (AMDGPU) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777245 Title: X freezes with kernel 4.15.0-23-generic (AMDGPU) Status in linux package in Ubuntu: Confirmed Bug description: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. I filed this bug using apport-cli, running the older (working) kernel, not the newer (failing) one. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296] do_vfs_ioctl+0xa8/0x630 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300] ? __schedule+0x29f/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304] SyS_ioctl+0x79/0x90 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309] do_syscall_64+0x73/0x130 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 EFLAGS: 3246 ORIG_RAX: 0010 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 0002 RCX: 7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: c0286448 RDI: 000e Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 00010144 R09: 000a Jun 15 23:26:23 xa-xubu kernel: [ 2417.563328] R10: 0039 R11: 3246 R12: c0286448 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563330] R13: 000e R14: 55e820965f20 R15: 0 which seems to point to some in-kernel AMD GPU driver. Since the problem seems to disappear when switching back to the previous kernel, I filed this as a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2
[Kernel-packages] [Bug 1777245] Re: X freezes
** Description changed: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. + + I filed this bug using apport-cli, running the older (working) kernel, + not the newer (failing) one. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296] do_vfs_ioctl+0xa8/0x630 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300] ? __schedule+0x29f/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304] SyS_ioctl+0x79/0x90 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309] do_syscall_64+0x73/0x130 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 EFLAGS: 3246 ORIG_RAX: 0010 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 0002 RCX: 7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: c0286448 RDI: 000e Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 00010144 R09: 000a Jun 15 23:26:23 xa-xubu kernel: [ 2417.563328] R10: 0039 R11: 3246 R12: c0286448 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563330] R13: 000e R14: 55e820965f20 R15: 0 which seems to point to some in-kernel AMD GPU driver. Since the problem seems to disappear when switching back to the previous kernel, I filed this as a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rhialto 21222 F pulseaudio /dev/snd/controlC0: rhialto 21222 F pulseaudio Date: Sat Jun 16 16:03:46 2018 InstallationDate: Installed on 2017-10-29 (230 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" -
[Kernel-packages] [Bug 1777245] [NEW] X freezes
Public bug reported: This is on my parents machine; I only have remote access and not continuously, so this may slow down providing additional information. Since the latest kernel upgrade (from Linux version 4.13.0-43-generic (buildd@lgw01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 (Ubuntu 4.13.0-43.48-generic 4.13.16) to Linux version 4.15.0-23-generic (buildd@lgw01-amd64-055) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 (Ubuntu 4.15.0-23.25-generic 4.15.18) the machine appears to freezes some time soon after booting. It is just X; the machine is still reachable via ssh. In /var/log/kernel I can see the following: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562386] INFO: task Xorg:757 blocked for more than 120 seconds. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562396] Not tainted 4.15.0-23-generic #25-Ubuntu Jun 15 23:26:23 xa-xubu kernel: [ 2417.562399] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 15 23:26:23 xa-xubu kernel: [ 2417.562403] XorgD0 757 724 0x0044 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562408] Call Trace: Jun 15 23:26:23 xa-xubu kernel: [ 2417.562424] __schedule+0x297/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562430] ? __kfifo_in+0x37/0x50 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562434] schedule+0x2c/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562559] amd_sched_entity_push_job+0xad/0xf0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562565] ? wait_woken+0x80/0x80 Jun 15 23:26:23 xa-xubu kernel: [ 2417.562653] amdgpu_job_submit+0x9f/0xc0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562723] amdgpu_vm_bo_update_mapping+0x389/0x3f0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562793] ? amdgpu_vm_it_iter_first+0x40/0x40 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562863] amdgpu_vm_bo_update+0x325/0x5b0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562930] amdgpu_gem_va_ioctl+0x524/0x540 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.562962] ? drm_gem_handle_create_tail+0x120/0x190 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563028] ? amdgpu_gem_create_ioctl+0xc1/0x270 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563096] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563115] drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563134] ? drm_ioctl_kernel+0x5f/0xb0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563154] drm_ioctl+0x31b/0x3d0 [drm] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563220] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563225] ? update_load_avg+0x57f/0x6e0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563231] ? futex_wake+0x8f/0x180 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563290] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] Jun 15 23:26:23 xa-xubu kernel: [ 2417.563296] do_vfs_ioctl+0xa8/0x630 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563300] ? __schedule+0x29f/0x8b0 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563304] SyS_ioctl+0x79/0x90 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563309] do_syscall_64+0x73/0x130 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563313] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563317] RIP: 0033:0x7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563319] RSP: 002b:7fff67e69aa8 EFLAGS: 3246 ORIG_RAX: 0010 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563322] RAX: ffda RBX: 0002 RCX: 7fbd7ddcf5d7 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563324] RDX: 7fff67e69af0 RSI: c0286448 RDI: 000e Jun 15 23:26:23 xa-xubu kernel: [ 2417.563326] RBP: 7fff67e69af0 R08: 00010144 R09: 000a Jun 15 23:26:23 xa-xubu kernel: [ 2417.563328] R10: 0039 R11: 3246 R12: c0286448 Jun 15 23:26:23 xa-xubu kernel: [ 2417.563330] R13: 000e R14: 55e820965f20 R15: 0 which seems to point to some in-kernel AMD GPU driver. Since the problem seems to disappear when switching back to the previous kernel, I filed this as a kernel bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rhialto 21222 F pulseaudio /dev/snd/controlC0: rhialto 21222 F pulseaudio Date: Sat Jun 16 16:03:46 2018 InstallationDate: Installed on 2017-10-29 (230 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: enp1s0no wireless extensions. lono wireless extensions. MachineType: LENOVO 90G9001RNY ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
I can also confirm this bug with Ubuntu 16.04 and kernel 4.10.0-27-generic on a Dell XPS 13 from 2015. I had a system freeze yesterday and today. In the months before I never experienced any problems despite heavy swapping. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: fff97000 R15: 8000 Apr 7 11:20:28 doe kernel: [26003.797440] FS: 7f70bd1df6c0() GS:93c0() knlGS: Apr 7 11:20:28 doe kernel: [26003.797470] CS: 0010 DS: ES: CR0: 80050033 Apr 7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 00016942 CR4: 003406f0 Apr 7 11:20:28 doe kernel: [26003.797523] Call Trace: Apr
[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
Attached is the acpi-dump from my Asus G752VM running Ubuntu 16.04. Same Touchpad (ELAN 0x3043, Version 0x100) as the above G752VS. ** Attachment added: "acpi-dump" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653456/+attachment/4840455/+files/acpi-dump -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) Status in linux package in Ubuntu: Confirmed Bug description: Non-Optimus laptop ASUS G752VS-GC063D-CST256. 17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS. Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and 17.04, among other problems I found that touchpad and Fn keys (all except volume control) doesn't work on my brand new ASUS G752VS. It is very hard even to try Ubuntu 16.10 and 17.04 because of the missing mouse pointer. This problem must be related to a video driver because if after installing one is capable to install Nvidia drivers - problem is solved. This problem doesn't exist both while trying and installing Ubuntu 16.04.1! I'm currently on Windows 10, and this bug report is made from Ubuntu 16.04.1 LiveCD. dmesg | grep -i elan [ 101.082929] input: ELAN1203:00 04F3:3043 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11 [ 101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00 xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ G-SPY USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=13 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=14 [slave pointer (2)] ⎜ ↳ ELAN1203:00 04F3:3043 Touchpad id=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ G-SPY USB Gaming Mouse id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=11 [slave keyboard (3)] ↳ ASASTeK COMPUTER INC. ROG MacroKey id=12 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04d9 Product=a070 Version=0110 N: Name="G-SPY USB Gaming Mouse" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04D9:A070.0001/input/input5 U: Uniq= H: Handlers=sysrq kbd event5 leds B: PROP=0 B: EV=120013 B:
[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
My dmesg | grep -i elan and xinput list looks exactly like OP above - except that I have a different USB mouse attached: Microsoft Microsoft 3-Button Mouse with IntelliEye™ id=9[slave pointer (2)] That mouse worked right away - installing Ubuntu 16.04.1 and then the Nvidia proprietary drivers was no problem. Almost everything works fine - except Touchpad and the Fn keys. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) Status in linux package in Ubuntu: Confirmed Bug description: Non-Optimus laptop ASUS G752VS-GC063D-CST256. 17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS. Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and 17.04, among other problems I found that touchpad and Fn keys (all except volume control) doesn't work on my brand new ASUS G752VS. It is very hard even to try Ubuntu 16.10 and 17.04 because of the missing mouse pointer. This problem must be related to a video driver because if after installing one is capable to install Nvidia drivers - problem is solved. This problem doesn't exist both while trying and installing Ubuntu 16.04.1! I'm currently on Windows 10, and this bug report is made from Ubuntu 16.04.1 LiveCD. dmesg | grep -i elan [ 101.082929] input: ELAN1203:00 04F3:3043 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11 [ 101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00 xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ G-SPY USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=13 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=14 [slave pointer (2)] ⎜ ↳ ELAN1203:00 04F3:3043 Touchpad id=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ G-SPY USB Gaming Mouse id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=11 [slave keyboard (3)] ↳ ASASTeK COMPUTER INC. ROG MacroKey id=12 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04d9 Product=a070 Version=0110 N: Name="G-SPY USB Gaming Mouse" P: Phys=usb-:00:14.0-2/input0 S:
[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
Same with Asus G752VM running Ubuntu 16.04. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) Status in linux package in Ubuntu: Confirmed Bug description: Non-Optimus laptop ASUS G752VS-GC063D-CST256. 17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS. Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and 17.04, among other problems I found that touchpad and Fn keys (all except volume control) doesn't work on my brand new ASUS G752VS. It is very hard even to try Ubuntu 16.10 and 17.04 because of the missing mouse pointer. This problem must be related to a video driver because if after installing one is capable to install Nvidia drivers - problem is solved. This problem doesn't exist both while trying and installing Ubuntu 16.04.1! I'm currently on Windows 10, and this bug report is made from Ubuntu 16.04.1 LiveCD. dmesg | grep -i elan [ 101.082929] input: ELAN1203:00 04F3:3043 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11 [ 101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00 xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ G-SPY USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=13 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=14 [slave pointer (2)] ⎜ ↳ ELAN1203:00 04F3:3043 Touchpad id=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ G-SPY USB Gaming Mouse id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=11 [slave keyboard (3)] ↳ ASASTeK COMPUTER INC. ROG MacroKey id=12 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04d9 Product=a070 Version=0110 N: Name="G-SPY USB Gaming Mouse" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04D9:A070.0001/input/input5 U: Uniq= H: Handlers=sysrq kbd event5 leds B: PROP=0 B: EV=120013 B: KEY=e080ffdf01cf fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=04d9 Product=a070 Version=0110 N: Name="G-SPY USB Gaming Mouse" P:
