[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: Fix Committed Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS -
[Kernel-packages] [Bug 1855811] Re: container from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
Issue found on 5.4.0-1016.16-gcp ** Tags added: 5.4 gocal ** Tags removed: gocal ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855811 Title: container from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP # k8s.io/kubernetes/pkg/kubelet/container pkg/kubelet/container/sync_result_test.go:48:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult pkg/kubelet/container/sync_result_test.go:56:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult pkg/kubelet/container/sync_result_test.go:66:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult []*k8s.io/kubernetes/pkg/kubelet/container.Pod FAIL k8s.io/kubernetes/pkg/kubelet/container [build failed] This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855810] Re: podautoscaler from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
Issue found on 5.4.0-1016.16-gcp ** Tags added: 5.4 sru-20200608 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855810 Title: podautoscaler from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP Test failed with: panic: test timed out after 2m0s (error message too long, please refer to the attachment) /tmp/kubernetes.git/_output/local/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:69 +0x62 FAIL k8s.io/kubernetes/pkg/controller/podautoscaler 120.039s This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876875] Update Released
The verification of the Stable Release Update for grub2-signed has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1876875 Title: Improve download-signed script to support current & grub2 Status in grub2-signed package in Ubuntu: Fix Released Status in linux-signed package in Ubuntu: Fix Committed Status in s390-tools-signed package in Ubuntu: Won't Fix Status in grub2-signed source package in Focal: Fix Released Bug description: [Impact] * Improve and generalise download-signed script to allow using it with any signed binaries we care about * Add support to download simply the most current version * Add support to download /uefi/ signed binaries * Clean up arg parsing, add help, drop unused statements & imports. [Test Case] * Test downloading signed kernel works with public & private archives * Test that rebuilt signed .debs are the same [Regression Potential] * This is a built time script, as long the binaries are downloaded & packaged up the same, there is no end-user facing impact. [Other Info] * With these changes, download-signed script can be used by s390-tools-signed & grub2-signed, as well as all the kernels. * This is needed to support resigning with different keys for different ubuntu products. For example, UC20 uses the same grub binaries, but wants an additional trustpath to UC20 CA for grade:secured core images. At the moment creating such a signature is only possible via a round-trip in a PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1876875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working
Running 5.4.0-37-generic adding "drm.vblankoffdelay=1 acpi_backlight=vendor" to my grub config did not work, unfortunatelly -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822581 Title: HP 1030 G3 fn-keys not working Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn key combinations are only working partially. What works: Volume up/down/mute, Airplane mode What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator lights I already tried solutions regarding editing the Kernel Parameter acpi_osi in the grub config but can not get the keys to work. In case of screen brightness changing it using the desktop slider works. But it seems, that the keypress isn't recognized at all. Neither xev nor acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone muting (fn+f8). Running showkey -k results in a keycode 465 pressed and released event for all three key combinations. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: udev 239-7ubuntu10.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Apr 1 14:22:47 2019 InstallationDate: Installed on 2019-03-30 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: HP HP EliteBook x360 1030 G3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2019 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.06.00 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.38.00 dmi.chassis.asset.tag: 5CD8427YK5 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook x360 dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 4QZ13ES#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876875] Re: Improve download-signed script to support current & grub2
This bug was fixed in the package grub2-signed - 1.142.1 --- grub2-signed (1.142.1) focal; urgency=medium * Support downloads from PPAs for additional signatures. LP: #1876875 -- Dimitri John Ledkov Fri, 24 Apr 2020 23:48:15 +0100 ** Changed in: grub2-signed (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1876875 Title: Improve download-signed script to support current & grub2 Status in grub2-signed package in Ubuntu: Fix Released Status in linux-signed package in Ubuntu: Fix Committed Status in s390-tools-signed package in Ubuntu: Won't Fix Status in grub2-signed source package in Focal: Fix Released Bug description: [Impact] * Improve and generalise download-signed script to allow using it with any signed binaries we care about * Add support to download simply the most current version * Add support to download /uefi/ signed binaries * Clean up arg parsing, add help, drop unused statements & imports. [Test Case] * Test downloading signed kernel works with public & private archives * Test that rebuilt signed .debs are the same [Regression Potential] * This is a built time script, as long the binaries are downloaded & packaged up the same, there is no end-user facing impact. [Other Info] * With these changes, download-signed script can be used by s390-tools-signed & grub2-signed, as well as all the kernels. * This is needed to support resigning with different keys for different ubuntu products. For example, UC20 uses the same grub binaries, but wants an additional trustpath to UC20 CA for grade:secured core images. At the moment creating such a signature is only possible via a round-trip in a PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1876875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855809] Re: vclib from ubuntu_k8s_unit_tests fail on Eoan 5.3 GCP
Issue found on 5.4.0-1016.16-gcp
** Tags added: focal sru-20200608
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1855809
Title:
vclib from ubuntu_k8s_unit_tests fail on Eoan 5.3 GCP
Status in ubuntu-kernel-tests:
New
Status in linux-gcp package in Ubuntu:
New
Bug description:
Issue found on 5.3.0-1010 Eoan GCP
E1207 09:14:34.779687 29118 datacenter.go:45] Failed to find the datacenter:
enoent. err: datacenter 'enoent' not found
E1207 09:14:34.783331 29118 datacenter.go:78] Unable to find VM by UUID. VM
UUID: enoent
E1207 09:14:34.785587 29118 datacenter.go:106] Failed to find VM by Path. VM
Path: enoent, err: vm 'enoent' not found
E1207 09:14:34.787217 29118 datacenter.go:153] Failed to parse vmDiskPath:
enoent
E1207 09:14:34.788754 29118 datacenter.go:165] Failed while searching for
datastore: enoent. err: datastore 'enoent' not found
E1207 09:14:34.792557 29118 datacenter.go:165] Failed while searching for
datastore: enoent. err: datastore 'enoent' not found
E1207 09:14:34.801865 29118 datacenter.go:191] Failed to get the folder
reference for enoent. err: folder 'enoent' not found
E1207 09:14:34.804569 29118 datacenter.go:203] VirtualMachine Object list is
empty
E1207 09:14:34.805548 29118 datacenter.go:213] Failed to get VM managed
objects from VM objects. vmObjList: [VirtualMachine:vm-54 @
/DC0/vm/DC0_H0_VM1], properties: [enoent], err: InvalidProperty
E1207 09:14:34.806781 29118 datacenter.go:241] Datastore Object list is empty
E1207 09:14:34.807159 29118 datacenter.go:251] Failed to get Datastore
managed objects from datastore objects. dsObjList:
[Datastore:/tmp/govcsim-DC0-LocalDS_0-314024335@folder-5 @
/DC0/datastore/LocalDS_0], properties: [enoent], err: InvalidProperty
E1207 09:14:34.968117 29118 connection.go:180] Failed to create new client.
err: EOF
2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:58028: remote
error: tls: bad certificate
E1207 09:14:35.039988 29118 connection.go:180] Failed to create new client.
err: Post https://127.0.0.1:35147/sdk: Host "127.0.0.1:35147" thumbprint does
not match "obviously wrong"
E1207 09:14:35.052610 29118 connection.go:180] Failed to create new client.
err: Post https://127.0.0.1:40591/sdk: x509: certificate signed by unknown
authority
2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:37506: remote
error: tls: bad certificate
2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:33050: remote
error: tls: bad certificate
E1207 09:14:35.081393 29118 connection.go:180] Failed to create new client.
err: EOF
E1207 09:14:35.081489 29118 connection.go:163] Failed to parse URL: . err:
parse https://should-not-matter:should-not-matter: invalid port
":should-not-matter" after host
--- FAIL: TestWithInvalidCaCertPath (0.00s)
connection_test.go:168: Expected an os.PathError, got: 'parse
https://should-not-matter:should-not-matter: invalid port ":should-not-matter"
after host' ({Op:"parse",
URL:"https://should-not-matter:should-not-matter;,
Err:(*errors.errorString)(0xc0004fcd70)})
E1207 09:14:35.081626 29118 connection.go:163] Failed to parse URL: . err:
parse https://should-not-matter:should-not-matter: invalid port
":should-not-matter" after host
--- FAIL: TestInvalidCaCert (0.00s)
connection_test.go:182: Expected invalid certificate error, got 'parse
https://should-not-matter:should-not-matter: invalid port ":should-not-matter"
after host'
FAIL
FAIL k8s.io/kubernetes/pkg/cloudprovider/providers/vsphere/vclib 0.319s
This is not a regression as this failure can be found in
5.3.0-1009.10-gcp as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855809/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876875] Re: Improve download-signed script to support current & grub2
No need to private build-logs privately, all good! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1876875 Title: Improve download-signed script to support current & grub2 Status in grub2-signed package in Ubuntu: Fix Released Status in linux-signed package in Ubuntu: Fix Committed Status in s390-tools-signed package in Ubuntu: Won't Fix Status in grub2-signed source package in Focal: Fix Released Bug description: [Impact] * Improve and generalise download-signed script to allow using it with any signed binaries we care about * Add support to download simply the most current version * Add support to download /uefi/ signed binaries * Clean up arg parsing, add help, drop unused statements & imports. [Test Case] * Test downloading signed kernel works with public & private archives * Test that rebuilt signed .debs are the same [Regression Potential] * This is a built time script, as long the binaries are downloaded & packaged up the same, there is no end-user facing impact. [Other Info] * With these changes, download-signed script can be used by s390-tools-signed & grub2-signed, as well as all the kernels. * This is needed to support resigning with different keys for different ubuntu products. For example, UC20 uses the same grub binaries, but wants an additional trustpath to UC20 CA for grade:secured core images. At the moment creating such a signature is only possible via a round-trip in a PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1876875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883498] Re: Frequent Panic in ip6_expire_frag_queue->icmpv6_send on 4.4.0-184-generic
@dvaerum I installed it from the xenial-proposed archive, for testing purpose only of course. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883498 Title: Frequent Panic in ip6_expire_frag_queue->icmpv6_send on 4.4.0-184-generic Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: I happened to do an upgrade on a number of servers last week. Some of them got 4.4.0-179-generic and the ones upgraded a bit later during the week got 4.4.0-184-generic as it was just released. The ones with 4.4.0-184-generic started getting stuck. With linux-crashdump installed I obtained the dmesgs and crash dumps. The backtrace appears somewhat similar to #202669 but that one only happened on bare hardware for us - this one is on KVM virtual instances. #202669 paniced in icmpv6_route_lookup and this one dies already in icmpv6_send. Between 2020-06-11 and 2020-06-15, on a set of 12 VMs running 4.4.0-184-generic, there were 85 crashes like this, on servers with noticeable IPv6 traffic. All of the 12 VMs with 4.4.0-184-generic crashed at least once. (There are more than 12 VMs experiencing this, this is just the set I had linux-crashdump on.) [57063.487084] BUG: unable to handle kernel NULL pointer dereference at 0018 [57063.487184] IP: [] icmp6_send+0x1fb/0x970 [57063.487218] PGD 0 [57063.487231] Oops: [#1] SMP [57063.488665] Call Trace: [57063.488679] [57063.488705] [] ? __netif_receive_skb+0x18/0x60 [57063.488739] [] ? task_tick_fair+0x4c8/0x8e0 [57063.488771] [] ? _raw_spin_unlock_bh+0x20/0x50 [57063.488802] [] icmpv6_send+0x21/0x30 [57063.488829] [] ip6_expire_frag_queue+0x115/0x1b0 [57063.488862] [] ? nf_ct_net_exit+0x50/0x50 [nf_defrag_ipv6] [57063.488897] [] nf_ct_frag6_expire+0x1f/0x30 [nf_defrag_ipv6] [57063.488937] [] call_timer_fn+0x37/0x140 [57063.488965] [] ? nf_ct_net_exit+0x50/0x50 [nf_defrag_ipv6] [57063.489002] [] run_timer_softirq+0x234/0x330 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883498/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855815] Re: flag from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP
This issue can be found in 5.4.0-1010.10-gcp as well. ** Summary changed: - flag from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP + flag from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855815 Title: flag from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP --- FAIL: TestConstantMaps (0.07s) ciphersuites_flag_test.go:106: discovered version tls.VersionTLS13 not in version map FAIL FAIL k8s.io/kubernetes/vendor/k8s.io/apiserver/pkg/util/flag 0.072s This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855811] Re: container from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP
This issue can be found in 5.4.0-1010.10-gcp as well. ** Summary changed: - container from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP + container from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP ** Tags added: sru-20200608 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855811 Title: container from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP # k8s.io/kubernetes/pkg/kubelet/container pkg/kubelet/container/sync_result_test.go:48:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult pkg/kubelet/container/sync_result_test.go:56:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult pkg/kubelet/container/sync_result_test.go:66:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult []*k8s.io/kubernetes/pkg/kubelet/container.Pod FAIL k8s.io/kubernetes/pkg/kubelet/container [build failed] This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855809] Re: vclib from ubuntu_k8s_unit_tests fail on Eoan 5.3 GCP / F-5.4-GCP
This issue can be found in 5.4.0-1010.10-gcp as well.
** Summary changed:
- vclib from ubuntu_k8s_unit_tests fail on Eoan 5.3 GCP
+ vclib from ubuntu_k8s_unit_tests fail on Eoan 5.3 GCP / F-5.4-GCP
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1855809
Title:
vclib from ubuntu_k8s_unit_tests fail on Eoan 5.3 GCP / F-5.4-GCP
Status in ubuntu-kernel-tests:
New
Status in linux-gcp package in Ubuntu:
New
Bug description:
Issue found on 5.3.0-1010 Eoan GCP
E1207 09:14:34.779687 29118 datacenter.go:45] Failed to find the datacenter:
enoent. err: datacenter 'enoent' not found
E1207 09:14:34.783331 29118 datacenter.go:78] Unable to find VM by UUID. VM
UUID: enoent
E1207 09:14:34.785587 29118 datacenter.go:106] Failed to find VM by Path. VM
Path: enoent, err: vm 'enoent' not found
E1207 09:14:34.787217 29118 datacenter.go:153] Failed to parse vmDiskPath:
enoent
E1207 09:14:34.788754 29118 datacenter.go:165] Failed while searching for
datastore: enoent. err: datastore 'enoent' not found
E1207 09:14:34.792557 29118 datacenter.go:165] Failed while searching for
datastore: enoent. err: datastore 'enoent' not found
E1207 09:14:34.801865 29118 datacenter.go:191] Failed to get the folder
reference for enoent. err: folder 'enoent' not found
E1207 09:14:34.804569 29118 datacenter.go:203] VirtualMachine Object list is
empty
E1207 09:14:34.805548 29118 datacenter.go:213] Failed to get VM managed
objects from VM objects. vmObjList: [VirtualMachine:vm-54 @
/DC0/vm/DC0_H0_VM1], properties: [enoent], err: InvalidProperty
E1207 09:14:34.806781 29118 datacenter.go:241] Datastore Object list is empty
E1207 09:14:34.807159 29118 datacenter.go:251] Failed to get Datastore
managed objects from datastore objects. dsObjList:
[Datastore:/tmp/govcsim-DC0-LocalDS_0-314024335@folder-5 @
/DC0/datastore/LocalDS_0], properties: [enoent], err: InvalidProperty
E1207 09:14:34.968117 29118 connection.go:180] Failed to create new client.
err: EOF
2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:58028: remote
error: tls: bad certificate
E1207 09:14:35.039988 29118 connection.go:180] Failed to create new client.
err: Post https://127.0.0.1:35147/sdk: Host "127.0.0.1:35147" thumbprint does
not match "obviously wrong"
E1207 09:14:35.052610 29118 connection.go:180] Failed to create new client.
err: Post https://127.0.0.1:40591/sdk: x509: certificate signed by unknown
authority
2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:37506: remote
error: tls: bad certificate
2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:33050: remote
error: tls: bad certificate
E1207 09:14:35.081393 29118 connection.go:180] Failed to create new client.
err: EOF
E1207 09:14:35.081489 29118 connection.go:163] Failed to parse URL: . err:
parse https://should-not-matter:should-not-matter: invalid port
":should-not-matter" after host
--- FAIL: TestWithInvalidCaCertPath (0.00s)
connection_test.go:168: Expected an os.PathError, got: 'parse
https://should-not-matter:should-not-matter: invalid port ":should-not-matter"
after host' ({Op:"parse",
URL:"https://should-not-matter:should-not-matter;,
Err:(*errors.errorString)(0xc0004fcd70)})
E1207 09:14:35.081626 29118 connection.go:163] Failed to parse URL: . err:
parse https://should-not-matter:should-not-matter: invalid port
":should-not-matter" after host
--- FAIL: TestInvalidCaCert (0.00s)
connection_test.go:182: Expected invalid certificate error, got 'parse
https://should-not-matter:should-not-matter: invalid port ":should-not-matter"
after host'
FAIL
FAIL k8s.io/kubernetes/pkg/cloudprovider/providers/vsphere/vclib 0.319s
This is not a regression as this failure can be found in
5.3.0-1009.10-gcp as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855809/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855810] Re: podautoscaler from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
This issue can be found in 5.4.0-1010.10-gcp as well. ** Summary changed: - podautoscaler from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP + podautoscaler from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855810 Title: podautoscaler from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP Test failed with: panic: test timed out after 2m0s (error message too long, please refer to the attachment) /tmp/kubernetes.git/_output/local/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:69 +0x62 FAIL k8s.io/kubernetes/pkg/controller/podautoscaler 120.039s This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883239] Re: Kernel modules missing in 5.4.0-37
I believe I was hit by the same bug. I'm using Ubuntu 20.04 on a ThinkPad X1 Carbon 4th. Manually installing the missing linux-modules- extra for 5.4.0-37 brings networking back, but I still had problems getting the system to detect external monitors. That is why I stay on 5.4.0-33 for the moment. However, even on 5.4.0-33, the detection of external monitors sometimes fails. That means that aspect could be a false alarm (on my system). What I can confirm is that for me networking is definitely broken because of the missing linux-modules-extra, which were automatically installed for 5.4.0.33 but were missing in 5.4.0.37. After manually installing the package, networking works as before. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883239 Title: Kernel modules missing in 5.4.0-37 Status in linux package in Ubuntu: Confirmed Bug description: I recently updated my Ubuntu 20.04 to the latest kernel (5.4.0-37) but upon reboot my Dell XPS lost a few peripherals, like the wifi, and the possibility to use the Dell WD-15 docking station for LAN or external monitors; USB hub functionality was working though. After some inspection, I've found that several kernel modules are missing for that specific kernel version: $ find /usr/lib/modules -iname ath10k /usr/lib/modules/5.4.0-28-generic/kernel/drivers/net/wireless/ath/ath10k /usr/lib/modules/5.4.0-31-generic/kernel/drivers/net/wireless/ath/ath10k /usr/lib/modules/5.4.0-33-generic/kernel/drivers/net/wireless/ath/ath10k And lspci shows the wireless card twice (one more time at the top) and that the following modules and drivers are not loaded for the proper devices: - i915 - processor_thermal_device - intel_pch_thermal - intel_lpss_pci - mei_me - snd_hda_intel - nouveau (but not the nvidia, which I'm using) - ath10k_pci - rtsx_pci Restarting with the previous kernel version (5.4.0-33) works without any issue. I'll attach both lspci outputs, but you can easily review the diff here: https://www.diffchecker.com/mVCbTzSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884025] Re: iwlwifi not loading on kernel 5.4.0.37.40
** Tags added: hwe-networking-wifi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884025 Title: iwlwifi not loading on kernel 5.4.0.37.40 Status in linux package in Ubuntu: Incomplete Bug description: I have a lenovo thinkpad E550 that has had kubuntu installed starting with 18.04, now updated to 20.04, I never had problems with wifi until last kernel update. If I boot with 5.4.0-33.37 the wireless connection acts normally, it's mostly stable and I have no major issues. If I boot with 5.4.0-37.41 there is a message like this and the wireless interface is not activated: [ 16.227170] kernel: iwlwifi :04:00.0: enabling device ( -> 0002) [ 16.227328] kernel: iwlwifi :04:00.0: HW_REV=0x, PCI issues? [ 16.275802] kernel: iwlwifi: probe of :04:00.0 failed with error -5 There are similar issue with previous releases, but none seem to have fixed the problem, some of the more informatives (apparently it's either a kernel issue fixed with kernel 5.6 or a firmware loaded incorrectly): - https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1867026 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865962 System specifications: System:Host: pc Kernel: 5.4.0-33-generic x86_64 bits: 64 Console: tty 0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: LENOVO product: 20DF004USP v: ThinkPad E550 serial: --- Mobo: LENOVO model: 20DF004USP v: SDK0E50510 WIN serial: --- UEFI [Legacy]: LENOVO v: J5ET54WW (1.25 ) date: 07/18/2016 CPU: Topology: Dual Core model: Intel Core i7-5500U bits: 64 type: MT MCP L2 cache: 4096 KiB Speed: 798 MHz min/max: 500/3000 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Network: Device-1: Intel Ethernet I218-V driver: e1000e IF: enp0s25 state: down mac: 68:f7:28:5f:d7:27 Device-2: Intel Wireless 3160 driver: iwlwifi IF: wlp4s0 state: up mac: d0:7e:35:84:92:57 IF-ID-1: lxcbr0 state: down mac: 00:16:3e:00:00:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884025/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839912] Re: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED"
** Tags added: sru-20200608 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839912 Title: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED" Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: This is at lease a test case regression with the proposed kernel: selftests: test_maps Allowed update sockmap '0:3' not in ESTABLISHED not ok 1..3 selftests: test_maps [FAIL] But with older kernel: selftests: test_maps test_maps: OK ok 1..3 selftests: test_maps [PASS] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 13 03:42 seq crw-rw 1 root audio 116, 33 Aug 13 03:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Aug 13 03:52:52 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1839912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848771] Re: Reboot after resume from suspend (deep)
For what it's worth, I had a similar sounding problem on a Dell Latitude E7470 on Ubuntu 20.04 (upgraded from 18.04). Suspend would work okay, but most of the time resume would just end up rebooting, immediately. I noticed a Bluetooth error in the dmesg output, so I disabled Bluetooth, both in Linux and in the BIOS. Now resume always works. I'm running the vanilla Kernel (5.4.0-34-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/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
As a workaround you can add "initcall_blacklist=elants_i2c_driver_init" to GRUB_CMDLINE_LINUX, run 'update-grub', power down the laptop and start it again. Works for me. (5.7.1 kernel-ppa mainline) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883498] Re: Frequent Panic in ip6_expire_frag_queue->icmpv6_send on 4.4.0-184-generic
I can deploy 4.4.0-185 from xenial-proposed for testing on Monday. The fix looks good, I was already staring at https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?id=5d41ce29e3b91ef305f88d23f72b3359de329cec which came in 4.4.0-184. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883498 Title: Frequent Panic in ip6_expire_frag_queue->icmpv6_send on 4.4.0-184-generic Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: I happened to do an upgrade on a number of servers last week. Some of them got 4.4.0-179-generic and the ones upgraded a bit later during the week got 4.4.0-184-generic as it was just released. The ones with 4.4.0-184-generic started getting stuck. With linux-crashdump installed I obtained the dmesgs and crash dumps. The backtrace appears somewhat similar to #202669 but that one only happened on bare hardware for us - this one is on KVM virtual instances. #202669 paniced in icmpv6_route_lookup and this one dies already in icmpv6_send. Between 2020-06-11 and 2020-06-15, on a set of 12 VMs running 4.4.0-184-generic, there were 85 crashes like this, on servers with noticeable IPv6 traffic. All of the 12 VMs with 4.4.0-184-generic crashed at least once. (There are more than 12 VMs experiencing this, this is just the set I had linux-crashdump on.) [57063.487084] BUG: unable to handle kernel NULL pointer dereference at 0018 [57063.487184] IP: [] icmp6_send+0x1fb/0x970 [57063.487218] PGD 0 [57063.487231] Oops: [#1] SMP [57063.488665] Call Trace: [57063.488679] [57063.488705] [] ? __netif_receive_skb+0x18/0x60 [57063.488739] [] ? task_tick_fair+0x4c8/0x8e0 [57063.488771] [] ? _raw_spin_unlock_bh+0x20/0x50 [57063.488802] [] icmpv6_send+0x21/0x30 [57063.488829] [] ip6_expire_frag_queue+0x115/0x1b0 [57063.488862] [] ? nf_ct_net_exit+0x50/0x50 [nf_defrag_ipv6] [57063.488897] [] nf_ct_frag6_expire+0x1f/0x30 [nf_defrag_ipv6] [57063.488937] [] call_timer_fn+0x37/0x140 [57063.488965] [] ? nf_ct_net_exit+0x50/0x50 [nf_defrag_ipv6] [57063.489002] [] run_timer_softirq+0x234/0x330 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883498/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870971] Re: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API
Can confirm that the problem occurs on my "Lenovo IdeaPad L340-17API" regularly when power isn't plugged in. On some occasions I got a corrupted root filesystem as a consequence of having to turn the system off "hard". Furthermore I noticed that sometimes the Power-LED began to blink instead of glowing steadily. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870971 Title: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API Status in linux package in Ubuntu: Confirmed Bug description: Freshly installed Xubuntu 20.04 shows black screen instead of login screen upon boot on Lenovo Ideapad L340-17API. It is not possible to chvt to text terminal when boot is stuck on black screen. Booting with 'nomodeset' kernel option works properly but is not an option (e.g. screen brightness is not adjustable in this case). Another workaround is to ssh to laptop and run systemctl restart display-manager.service. After 5-10 seconds upon executing this command perfectly working login screen appears. Check dmesg. There is apparently related messages from amdgpu driver: ... апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm] recover vram bo from shadow start апр 05 20:46:45 kernel: [drm] recover vram bo from shadow done апр 05 20:46:45 kernel: [drm] Skip scheduling IBs! апр 05 20:46:45 kernel: [ cut here ] апр 05 20:46:45 kernel: WARNING: CPU: 3 PID: 793 at include/linux/dma-fence.h:533 drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Modules linked in: cmac algif_hash algif_skcipher af_alg bnep zram nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt snd_hda_codec > апр 05 20:46:45 kernel: CPU: 3 PID: 793 Comm: kworker/3:4 Tainted: G OE 5.4.0-21-generic #25-Ubuntu апр 05 20:46:45 kernel: Hardware name: LENOVO 81LY/LNVNB161216, BIOS ARCN32WW 07/11/2019 апр 05 20:46:45 kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] апр 05 20:46:45 kernel: RIP: 0010:drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Code: 41 5c 41 5d 41 5e 41 5f 5d c3 49 8b 46 10 31 c9 48 c7 80 80 00 00 00 00 00 00 00 49 8b 7f 70 31 c0 83 e7 01 74 04 0f 0b eb bf <0f> 0b eb c7 0f 0b eb 8b 66 0f 1f 44 00 00 0f 1f 44 00 00 83 7f 4c апр 05 20:46:45 kernel: RSP: 0018:a4dc806d7d28 EFLAGS: 00010246 апр 05 20:46:45 kernel: RAX: RBX: 0001 RCX: апр 05 20:46:45 kernel: RDX: 8cc9a6fc9180 RSI: 8cc9ac4609f8 RDI: апр 05 20:46:45 kernel: RBP: a4dc806d7d60 R08: 047a R09: 0004 апр 05 20:46:45 kernel: R10: R11: 0001 R12: 8cc9ac463c00 апр 05 20:46:45 kernel: R13: 8cc9a63c7980 R14: 8cc9ac460800 R15: 8cc9a6fc9140 апр 05 20:46:45 kernel: FS: () GS:8cc9b88c() knlGS: апр 05 20:46:45 kernel: CS: 0010 DS: ES: CR0: 80050033 апр 05 20:46:45 kernel: CR2: 7f275ff6c000 CR3: 0001af148000 CR4: 003406e0 апр 05 20:46:45 kernel: Call Trace: апр 05 20:46:45 kernel: amdgpu_device_gpu_recover+0x6cd/0x95a [amdgpu] апр 05 20:46:45 kernel:
[Kernel-packages] [Bug 1884060] Re: nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure with 5.4 kernels in Bionic
** Attachment added: "make.log" https://bugs.launchpad.net/bugs/1884060/+attachment/5384965/+files/make.log ** Also affects: nvidia-graphics-drivers-435 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: New => Invalid ** Changed in: nvidia-graphics-drivers-435 (Ubuntu Bionic) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-435 (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-435 (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1884060 Title: nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure with 5.4 kernels in Bionic Status in nvidia-graphics-drivers-435 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 source package in Bionic: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/n/nvidia-graphics-drivers-435/20200617_180544_6a91a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1884060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884060] [NEW] nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure with 5.4 kernels in Bionic
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/n/nvidia-graphics-drivers-435/20200617_180544_6a91a@/log.gz ** Affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: nvidia-graphics-drivers-435 (Ubuntu Bionic) Importance: High Assignee: Alberto Milone (albertomilone) Status: Confirmed ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Summary changed: - nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure with linux-oracle-5.4 5.4.0-1016.16~18.04.1 + nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure with 5.4 kernels in Bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1884060 Title: nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure with 5.4 kernels in Bionic Status in nvidia-graphics-drivers-435 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 source package in Bionic: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/n/nvidia-graphics-drivers-435/20200617_180544_6a91a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1884060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855816] Re: naming from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
Issue found on 5.4.0-1016.16-gcp ** Tags added: 5.4 focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855816 Title: naming from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP --- FAIL: TestGetNameFromCallsite (0.00s) --- FAIL: TestGetNameFromCallsite/ignore-package (0.00s) from_stack_test.go:52: expected "testing/testing.go:777", got "testing/testing.go:865" --- FAIL: TestGetNameFromCallsite/ignore-file (0.00s) from_stack_test.go:52: expected "testing/testing.go:777", got "testing/testing.go:865" FAIL FAIL k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/naming0.002s This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855815] Re: flag from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP
Issue found on 5.4.0-1016.16-gcp ** Tags added: 5.4 focal sru-20200608 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855815 Title: flag from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP --- FAIL: TestConstantMaps (0.07s) ciphersuites_flag_test.go:106: discovered version tls.VersionTLS13 not in version map FAIL FAIL k8s.io/kubernetes/vendor/k8s.io/apiserver/pkg/util/flag 0.072s This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855816] Re: naming from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP
This issue can be found in 5.4.0-1010.10-gcp as well. ** Summary changed: - naming from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP + naming from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP ** Tags added: sru-20200608 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855816 Title: naming from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP --- FAIL: TestGetNameFromCallsite (0.00s) --- FAIL: TestGetNameFromCallsite/ignore-package (0.00s) from_stack_test.go:52: expected "testing/testing.go:777", got "testing/testing.go:865" --- FAIL: TestGetNameFromCallsite/ignore-file (0.00s) from_stack_test.go:52: expected "testing/testing.go:777", got "testing/testing.go:865" FAIL FAIL k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/naming0.002s This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836708] Re: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10]
In the meantime the Debian packaging was split and now comes from src:libbpf. That in turn went into groovy and works well. Thanks @fginther for making me aware. This is done, I have closed the remaining tasks appropriately. ** Also affects: libbpf (Ubuntu) Importance: Undecided Status: New ** Changed in: libbpf (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836708 Title: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10] Status in libbpf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Won't Fix Bug description: Hi, Debian packages libbpf and so far does so out of the kernel source [1]. There is some movement to separate that from the kernel source [2] but this isn't ready yet. So far it is just a sync of the subtree out of the kernel sources. Since we do not share our kernel packaging we will not get this for-free without doing anything. If there will be an ITP about it in Debian I'll let you know and we can abort this, but unless that really happens I wanted to ask if you could as well build the libbpf* packages for 19.10 and onward? Note: this is not the same bpf lib as [3] despite the similarity in names. Reasoning: BPF becomes more and more important in general and is used in the kernel for many things. In the case that brought it to my attention it will be a PMD of DPDK that will need it to control XDP [4]. And XDP in general is an interesting and rising feature for network acceleration - I'd think it would be helpful to have this package around in Ubuntu. --- FYI here the package info from buster as of today root@d10-buster:~# apt-cache show libbpf-dev libbpf4.19 Package: libbpf-dev Source: linux Version: 4.19.28-2 Installed-Size: 350 Maintainer: Debian Kernel Team Architecture: amd64 Depends: libbpf4.19 (= 4.19.28-2) Description-en: eBPF helper library (development files) libbpf is a library for loading eBPF programs and reading and manipulating eBPF objects from user-space. Description-md5: b8834dcec31d23cd9577fbae4ac6a867 Multi-Arch: same Homepage: https://www.kernel.org/ Tag: devel::library, role::devel-lib Section: libdevel Priority: optional Filename: pool/main/l/linux/libbpf-dev_4.19.28-2_amd64.deb Size: 262268 MD5sum: 2ab356bbbc421ac44f4106b6cf234f17 SHA256: f567734a69bc472f2f5a546ace4ad3abf42d69f09d2613bca52a411d78179718 Package: libbpf4.19 Source: linux Version: 4.19.28-2 Installed-Size: 318 Maintainer: Debian Kernel Team Architecture: amd64 Depends: libc6 (>= 2.26), libelf1 (>= 0.131) Description-en: eBPF helper library (shared library) libbpf is a library for loading eBPF programs and reading and manipulating eBPF objects from user-space. Description-md5: 320aac663a5bd3caf223c7aa27857113 Multi-Arch: same Homepage: https://www.kernel.org/ Tag: role::shared-lib Section: libs Priority: optional Filename: pool/main/l/linux/libbpf4.19_4.19.28-2_amd64.deb Size: 259924 MD5sum: bbb27965530e4101d43b7226fd563840 SHA256: 18fdf5da4a90c8f42dedb8db510324d09d28f11eb2fa1b364508b14a95d5179b --- [1]: https://packages.debian.org/sid/libbpf-dev [2]: https://github.com/libbpf/libbpf [3]: https://github.com/iovisor/bcc [4]: https://www.iovisor.org/technology/xdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libbpf/+bug/1836708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883239] Re: Kernel modules missing in 5.4.0-37
@vicamo Thanks for pointing that out, I was missing linux-generic. I probably got into some apt or metapackage bug that removed it from my system, because I'm sure I didn't remove it manually. I dug into my apt logs and I've found this in the history log: Start-Date: 2020-05-28 09:32:50 Commandline: apt-get install -f Requested-By: alai (1000) Upgrade: libreoffice-common:amd64 (1:6.4.2-0ubuntu3, 1:6.4.3-0ubuntu0.20.04.1) Remove: linux-image-generic:amd64 (5.4.0.33.38), linux-image-generic-hwe-20.04:amd64 (5.4.0.33.38), linux-generic-hwe-20.04:amd64 (5.4.0.33.38), linux-modules-extra-5.4.0-33-generic:amd64 (5.4.0-33.37), linux-generic:amd64 (5.4.0.33.38) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2020-05-28 09:32:55 And im the corresponding term log, linux-generic was removed, but the update crashed when unpacking the OpenOffice update. That's really unfortunate. I should be fine now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883239 Title: Kernel modules missing in 5.4.0-37 Status in linux package in Ubuntu: Invalid Bug description: I recently updated my Ubuntu 20.04 to the latest kernel (5.4.0-37) but upon reboot my Dell XPS lost a few peripherals, like the wifi, and the possibility to use the Dell WD-15 docking station for LAN or external monitors; USB hub functionality was working though. After some inspection, I've found that several kernel modules are missing for that specific kernel version: $ find /usr/lib/modules -iname ath10k /usr/lib/modules/5.4.0-28-generic/kernel/drivers/net/wireless/ath/ath10k /usr/lib/modules/5.4.0-31-generic/kernel/drivers/net/wireless/ath/ath10k /usr/lib/modules/5.4.0-33-generic/kernel/drivers/net/wireless/ath/ath10k And lspci shows the wireless card twice (one more time at the top) and that the following modules and drivers are not loaded for the proper devices: - i915 - processor_thermal_device - intel_pch_thermal - intel_lpss_pci - mei_me - snd_hda_intel - nouveau (but not the nvidia, which I'm using) - ath10k_pci - rtsx_pci Restarting with the previous kernel version (5.4.0-33) works without any issue. I'll attach both lspci outputs, but you can easily review the diff here: https://www.diffchecker.com/mVCbTzSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
@Stephane, if this bug was not phrased that generically I would feel inclined to say it verified ok if the kernel image can be booted in secureboot mode and has the requested config options set. And treat the initrd issue as a separate one on the path to completion. For us, I would propose to count this feedback as success (and still release the kernel that way if there is no other problems). -- 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/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: Fix Committed Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 80010033, CR2 - , CR3 - 3FC01000 CR4 - 0668, CR8 - DR0 -
[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 I am experiencing this issue as well, but don't know how to extract the 19.10 default.pa from the .deb package. Can someone who has successfully applied this solution please post which lines they changed/added? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Trying to boot the proposed kernel in LXD: """ BdsDxe: loading Boot0007 "ubuntu" from HD(1,GPT,25633192-5DBD-412A-8A50-E29B79F72A50,0x800,0x32000)/\EFI\ubuntu\shimx64.efi BdsDxe: starting Boot0007 "ubuntu" from HD(1,GPT,25633192-5DBD-412A-8A50-E29B79F72A50,0x800,0x32000)/\EFI\ubuntu\shimx64.efi RAMDISK: incomplete write (4194304 != 8388608) Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-1017-kvm #17-Ubuntu Hardware name: QEMU Standard PC (Q35 + ICH9, 2009)/LXD, BIOS 0.0.0 02/06/2015 Call Trace: 0x9392230d 0x932a8a21 0x9412e5c1 0x9412e80f 0x9412e976 0x9412e274 ? 0x93938a70 0x93938a79 0x93a00215 Kernel Offset: 0x1220 from 0x8100 (relocation range: 0x8000-0xbfff) ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]--- """ This appears to be lz4 related. Changing the initramfs to gzip makes the VM boot just fine. It's worth noting that when booting the generic kernel, we get the unpack error showed in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660 but things still boot fine. Marking verification as failed based on this. We need images to work properly with a standard Ubuntu config so need lz4 fixed. ** Tags removed: verification-needed-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/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: Fix Committed Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 "
[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
""" Jun 18 13:56:15 f1 kernel: [0.383207] Trying to unpack rootfs image as initramfs... Jun 18 13:56:15 f1 kernel: [0.463102] Initramfs unpacking failed: Decoding failed """ Is what we're getting on current generic kernel, though boot continues after that. I don't know if when that happens we're actually skipping the initrd entirely and just get lucky that the generic kernel has everything we need builtin so it boots or if the error in that case is just wrong and the initrd is still properly unpacked and run. Either way, this needs sorting, looking at the other bug report, there's been something wrong with our kernel and lz4 initrd for a long time and it's apparently biting us a lot more now. -- 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/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: Fix Committed Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 -
[Kernel-packages] [Bug 1424727]
I've tried this with using https://www.theacademicpapers.co.uk/ and this works good on my side. I would suggest you should also try this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1424727 Title: NFS access not revoked on kdestroy Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: 1) Ubuntu 14.04 2) 3.13 kernel or mainline kernel 3.19. krb5-user [1.12+dfsg-2ubuntu5.1] nfs-common [1:1.2.8-6ubuntu1] 3) What should happen: Start as unpriviledged (in a kerberos sense) user with access to a kerberos protected NFS share (in this case it contains home directories) kinit user1 ls ~user1 #Test user1 permissions, this should always succeed (and does) kdestroy #should destroy user1 permissions kinit user2 ls ~user2# this should succeed! ls ~user1# this should fail! 4) What happened instead: After kinit user2: ls ~user2# this FAILS ls ~user1# this still WORKS This appears to be known upstream: http://www.citi.umich.edu/projects/nfsv4/linux/faq/#krb5_006 Bits and pieces of an earlier attempt at a fix: http://www.spinics.net/lists/linux-nfs/msg34236.html nfslogin/logout prototype http://www.citi.umich.edu/projects/asci/icsi-alpha/nfs-utils-patches/1.0.10-asci-2/nfs-utils-1.0.10-asci-017-add_nfslogin.dif Another bug request: https://fedorahosted.org/gss-proxy/ticket/1 (and linked discussion) Workarounds: Unmount/Mount NFS share To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1424727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
All LXD virtual machines are hitting this too. Run: - lxc launch images:ubuntu/focal/cloud f1 && lxc console f1 And you'll see it show that message. As mentioned above, boot then still goes ahead and you get a login prompt, but as that may not always be the case. For example in linux-kvm, that fallback mechanism doesn't appear to work and we instead get a kernel panic unless we've manually modified the initrd to be gzip: https://bugs.launchpad.net/cloud-images/+bug/1873809 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883962] Re: apparmor reference leak causes refcount_t overflow with af_alg_accept()
After a few hours with the reproducer running on the original kernel, the kernel errors about the reference count are observed: Focal: - $ uname -rv 5.4.0-38-generic #42-Ubuntu SMP Mon Jun 8 14:14:24 UTC 2020 $ ./aa-refcnt-af_alg [ 9581.048189] [ cut here ] [ 9581.049497] refcount_t overflow at apparmor_sk_clone_security+0x35/0x70 in aa-refcnt-af_al[1023], uid/euid: 1000/1000 [ 9581.052125] WARNING: CPU: 1 PID: 1023 at kernel/panic.c:677 refcount_error_report+0x9b/0xab [ 9581.054428] Modules linked in: ... [ 9581.063137] CPU: 1 PID: 1023 Comm: aa-refcnt-af_al Tainted: G OE 5.4.0-38-generic #42-Ubuntu [ 9581.065494] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 9581.067693] RIP: 0010:refcount_error_report+0x9b/0xab ... [ 9581.088358] Call Trace: [ 9581.089083] ex_handler_refcount+0x50/0x70 [ 9581.090147] fixup_exception+0x4a/0x61 [ 9581.091142] do_trap+0x4e/0xf0 [ 9581.091998] do_error_trap+0x7c/0xc0 [ 9581.092958] ? csum_partial_copy_generic+0x1687/0x3a10 [ 9581.094250] do_invalid_op+0x3c/0x50 [ 9581.095210] ? csum_partial_copy_generic+0x1687/0x3a10 [ 9581.096505] invalid_op+0x1e/0x30 [ 9581.097413] RIP: 0010:apparmor_sk_clone_security+0x35/0x70 ... [ 9581.113048] security_sk_clone+0x2f/0x40 [ 9581.114078] af_alg_accept+0x7e/0x190 [af_alg] [ 9581.115456] alg_accept+0x15/0x20 [af_alg] [ 9581.116549] __sys_accept4+0x109/0x210 [ 9581.117549] ? _cond_resched+0x19/0x30 [ 9581.118545] __x64_sys_accept+0x1c/0x20 [ 9581.119573] do_syscall_64+0x57/0x190 [ 9581.120551] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 9581.121821] RIP: 0033:0x7efc1bc390a7 ... Bionic: -- $ uname -rv 4.15.0-107-generic #108-Ubuntu SMP Mon Jun 8 17:51:33 UTC 2020 $ ./aa-refcnt-af_alg [ 8460.359291] [ cut here ] [ 8460.360638] refcount_t overflow at apparmor_sk_clone_security+0x37/0x70 in aa-refcnt-af_al[1243], uid/euid: 1000/1000 [ 8460.363332] WARNING: CPU: 1 PID: 1243 at /build/linux-oHXYZI/linux-4.15.0/kernel/panic.c:662 refcount_error_report+0x9c/0xac [ 8460.366556] Modules linked in: ... [ 8460.375936] CPU: 1 PID: 1243 Comm: aa-refcnt-af_al Tainted: G OE 4.15.0-107-generic #108-Ubuntu [ 8460.378352] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 8460.380598] RIP: 0010:refcount_error_report+0x9c/0xac ... [ 8460.397294] Call Trace: [ 8460.398331] ex_handler_refcount+0x52/0x80 [ 8460.399432] fixup_exception+0x3a/0x50 [ 8460.400462] do_trap+0x8a/0x140 [ 8460.401346] do_error_trap+0xa6/0x140 [ 8460.402355] ? csum_partial_copy_generic+0xcfb/0x27a0 [ 8460.403671] ? ___slab_alloc+0x204/0x4f0 [ 8460.404730] ? ___slab_alloc+0x204/0x4f0 [ 8460.405786] ? get_empty_filp+0x5c/0x1c0 [ 8460.406840] do_invalid_op+0x20/0x30 [ 8460.407830] invalid_op+0x1b/0x40 [ 8460.408755] RIP: 0010:apparmor_sk_clone_security+0x37/0x70 ... [ 8460.420262] security_sk_clone+0x33/0x50 [ 8460.421314] af_alg_accept+0x81/0x1c0 [af_alg] [ 8460.422484] ? aa_sock_accept_perm+0x25/0x30 [ 8460.423623] alg_accept+0x15/0x20 [af_alg] [ 8460.424725] SYSC_accept4+0xff/0x210 [ 8460.425706] ? mntput+0x24/0x40 [ 8460.426598] ? __fput+0x193/0x220 [ 8460.427536] ? _cond_resched+0x19/0x40 [ 8460.428561] ? task_work_run+0x46/0xc0 [ 8460.429586] SyS_accept+0x10/0x20 [ 8460.430518] do_syscall_64+0x73/0x130 [ 8460.431522] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 8460.432830] RIP: 0033:0x7f0ecc0c87e4 ... ** Description changed: [Impact] * Users of the Crypto (user-space) API (i.e., AF_ALG) can trigger refcount errors in AppArmor under high load (might lead to memory leak or use after free.) * There is a reference leak in AppArmor when af_alg_accept() calls security_sock_graft() and then security_sk_clone(). * Both acquire a reference to a label, to assign it to the same pointer, but the latter does not release the former's acquired reference (before overwriting the pointer value.) * This reference leak builds up over time, and under high load can eventually overflow/underflow/saturate refcount, depending on which value it has when a program hits that. * The fix just checks if the pointer has an assigned label, then releases its acquired reference. [Test Case] + * See comment #1 for the test-case 'aa-refcnt-af_alg.c'. + * Exercise that code path indefinitely until it hits the refcount_t overflow/underflow/saturate message -(or not, with the patch.) +(or not, with the patch.) (see comment #4) - * See comment #1 for the test-case 'aa-refcnt-af_alg.c'. - -If the problem happens, in a few hours there is an -error message in the kernel logs (see comment #1.) + If the problem happens, in a few hours there is an + error message in the kernel logs (see comment #1.) * It's possible to monitor refcount values with kprobes, -to confirm whether or not the
[Kernel-packages] [Bug 1883962] Re: apparmor reference leak causes refcount_t overflow with af_alg_accept()
Monitoring the label reference count with the kprobes module: - original kernel: the counter keeps increasing on every pair of accept()/release() syscalls. - modified kernel: the counter keeps stable. Focal: - original) $ uname -rv 5.4.0-38-generic #42-Ubuntu SMP Mon Jun 8 14:14:24 UTC 2020 $ ./aa-refcnt-af_alg & $ sudo insmod kmod.ko ... [ 4739.811403] accept() :: comm = aa-refcnt-af_al, pid = 1023, sk->sk_security->label->count = 0x40b395e0 [ 4739.813677] release() :: comm = aa-refcnt-af_al, pid = 1023, sk->sk_security->label->count = 0x40b395e2 [ 4739.815994] accept() :: comm = aa-refcnt-af_al, pid = 1023, sk->sk_security->label->count = 0x40b395e1 [ 4739.818274] release() :: comm = aa-refcnt-af_al, pid = 1023, sk->sk_security->label->count = 0x40b395e3 [ 4739.820555] accept() :: comm = aa-refcnt-af_al, pid = 1023, sk->sk_security->label->count = 0x40b395e2 [ 4739.822833] release() :: comm = aa-refcnt-af_al, pid = 1023, sk->sk_security->label->count = 0x40b395e4 ... $ sudo rmmod kmod modified) $ uname -rv 5.4.0-38-generic #42+test20200617b1 SMP Wed Jun 17 16:31:24 -03 2020 $ ./aa-refcnt-af_alg & $ sudo insmod kmod.ko ... [ 185.657133] accept() :: comm = aa-refcnt-af_al, pid = 1098, sk->sk_security->label->count = 0x649 [ 185.660720] release() :: comm = aa-refcnt-af_al, pid = 1098, sk->sk_security->label->count = 0x64a [ 185.664321] accept() :: comm = aa-refcnt-af_al, pid = 1098, sk->sk_security->label->count = 0x649 [ 185.668981] release() :: comm = aa-refcnt-af_al, pid = 1098, sk->sk_security->label->count = 0x64a [ 185.672648] accept() :: comm = aa-refcnt-af_al, pid = 1098, sk->sk_security->label->count = 0x629 [ 185.676299] release() :: comm = aa-refcnt-af_al, pid = 1098, sk->sk_security->label->count = 0x62a ... $ sudo rmmod kmod Bionic: -- original) $ uname -rv 4.15.0-107-generic #108-Ubuntu SMP Mon Jun 8 17:51:33 UTC 2020 $ ./aa-refcnt-af_alg & $ sudo insmod kmod.ko ... [ 4333.136581] accept() :: comm = aa-refcnt-af_al, pid = 1243, sk->sk_security->label->count = 0x449b9e85 [ 4333.139131] release() :: comm = aa-refcnt-af_al, pid = 1243, sk->sk_security->label->count = 0x449b9e87 [ 4333.141650] accept() :: comm = aa-refcnt-af_al, pid = 1243, sk->sk_security->label->count = 0x449b9e86 [ 4333.144142] release() :: comm = aa-refcnt-af_al, pid = 1243, sk->sk_security->label->count = 0x449b9e88 [ 4333.146675] accept() :: comm = aa-refcnt-af_al, pid = 1243, sk->sk_security->label->count = 0x449b9e87 [ 4333.149199] release() :: comm = aa-refcnt-af_al, pid = 1243, sk->sk_security->label->count = 0x449b9e89 ... $ sudo rmmod kmod modified) $ uname -rv 4.15.0-107-generic #108+test20200617b1 SMP Wed Jun 17 16:33:16 -03 2020 $ ./aa-refcnt-af_alg & $ sudo insmod kmod.ko ... [ 245.921217] accept() :: comm = aa-refcnt-af_al, pid = 1165, sk->sk_security->label->count = 0x608 [ 245.923456] release() :: comm = aa-refcnt-af_al, pid = 1165, sk->sk_security->label->count = 0x609 [ 245.925718] accept() :: comm = aa-refcnt-af_al, pid = 1165, sk->sk_security->label->count = 0x608 [ 245.927954] release() :: comm = aa-refcnt-af_al, pid = 1165, sk->sk_security->label->count = 0x609 [ 245.930221] accept() :: comm = aa-refcnt-af_al, pid = 1165, sk->sk_security->label->count = 0x608 [ 245.932469] release() :: comm = aa-refcnt-af_al, pid = 1165, sk->sk_security->label->count = 0x609 ... $ sudo rmmod kmod -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883962 Title: apparmor reference leak causes refcount_t overflow with af_alg_accept() Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Won't Fix Bug description: [Impact] * Users of the Crypto (user-space) API (i.e., AF_ALG) can trigger refcount errors in AppArmor under high load (might lead to memory leak or use after free.) * There is a reference leak in AppArmor when af_alg_accept() calls security_sock_graft() and then security_sk_clone(). * Both acquire a reference to a label, to assign it to the same pointer, but the latter does not release the former's acquired reference (before overwriting the pointer value.) * This reference leak builds up over time, and under high load can eventually overflow/underflow/saturate refcount, depending on which value it has when a program hits that. * The fix just checks if the pointer has an assigned label, then releases its acquired reference. [Test Case] * See comment #1 for the test-case 'aa-refcnt-af_alg.c'. * Exercise that code path indefinitely until it hits the refcount_t overflow/underflow/saturate message (or not, with the patch.) (see comment #4) * It's possible to
[Kernel-packages] [Bug 1883239] Re: Kernel modules missing in 5.4.0-37
@Jean, please just install linux-modules-extra-5.4.0-37-generic. I'm marking this as INVALID for linux-modules-extra is necessary to enable this device, so it's the right solution for this problem. Meta package "linux-generic" or similar would always depending on it, so you should also install "linux-generic" to prevent this from happening again. @Philipp, please file a separate bug for external monitor detection. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883239 Title: Kernel modules missing in 5.4.0-37 Status in linux package in Ubuntu: Invalid Bug description: I recently updated my Ubuntu 20.04 to the latest kernel (5.4.0-37) but upon reboot my Dell XPS lost a few peripherals, like the wifi, and the possibility to use the Dell WD-15 docking station for LAN or external monitors; USB hub functionality was working though. After some inspection, I've found that several kernel modules are missing for that specific kernel version: $ find /usr/lib/modules -iname ath10k /usr/lib/modules/5.4.0-28-generic/kernel/drivers/net/wireless/ath/ath10k /usr/lib/modules/5.4.0-31-generic/kernel/drivers/net/wireless/ath/ath10k /usr/lib/modules/5.4.0-33-generic/kernel/drivers/net/wireless/ath/ath10k And lspci shows the wireless card twice (one more time at the top) and that the following modules and drivers are not loaded for the proper devices: - i915 - processor_thermal_device - intel_pch_thermal - intel_lpss_pci - mei_me - snd_hda_intel - nouveau (but not the nvidia, which I'm using) - ath10k_pci - rtsx_pci Restarting with the previous kernel version (5.4.0-33) works without any issue. I'll attach both lspci outputs, but you can easily review the diff here: https://www.diffchecker.com/mVCbTzSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884089] [NEW] Focal update: v5.4.47 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.47 upstream stable release
from git://git.kernel.org/
ipv6: fix IPV6_ADDRFORM operation logic
mlxsw: core: Use different get_trend() callbacks for different thermal zones
net_failover: fixed rollback in net_failover_open()
tun: correct header offsets in napi frags mode
bridge: Avoid infinite loop when suppressing NS messages with invalid options
vxlan: Avoid infinite loop when suppressing NS messages with invalid options
bpf: Support llvm-objcopy for vmlinux BTF
elfnote: mark all .note sections SHF_ALLOC
Input: mms114 - fix handling of mms345l
ARM: 8977/1: ptrace: Fix mask for thumb breakpoint hook
sched/fair: Don't NUMA balance for kthreads
Input: synaptics - add a second working PNP_ID for Lenovo T470s
csky: Fixup abiv2 syscall_trace break a4 & a5
gfs2: Even more gfs2_find_jhead fixes
drivers/net/ibmvnic: Update VNIC protocol version reporting
powerpc/xive: Clear the page tables for the ESB IO mapping
spi: dw: Fix native CS being unset
ath9k_htc: Silence undersized packet warnings
smack: avoid unused 'sip' variable warning
RDMA/uverbs: Make the event_queue fds return POLLERR when disassociated
padata: add separate cpuhp node for CPUHP_PADATA_DEAD
s390/pci: Log new handle in clp_disable_fh()
x86/cpu/amd: Make erratum #1054 a legacy erratum
KVM: x86: only do L1TF workaround on affected processors
PCI/PM: Adjust pcie_wait_for_link_delay() for caller delay
perf probe: Accept the instance number of kretprobe event
mm: add kvfree_sensitive() for freeing sensitive data objects
selftests: fix flower parent qdisc
fanotify: fix ignore mask logic for events on child and on dir
aio: fix async fsync creds
ipv4: fix a RCU-list lock in fib_triestat_seq_show
iwlwifi: mvm: fix NVM check for 3168 devices
sctp: fix possibly using a bad saddr with a given dst
sctp: fix refcount bug in sctp_wfree
x86_64: Fix jiffies ODR violation
x86/PCI: Mark Intel C620 MROMs as having non-compliant BARs
x86/speculation: Prevent rogue cross-process SSBD shutdown
x86/speculation: Avoid force-disabling IBPB based on STIBP and enhanced IBRS.
x86/speculation: PR_SPEC_FORCE_DISABLE enforcement for indirect branches.
x86/reboot/quirks: Add MacBook6,1 reboot quirk
perf/x86/intel: Add more available bits for OFFCORE_RESPONSE of Intel Tremont
KVM: x86/mmu: Set mmio_value to '0' if reserved #PF can't be generated
KVM: x86: respect singlestep when emulating instruction
KVM: x86: Fix APIC page invalidation race
powerpc/ptdump: Properly handle non standard page size
ASoC: max9867: fix volume controls
io_uring: use kvfree() in io_sqe_buffer_register()
efi/efivars: Add missing kobject_put() in sysfs entry creation error path
smb3: fix incorrect number of credits when ioctl MaxOutputResponse > 64K
smb3: add indatalen that can be a non-zero value to calculation of credit
charge in smb2 ioctl
watchdog: imx_sc_wdt: Fix reboot on crash
ALSA: es1688: Add the missed snd_card_free()
ALSA: fireface: fix configuration error for nominal sampling transfer frequency
ALSA: hda/realtek - add a pintbl quirk for several Lenovo machines
ALSA: pcm: disallow linking stream to itself
ALSA: pcm: fix snd_pcm_link() lockdep splat
ALSA: usb-audio: Fix inconsistent card PM state after resume
ALSA: usb-audio: Add vendor, product and profile name for HP Thunderbolt Dock
ACPI: sysfs: Fix reference count leak in acpi_sysfs_add_hotplug_profile()
ACPI: CPPC: Fix reference count leak in acpi_cppc_processor_probe()
ACPI: GED: add support for _Exx / _Lxx handler methods
ACPI: PM: Avoid using power resources if there are none for D0
arm64: acpi: fix UBSAN warning
lib/lzo: fix ambiguous encoding bug in lzo-rle
nilfs2: fix null pointer dereference at nilfs_segctor_do_construct()
spi: dw: Fix controller unregister order
spi: Fix controller unregister order
spi: pxa2xx: Fix controller unregister order
spi: pxa2xx: Fix runtime PM ref imbalance on probe error
spi: bcm2835: Fix controller unregister order
spi: bcm2835aux: Fix controller unregister order
spi: bcm-qspi: Handle clock probe deferral
spi: bcm-qspi: when tx/rx buffer is NULL set to 0
PM: runtime: clk: Fix clk_pm_runtime_get() error path
gup: document and work around "COW can break either way" issue
crypto: cavium/nitrox - Fix 'nitrox_get_first_device()' when ndevlist is fully
iterated
crypto: algapi - Avoid spurious modprobe on LOADED
crypto: drbg - fix error return code in drbg_alloc_state()
x86/{mce,mm}: Unmap the entire page if the whole page is affected and poisoned
firmware: imx: warn on unexpected RX
firmware: imx-scu: Support one TX and one RX
[Kernel-packages] [Bug 1881322] Re: Touchpad not detected in 'Lenovo V15-IIL model 82C5' after installing Ubuntu 20.04
You-Cheng, i also tried removing pci=nocrs and rebooting and it did not work either. I would like to try https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1881322, should I delete all the grub parameters that i added? To add further information: - With the parameters I currently have, and with Mouse Click Emulation set in "Area" (in Tweaks), the right mouse button and middle mouse button does not work (In xev i can see that all are mapped to button 1) but the gestures as two finger scrolling work fine. - With Click Emulation set in "Fingers", xev shows button 1, button 2 and button 3 with one, two and three fingers, respectively. - The Option "Disable Touchpad while Typing" does not work with any of the previous configurations. Also, I think this is unrelated: - Sometimes when I boot ubuntu, the sound does not work, even the icon in the sound settings (top right corner) does not show, and the volume with the Fn keys does not change. - When you try to open an app (e.g. Firefox), a folder or a terminal, it needs around a minute to work for the first time, then you can open anything normally. - When I try to shutdown or restart, it shows a recurrent message "[ 56.603594] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x202f8100" - The initial number rises (e.g. the second message is [57.607631]) and the hexadecimal number also changes. - I have to force the shutdown. It usually requires one restart to fix, but sometimes i get in this situation two times in a row. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881322 Title: Touchpad not detected in 'Lenovo V15-IIL model 82C5' after installing Ubuntu 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 is installed in a brand new Lenovo V15-IIL alongside Windows 10. According to lenovo's support page, the driver for windows is Synaptics 19.5.10.149_Elan 22.4.18.1. In windows the touchpad works fine. This model has two options in BIOS regarding Fn Keys, a "Smart Fn key" that toogles the Fn key on/off each time you press it and a "Foolproof Fn Key" that maps the Fn key to Ctrl when you press a combinations of keys that does not have a Fn assigned. When I enable the "foolproof fn key" in the BIOS, the Fn + F1...F12 and the sound driver stop working (i dont have sound, i can't change the volume and the volume icon in the GUI does not show). Fn+F6 (to enable/disable touchpad) can't enable it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fdadam 1434 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 29 13:08:24 2020 InstallationDate: Installed on 2020-05-28 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 002: ID 0458:0186 KYE Systems Corp. (Mouse Systems) Genius DX-120 Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82C5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=fd0c8ed1-6032-467c-9902-3094e6740be8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn82C5:pvrLenovoV15-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV15-IIL: dmi.product.family: V15-IIL dmi.product.name: 82C5 dmi.product.sku: LENOVO_MT_82C5_BU_idea_FM_V15-IIL dmi.product.version: Lenovo V15-IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881322/+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 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
Hello. @Alejandro Miranda, would you be kind enough to share that script with us? It would be greatly appreciated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal Status in alsa-ucm-conf package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14 Audio works and the volume seems reasonable however the audio is noticeably missing bass giving everything a high treble sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-ucm-conf 1.2.2-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 09:17:33 2020 Dependencies: InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-ucm-conf UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: linux PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883962] Re: apparmor reference leak causes refcount_t overflow with af_alg_accept()
** Tags added: sts ** Changed in: linux (Ubuntu Groovy) Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883962 Title: apparmor reference leak causes refcount_t overflow with af_alg_accept() Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Invalid Bug description: [Impact] * Users of the Crypto (user-space) API (i.e., AF_ALG) can trigger refcount errors in AppArmor under high load (might lead to memory leak or use after free.) * There is a reference leak in AppArmor when af_alg_accept() calls security_sock_graft() and then security_sk_clone(). * Both acquire a reference to a label, to assign it to the same pointer, but the latter does not release the former's acquired reference (before overwriting the pointer value.) * This reference leak builds up over time, and under high load can eventually overflow/underflow/saturate refcount, depending on which value it has when a program hits that. * The fix just checks if the pointer has an assigned label, then releases its acquired reference. [Test Case] * See comment #1 for the test-case 'aa-refcnt-af_alg.c'. * Exercise that code path indefinitely until it hits the refcount_t overflow/underflow/saturate message (or not, with the patch.) (see comment #4) * It's possible to monitor refcount values with kprobes, to confirm whether or not the problem is happening. (see comments #2 and #3) [Other Info] * Patch applied upstream on v5.8-rc1 [1] * Applied on Unstable (tag Ubuntu-5.8-5.8.0-0.1) * Not required on Groovy (still 5.4; should sync from Unstable) * Not required on Eoan (EOL date before SRU cycle release date) * Required on Bionic and Focal. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=3b646abc5bc6c0df649daea4c2c976bd4d47e4c8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880792] Re: linux-firmware: add sof-firmware and tplg files for tgl machines
** Tags added: oem-priority originate-from-1880147 -- 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/1880792 Title: linux-firmware: add sof-firmware and tplg files for tgl machines Status in HWE Next: New Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Groovy: Fix Committed Bug description: [Impact] When booting our 20.04 + oem-5.6 kernel on tgl platforms, the sof audio driver always fails to load the sof firmware, the audio function deosn't work at all on tgl platforms. [Fix] Intel released sof-firmware including tplg for tgl platforms, after putting them in the /lib/firmware/inte/sof|sof-tplg, the audio works well on those tgl platforms. [Test Case] Put those firmware and tplg to linux-firmware folders, boot 20.04 + oem-5.6 kernel on tgl platforms, the audio works well. [Regression Risk] Low, just adding some new files, no change on existing files. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1880792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
** Tags added: originate-from-1880147 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Released Bug description: This is for alsa-ucm-conf: The patches are already in the mainline alsa-ucm-conf, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] After fixing the kernel, we also need to change the ucm2 to make it support the machine without Intel hdmi audio. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline alsa-ucm-conf. And we already tested them on 4 HP machines. This is for linux kernel: The patch is already in the oem-5.6 kernel and unstable kernel, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] Intel upstream 2 patches in the kernel to fix it. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline kernel. On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
Given that the change to the compression format is one of the headline features of Ubuntu 20, and that Ubuntu 20 is a LTS release (and thus, for one thing, a release upon which other Linux distributions are based) I am surprised that this problem made it into the final release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848771]
Please re-test it with v5.8-rc1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 @David is it sustainable in your case and works also after a power down of the machine? unfortunately, in my case it only works when I first boot ubuntu 19.10 via live iso and reboot into installed ubuntu 20.04. however, after a complete power down my 20.04 fails back to not working hsp/hfp mode. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883962] Re: apparmor reference leak causes refcount_t overflow with af_alg_accept()
[B][PATCH 0/1] Fix apparmor reference leak via AF_ALG https://lists.ubuntu.com/archives/kernel-team/2020-June/36.html [B][PATCH 1/1] apparmor: check/put label on apparmor_sk_clone_security() https://lists.ubuntu.com/archives/kernel-team/2020-June/37.html [F][PATCH 1/1] apparmor: check/put label on apparmor_sk_clone_security() https://lists.ubuntu.com/archives/kernel-team/2020-June/38.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883962 Title: apparmor reference leak causes refcount_t overflow with af_alg_accept() Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Won't Fix Bug description: [Impact] * Users of the Crypto (user-space) API (i.e., AF_ALG) can trigger refcount errors in AppArmor under high load (might lead to memory leak or use after free.) * There is a reference leak in AppArmor when af_alg_accept() calls security_sock_graft() and then security_sk_clone(). * Both acquire a reference to a label, to assign it to the same pointer, but the latter does not release the former's acquired reference (before overwriting the pointer value.) * This reference leak builds up over time, and under high load can eventually overflow/underflow/saturate refcount, depending on which value it has when a program hits that. * The fix just checks if the pointer has an assigned label, then releases its acquired reference. [Test Case] * See comment #1 for the test-case 'aa-refcnt-af_alg.c'. * Exercise that code path indefinitely until it hits the refcount_t overflow/underflow/saturate message (or not, with the patch.) (see comment #4) * It's possible to monitor refcount values with kprobes, to confirm whether or not the problem is happening. (see comments #2 and #3) [Other Info] * Patch applied upstream on v5.8-rc1 [1] * Applied on Unstable (tag Ubuntu-5.8-5.8.0-0.1) * Not required on Groovy (still 5.4; should sync from Unstable) * Not required on Eoan (EOL date before SRU cycle release date) * Required on Bionic and Focal. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=3b646abc5bc6c0df649daea4c2c976bd4d47e4c8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882823] Re: int3403 thermal INT3403:00
Thank you. Will the patch make it to kernel 5.4? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882823 Title: int3403 thermal INT3403:00 Status in linux package in Ubuntu: Confirmed Bug description: [8.112761] int3403 thermal INT3403:00: Unsupported event [0x91] [ 10.121722] int3403 thermal INT3403:00: Unsupported event [0x91] [ 12.165233] int3403 thermal INT3403:00: Unsupported event [0x91] Is constantly flooding my dmesg. I believe this is also due to missing audio drivers as well. Which is another issue that I am facing. Realtek ALC1220 Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883976] Re: package linux-modules-extra-5.4.0-37-generic (not installed) failed to install/upgrade: impossible de créer le fichier « /var/lib/dpkg/info/linux-modules-extra-5.4.
Please stop Sophos Antivirus while upgrading/installing kernel related packages: $ sudo systemctl stop sav-protect.service ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883976 Title: package linux-modules-extra-5.4.0-37-generic (not installed) failed to install/upgrade: impossible de créer le fichier « /var/lib/dpkg/info /linux-modules-extra-5.4.0-37-generic.list-new »: Opération non permise Status in linux package in Ubuntu: Incomplete Bug description: sudden error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-37-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vincent1212 F pulseaudio CasperMD5CheckResult: skip Date: Wed Jun 10 18:15:20 2020 ErrorMessage: impossible de créer le fichier « /var/lib/dpkg/info/linux-modules-extra-5.4.0-37-generic.list-new »: Opération non permise InstallationDate: Installed on 2019-06-21 (362 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: HP HP EliteBook 840 G5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux Title: package linux-modules-extra-5.4.0-37-generic (not installed) failed to install/upgrade: impossible de créer le fichier « /var/lib/dpkg/info/linux-modules-extra-5.4.0-37-generic.list-new »: Opération non permise UpgradeStatus: Upgraded to focal on 2020-04-29 (48 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: HP dmi.bios.version: Q78 Ver. 01.06.00 dmi.board.name: 83B2 dmi.board.vendor: HP dmi.board.version: KBC Version 04.57.00 dmi.chassis.asset.tag: 5CG91409QS dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ78Ver.01.06.00:bd01/03/2019:svnHP:pnHPEliteBook840G5:pvr:rvnHP:rn83B2:rvrKBCVersion04.57.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G5 dmi.product.sku: 2FA68AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883962] Re: apparmor reference leak causes refcount_t overflow with af_alg_accept()
kprobes module to monitor the apparmor label reference count. ** Attachment added: "kmod.c" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883962/+attachment/5385006/+files/kmod.c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883962 Title: apparmor reference leak causes refcount_t overflow with af_alg_accept() Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Won't Fix Bug description: [Impact] * Users of the Crypto (user-space) API (i.e., AF_ALG) can trigger refcount errors in AppArmor under high load (might lead to memory leak or use after free.) * There is a reference leak in AppArmor when af_alg_accept() calls security_sock_graft() and then security_sk_clone(). * Both acquire a reference to a label, to assign it to the same pointer, but the latter does not release the former's acquired reference (before overwriting the pointer value.) * This reference leak builds up over time, and under high load can eventually overflow/underflow/saturate refcount, depending on which value it has when a program hits that. * The fix just checks if the pointer has an assigned label, then releases its acquired reference. [Test Case] * See comment #1 for the test-case 'aa-refcnt-af_alg.c'. * Exercise that code path indefinitely until it hits the refcount_t overflow/underflow/saturate message (or not, with the patch.) (see comment #4) * It's possible to monitor refcount values with kprobes, to confirm whether or not the problem is happening. (see comments #2 and #3) [Other Info] * Patch applied upstream on v5.8-rc1 [1] * Applied on Unstable (tag Ubuntu-5.8-5.8.0-0.1) * Not required on Groovy (still 5.4; should sync from Unstable) * Not required on Eoan (EOL date before SRU cycle release date) * Required on Bionic and Focal. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=3b646abc5bc6c0df649daea4c2c976bd4d47e4c8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813142] Re: Network connection lost after standby
** Tags added: hwe-networking-ethernet ** Summary changed: - Network connection lost after standby + Realtek RTL8111/8168/8411 [10ec:8168] Subsystem [1734:11ff]: Network connection lost after standby -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813142 Title: Realtek RTL8111/8168/8411 [10ec:8168] Subsystem [1734:11ff]: Network connection lost after standby Status in linux package in Ubuntu: Incomplete Bug description: System has a Realtek network card, so r8169 driver is used. The behaviour occurs under the following circumstances: $ sudo ethtool enp1s0 reports Supports Wake-on: pumbg Wake-on: d If in this case I send the system to standby (ALT-key plus pause symbol from the control dropdown) then the system goes to standby. After waking up the system the network connectivity is lost and the control panel for network settings reports "cable disconnected". The strange thing is: If I set the WOL properties to g with $ sudo ethtool -s enp1s0 wol g and do exactly the same, then the problem does not occur. I assume there is a bug in the standby handling of the r8169 driver because network connectivity shouldn't get lost if WOL is disabled. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rainer 1401 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 24 11:03:13 2019 InstallationDate: Installed on 2019-01-23 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. enp1s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1267:0103 Logic3 / SpectraVideo plc G-720 Keyboard Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=d0aba4e1-c5f2-4968-bc5e-7d256035ae10 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2018 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.13 R1.11.0 for D3600-A1x dmi.board.name: D3600-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3600-A1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.13R1.11.0forD3600-A1x:bd11/07/2018:svnFUJITSU:pn:pvr:rvnFUJITSU:rnD3600-A1:rvrS26361-D3600-A1:cvnFUJITSU:ct3:cvr: dmi.product.family: ESPRIMO-FTS dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
Didier, there is a long-standing grub2 task on this bug, but from the comment history it's not clear to me that there are further changes required to grub or what those are, can you have another look at this please? (Given the description is "zfs-initramfs" failing, I would think that's not a grub bug, but I'm not sure.) ** Changed in: grub2 (Ubuntu) Assignee: (unassigned) => Didier Roche (didrocks) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Fix Released Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
Adding "initcall_blacklist=elants_i2c_driver_init" to GRUB_CMDLINE_LINUX in /etc/default/grub and run 'update-grub' works also fine for me! Tested with mainline kernel 5.7.1 from https://kernel.ubuntu.com/~kernel-ppa/mainline/ Newer mainline (5.7.1 to 5.7.4) faild to build properly for AMD @Jasper van der Neut: Thank you! Much more convenient workaround if mainline builds are fixed... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883243] Re: Hardware issues on lenovo ideapad 5
Just to add details, this laptop series is totally %%""$$$ , I tried in addition mint, manjaro , MX. MX doesn't boot, Fedora - dead touchpad, manjaro - every ~3 rd boot touchpad works + no sound issue (5.4x kernel helps with sound), mint 19.3 - no sound, every ~3rd boot touchpad works, mint 20.0 beta - same. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883243 Title: Hardware issues on lenovo ideapad 5 Status in linux package in Ubuntu: Confirmed Bug description: Concerned Hardware: lenovo Ideapad [specs](https://psref.lenovo.com/Detail/IdeaPad/IdeaPad_5_15ARE05?M=81YQ000FGE) I created a dual boot ubuntu 20.4 alongside windows and also had disabled secure boot in BIOS before installing Ubuntu. However, Touchpad doesn't work Followed troubleshooting guide on https://wiki.ubuntu.com/DebuggingTouchpadDetection. additional issues: 1. the fingerprint reader is not recognized. 2. Suspend doesn't work. On triggering suspend, system wakes up automatically after ~10 seconds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aman 1150 F pulseaudio /dev/snd/controlC0: aman 1150 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 12 13:11:14 2020 InstallationDate: Installed on 2020-06-08 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=b575160b-cafb-40d2-9d33-80230b5f20ab ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
I will have a look (I don’t remember if the grub task is due to the grub.cfg generation or to grub code itself), but TBH, this is low priority on my list (downgrading the bug task priority as such, as this is a multi-system corner-case) ** Changed in: systemd (Ubuntu) Importance: Medium => Low ** Changed in: grub2 (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Fix Released Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867465] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in systemd: Unknown Status in Release Notes for Ubuntu: Fix Released Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Won't Fix Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1867465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884058] [NEW] kernel warning in epyc2 nested virtualization
You have been subscribed to a public bug: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment kvm -- kernel warning in epyc2 nested virtualization https://bugs.launchpad.net/bugs/1884058 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working
Interesting. I came upon this HP form post today that suggest that booting into Windows does something that disables the brightness keys in Linux: https://h30434.www3.hp.com/t5/Notebook-Operating-System-and-Recovery /Brightness-keys-not-working-in-Linux/m-p/7549927/highlight/true#M585533 The OP suggests that re-flashing the BIOS restores functionality. Going to test now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822581 Title: HP 1030 G3 fn-keys not working Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn key combinations are only working partially. What works: Volume up/down/mute, Airplane mode What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator lights I already tried solutions regarding editing the Kernel Parameter acpi_osi in the grub config but can not get the keys to work. In case of screen brightness changing it using the desktop slider works. But it seems, that the keypress isn't recognized at all. Neither xev nor acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone muting (fn+f8). Running showkey -k results in a keycode 465 pressed and released event for all three key combinations. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: udev 239-7ubuntu10.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Apr 1 14:22:47 2019 InstallationDate: Installed on 2019-03-30 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: HP HP EliteBook x360 1030 G3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2019 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.06.00 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.38.00 dmi.chassis.asset.tag: 5CD8427YK5 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook x360 dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 4QZ13ES#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
@Stefan, so actually this is an actual regression. 1015 will boot just fine in LXD with secureboot disabled. 1017 will not boot at all in LXD with or without secureboot disabled. I don't know if it's switching to a signed kernel which causes the lz4 issue but the result is a clear regression so I would not consider this kernel suitable for release to anyone. -- 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/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: Fix Committed Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 80010033, CR2 - , CR3 - 3FC01000 CR4 - 0668, CR8 - DR0 - , DR1 -
[Kernel-packages] [Bug 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
@ddstreet Indeed, https://www.freedesktop.org/software/systemd/man/systemd.net- naming-scheme.html b1 seems to stand for "Broadcom bus (BCMA) core number" So it seems to me that our stock vanilla kernel has gained support for this broadcom wifi chip with proper Broadcom bus support. Yet we also have some other implementation that claims to support the same chip, and then doesn't quite work the same way. I guess wl & bcmwl-kernel-source should not be both declaring support for the same chip? Such that user is not receiving one or the other, at random, or switching between the two, just because they ask installer to enable Nvidia. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: bcmwl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in systemd: Unknown Status in Release Notes for Ubuntu: Fix Released Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Won't Fix Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1867465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884058] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1884058 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884058 Title: kernel warning in epyc2 nested virtualization Status in linux package in Ubuntu: Incomplete Bug description: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09:
[Kernel-packages] [Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
hi, I'm also facing the same problem(stuck while rebooting) and also sometimes my integrated webcam of my laptop (dell vostro) doesnt work since i updated my ubuntu sytem to 18.04 does any one on know what could be the resolution for this problem. thanks!! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hardware: HPE ProLiant DL360 gen9 Ubuntu Version: 18.04 Problem: When rebooting the server, everything goes well (shutting down services, unmounting etc) until the last step where it reads "Starting Reboot". At this point the system is getting stuck and nothing else can can be done than holding the power button in for a long enough time to turn it off. At the same time as the system get stuck, a red error light is lightening up on the server. This light is green until it reaches this "Starting Reboot" stage. The same happens if the server is shutdown, with the difference that the last message is "Starting Power-Off" instead of "Starting Reboot". The server is installed with a new clean 18.04 installation. This server was rebooting/shutting down without a problem with all releases between 16.04 and 17.10. This problem is serious as it prevents remote reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 13 11:16 seq crw-rw 1 root audio 116, 33 Jun 13 11:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/21/2018 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884110] [NEW] Enable ZFS on arm64
Public bug reported: Placeholder ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1884110 Title: Enable ZFS on arm64 Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Focal: New Bug description: Placeholder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1884110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working
Nice! I'll try this as well! Do you have any special Kernel parameters set? And how did you flash the bios? Using the softpaq tool? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822581 Title: HP 1030 G3 fn-keys not working Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn key combinations are only working partially. What works: Volume up/down/mute, Airplane mode What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator lights I already tried solutions regarding editing the Kernel Parameter acpi_osi in the grub config but can not get the keys to work. In case of screen brightness changing it using the desktop slider works. But it seems, that the keypress isn't recognized at all. Neither xev nor acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone muting (fn+f8). Running showkey -k results in a keycode 465 pressed and released event for all three key combinations. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: udev 239-7ubuntu10.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Apr 1 14:22:47 2019 InstallationDate: Installed on 2019-03-30 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: HP HP EliteBook x360 1030 G3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2019 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.06.00 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.38.00 dmi.chassis.asset.tag: 5CD8427YK5 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook x360 dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 4QZ13ES#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
@Simon, you should upgrade the ubuntu-mainline-kernel script, the directory layout on kernel-ppa has changed, so the kernels are in a different location. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working
Can confirm as well! Flashed the BIOS and now it works for me, too! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822581 Title: HP 1030 G3 fn-keys not working Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn key combinations are only working partially. What works: Volume up/down/mute, Airplane mode What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator lights I already tried solutions regarding editing the Kernel Parameter acpi_osi in the grub config but can not get the keys to work. In case of screen brightness changing it using the desktop slider works. But it seems, that the keypress isn't recognized at all. Neither xev nor acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone muting (fn+f8). Running showkey -k results in a keycode 465 pressed and released event for all three key combinations. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: udev 239-7ubuntu10.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Apr 1 14:22:47 2019 InstallationDate: Installed on 2019-03-30 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: HP HP EliteBook x360 1030 G3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2019 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.06.00 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.38.00 dmi.chassis.asset.tag: 5CD8427YK5 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook x360 dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 4QZ13ES#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
I just follow the mentioned before: sudo apt install install alsa-tools then run sudo hda-verb /dev/snd/hwC0D0 0x17 SET_CONNECT_SEL 1 For the changes take effects after reboot: sudo gedit /etc/rc.local and put this on it: #!/bin/sh -e hda-verb /dev/snd/hwC0D0 0x17 SET_CONNECT_SEL 1 exit 0 Now give permission to the file: sudo chmod +x /etc/rc.local reboot and that's it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal Status in alsa-ucm-conf package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14 Audio works and the volume seems reasonable however the audio is noticeably missing bass giving everything a high treble sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-ucm-conf 1.2.2-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 09:17:33 2020 Dependencies: InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-ucm-conf UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: linux PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870971] Re: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API
This problem also occurs in my HP-CW1011la laptop (Ryzen 3500u) while trying to boot on battery. Iĺl try Alexander´s workaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870971 Title: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API Status in linux package in Ubuntu: Confirmed Bug description: Freshly installed Xubuntu 20.04 shows black screen instead of login screen upon boot on Lenovo Ideapad L340-17API. It is not possible to chvt to text terminal when boot is stuck on black screen. Booting with 'nomodeset' kernel option works properly but is not an option (e.g. screen brightness is not adjustable in this case). Another workaround is to ssh to laptop and run systemctl restart display-manager.service. After 5-10 seconds upon executing this command perfectly working login screen appears. Check dmesg. There is apparently related messages from amdgpu driver: ... апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm] recover vram bo from shadow start апр 05 20:46:45 kernel: [drm] recover vram bo from shadow done апр 05 20:46:45 kernel: [drm] Skip scheduling IBs! апр 05 20:46:45 kernel: [ cut here ] апр 05 20:46:45 kernel: WARNING: CPU: 3 PID: 793 at include/linux/dma-fence.h:533 drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Modules linked in: cmac algif_hash algif_skcipher af_alg bnep zram nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt snd_hda_codec > апр 05 20:46:45 kernel: CPU: 3 PID: 793 Comm: kworker/3:4 Tainted: G OE 5.4.0-21-generic #25-Ubuntu апр 05 20:46:45 kernel: Hardware name: LENOVO 81LY/LNVNB161216, BIOS ARCN32WW 07/11/2019 апр 05 20:46:45 kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] апр 05 20:46:45 kernel: RIP: 0010:drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Code: 41 5c 41 5d 41 5e 41 5f 5d c3 49 8b 46 10 31 c9 48 c7 80 80 00 00 00 00 00 00 00 49 8b 7f 70 31 c0 83 e7 01 74 04 0f 0b eb bf <0f> 0b eb c7 0f 0b eb 8b 66 0f 1f 44 00 00 0f 1f 44 00 00 83 7f 4c апр 05 20:46:45 kernel: RSP: 0018:a4dc806d7d28 EFLAGS: 00010246 апр 05 20:46:45 kernel: RAX: RBX: 0001 RCX: апр 05 20:46:45 kernel: RDX: 8cc9a6fc9180 RSI: 8cc9ac4609f8 RDI: апр 05 20:46:45 kernel: RBP: a4dc806d7d60 R08: 047a R09: 0004 апр 05 20:46:45 kernel: R10: R11: 0001 R12: 8cc9ac463c00 апр 05 20:46:45 kernel: R13: 8cc9a63c7980 R14: 8cc9ac460800 R15: 8cc9a6fc9140 апр 05 20:46:45 kernel: FS: () GS:8cc9b88c() knlGS: апр 05 20:46:45 kernel: CS: 0010 DS: ES: CR0: 80050033 апр 05 20:46:45 kernel: CR2: 7f275ff6c000 CR3: 0001af148000 CR4: 003406e0 апр 05 20:46:45 kernel: Call Trace: апр 05 20:46:45 kernel: amdgpu_device_gpu_recover+0x6cd/0x95a [amdgpu] апр 05 20:46:45 kernel: amdgpu_job_timedout+0x103/0x130 [amdgpu] апр 05 20:46:45 kernel: drm_sched_job_timedout+0x44/0x90 [gpu_sched] апр 05 20:46:45 kernel: process_one_work+0x1eb/0x3b0 апр 05 20:46:45
[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working
No special kernel parms (at least that would relate to this). I re- flashed the BIOS by booting into the system utils menu and then choosing "firmware update" or some such. BTW, on my machine (HP EliteBook x360 1030 G4) there's a newer version of the bios that came out recently: R94 Ver. 01.05.03 (04/28/2020). I just upgraded to that. We'll see if it makes any difference. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822581 Title: HP 1030 G3 fn-keys not working Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn key combinations are only working partially. What works: Volume up/down/mute, Airplane mode What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator lights I already tried solutions regarding editing the Kernel Parameter acpi_osi in the grub config but can not get the keys to work. In case of screen brightness changing it using the desktop slider works. But it seems, that the keypress isn't recognized at all. Neither xev nor acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone muting (fn+f8). Running showkey -k results in a keycode 465 pressed and released event for all three key combinations. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: udev 239-7ubuntu10.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Apr 1 14:22:47 2019 InstallationDate: Installed on 2019-03-30 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: HP HP EliteBook x360 1030 G3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2019 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.06.00 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.38.00 dmi.chassis.asset.tag: 5CD8427YK5 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook x360 dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 4QZ13ES#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working
Confirmed. I re-flashed the BIOS, then booted back into Linux, and now my brightness keys work again. Nice to now there's an explanation, and a workaround to fix the issue. Would love to see if there's a Linux code change that can address the root issue though. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822581 Title: HP 1030 G3 fn-keys not working Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn key combinations are only working partially. What works: Volume up/down/mute, Airplane mode What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator lights I already tried solutions regarding editing the Kernel Parameter acpi_osi in the grub config but can not get the keys to work. In case of screen brightness changing it using the desktop slider works. But it seems, that the keypress isn't recognized at all. Neither xev nor acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone muting (fn+f8). Running showkey -k results in a keycode 465 pressed and released event for all three key combinations. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: udev 239-7ubuntu10.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Apr 1 14:22:47 2019 InstallationDate: Installed on 2019-03-30 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: HP HP EliteBook x360 1030 G3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2019 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.06.00 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.38.00 dmi.chassis.asset.tag: 5CD8427YK5 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook x360 dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 4QZ13ES#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824886] Re: Battery level stuck at 100% and Estimating...
Issue sill exist in focal fossa with kernel 5.4. Jumper Ezbook X1 Screenshot with upower and uname output attached. ** Attachment added: "Снимок экрана от 2020-06-18 20-22-47.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824886/+attachment/5385061/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202020-06-18%2020-22-47.png ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824886 Title: Battery level stuck at 100% and Estimating... Status in linux package in Ubuntu: Confirmed Bug description: Battery applet does not display battery charge. Always shows 100%. ASUS 1215T-RED008S. Description: Ubuntu 18.04.2 LTS Release: 18.04 gnome-control-center: Установлен: 1:3.28.2-0ubuntu0.18.04.2 Кандидат: 1:3.28.2-0ubuntu0.18.04.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 00:48:18 2019 InstallationDate: Installed on 2019-04-10 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870971] Re: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API
Alexander´s solution worked just fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870971 Title: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API Status in linux package in Ubuntu: Confirmed Bug description: Freshly installed Xubuntu 20.04 shows black screen instead of login screen upon boot on Lenovo Ideapad L340-17API. It is not possible to chvt to text terminal when boot is stuck on black screen. Booting with 'nomodeset' kernel option works properly but is not an option (e.g. screen brightness is not adjustable in this case). Another workaround is to ssh to laptop and run systemctl restart display-manager.service. After 5-10 seconds upon executing this command perfectly working login screen appears. Check dmesg. There is apparently related messages from amdgpu driver: ... апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm] recover vram bo from shadow start апр 05 20:46:45 kernel: [drm] recover vram bo from shadow done апр 05 20:46:45 kernel: [drm] Skip scheduling IBs! апр 05 20:46:45 kernel: [ cut here ] апр 05 20:46:45 kernel: WARNING: CPU: 3 PID: 793 at include/linux/dma-fence.h:533 drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Modules linked in: cmac algif_hash algif_skcipher af_alg bnep zram nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt snd_hda_codec > апр 05 20:46:45 kernel: CPU: 3 PID: 793 Comm: kworker/3:4 Tainted: G OE 5.4.0-21-generic #25-Ubuntu апр 05 20:46:45 kernel: Hardware name: LENOVO 81LY/LNVNB161216, BIOS ARCN32WW 07/11/2019 апр 05 20:46:45 kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] апр 05 20:46:45 kernel: RIP: 0010:drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Code: 41 5c 41 5d 41 5e 41 5f 5d c3 49 8b 46 10 31 c9 48 c7 80 80 00 00 00 00 00 00 00 49 8b 7f 70 31 c0 83 e7 01 74 04 0f 0b eb bf <0f> 0b eb c7 0f 0b eb 8b 66 0f 1f 44 00 00 0f 1f 44 00 00 83 7f 4c апр 05 20:46:45 kernel: RSP: 0018:a4dc806d7d28 EFLAGS: 00010246 апр 05 20:46:45 kernel: RAX: RBX: 0001 RCX: апр 05 20:46:45 kernel: RDX: 8cc9a6fc9180 RSI: 8cc9ac4609f8 RDI: апр 05 20:46:45 kernel: RBP: a4dc806d7d60 R08: 047a R09: 0004 апр 05 20:46:45 kernel: R10: R11: 0001 R12: 8cc9ac463c00 апр 05 20:46:45 kernel: R13: 8cc9a63c7980 R14: 8cc9ac460800 R15: 8cc9a6fc9140 апр 05 20:46:45 kernel: FS: () GS:8cc9b88c() knlGS: апр 05 20:46:45 kernel: CS: 0010 DS: ES: CR0: 80050033 апр 05 20:46:45 kernel: CR2: 7f275ff6c000 CR3: 0001af148000 CR4: 003406e0 апр 05 20:46:45 kernel: Call Trace: апр 05 20:46:45 kernel: amdgpu_device_gpu_recover+0x6cd/0x95a [amdgpu] апр 05 20:46:45 kernel: amdgpu_job_timedout+0x103/0x130 [amdgpu] апр 05 20:46:45 kernel: drm_sched_job_timedout+0x44/0x90 [gpu_sched] апр 05 20:46:45 kernel: process_one_work+0x1eb/0x3b0 апр 05 20:46:45 kernel: worker_thread+0x4d/0x400 апр 05 20:46:45 kernel: kthread+0x104/0x140 апр 05
[Kernel-packages] [Bug 1884133] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884133 Title: Micro SD card not discovered (O2 Micro, Inc. SD/MMC Card Reader) Status in linux package in Ubuntu: Confirmed Bug description: Hi, Ubuntu 20.04 fails to discover a micro SD card inserted into the "O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01)". I currently have no other card available for testing, but the one I have tested with is a Lexar 32 GB 633x microSDHC UHS-I, according to the packaging. It works well in a digital camera. I tried intstalling exfat-fuse and exfat-utils - that didn't cut it. Thanks! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steinarne 1562 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 18 20:34:15 2020 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2019-08-08 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS0017MX ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=12011978-2f19-446b-afb7-6b82d2459023 ro quiet splash psmouse.elantech_smbus=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 20:34:46.361: The udisks-daemon is running (name-owner :1.9). UpgradeStatus: Upgraded to focal on 2020-04-13 (66 days ago) dmi.bios.date: 05/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET56W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS0017MX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0QET56W(1.33):bd05/05/2019:svnLENOVO:pn20LS0017MX:pvrThinkPadL480:rvnLENOVO:rn20LS0017MX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS0017MX dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882823] Re: int3403 thermal INT3403:00
I also cc'ed stable which includes kernel 5.4. It should be available in kernel 5.4 automatically when (and if) it lands into mainline kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882823 Title: int3403 thermal INT3403:00 Status in linux package in Ubuntu: Confirmed Bug description: [8.112761] int3403 thermal INT3403:00: Unsupported event [0x91] [ 10.121722] int3403 thermal INT3403:00: Unsupported event [0x91] [ 12.165233] int3403 thermal INT3403:00: Unsupported event [0x91] Is constantly flooding my dmesg. I believe this is also due to missing audio drivers as well. Which is another issue that I am facing. Realtek ALC1220 Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884133] [NEW] Micro SD card not discovered (O2 Micro, Inc. SD/MMC Card Reader)
Public bug reported: Hi, Ubuntu 20.04 fails to discover a micro SD card inserted into the "O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01)". I currently have no other card available for testing, but the one I have tested with is a Lexar 32 GB 633x microSDHC UHS-I, according to the packaging. It works well in a digital camera. I tried intstalling exfat-fuse and exfat-utils - that didn't cut it. Thanks! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steinarne 1562 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 18 20:34:15 2020 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2019-08-08 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS0017MX ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=12011978-2f19-446b-afb7-6b82d2459023 ro quiet splash psmouse.elantech_smbus=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 20:34:46.361: The udisks-daemon is running (name-owner :1.9). UpgradeStatus: Upgraded to focal on 2020-04-13 (66 days ago) dmi.bios.date: 05/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET56W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS0017MX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0QET56W(1.33):bd05/05/2019:svnLENOVO:pn20LS0017MX:pvrThinkPadL480:rvnLENOVO:rn20LS0017MX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS0017MX dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884133 Title: Micro SD card not discovered (O2 Micro, Inc. SD/MMC Card Reader) Status in linux package in Ubuntu: Confirmed Bug description: Hi, Ubuntu 20.04 fails to discover a micro SD card inserted into the "O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01)". I currently have no other card available for testing, but the one I have tested with is a Lexar 32 GB 633x microSDHC UHS-I, according to the packaging. It works well in a digital camera. I tried intstalling exfat-fuse and exfat-utils - that didn't cut it. Thanks! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steinarne 1562 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 18 20:34:15 2020 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2019-08-08 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS0017MX ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=12011978-2f19-446b-afb7-6b82d2459023 ro quiet splash psmouse.elantech_smbus=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 20:34:46.361: The udisks-daemon is running (name-owner :1.9). UpgradeStatus: Upgraded
[Kernel-packages] [Bug 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
@MarkF (az2008) What you have experienced is abnormal. Normally there is only one driver for device, we offer the best driver we have, and once connected to the internet, the connection persists without any disconnects. And copies wifi config into the target installed system. Such that one never has to type the WiFi password a second time. I'm trying to troubleshoot what went wrong. As normally, we shouldn't cause such disruption at all. And thus there should be no need for confusing popups saying things about disconnects, waiting, redoing things. ** Tags removed: rls-ff-notfixing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in systemd: Unknown Status in Release Notes for Ubuntu: Fix Released Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Won't Fix Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1867465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
@Alberto Milone Something odd is happening for the user of BCM4313 wifi chip. The devices appears to jump from bus1 to bus0, and thus getting a new name. Or as if, there are two different drivers offered to the user and/or operational via different buses. Such that udev identifies the same card on bus1 at first, and then later at bus0 and thus generates wlp2s0b1 name at first, and then wlp2s0 device name (not that when bus is 0, b0 is ommitted). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in systemd: Unknown Status in Release Notes for Ubuntu: Fix Released Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Won't Fix Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1867465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884159] [NEW] Update lockdown patches
Public bug reported: Impact: The lockdown patches have evolved over time, and part of this was restricting more areas of the kernel. Not all of these additions were backported, and some can lead to lockdown bypasses, see [1] and [2]. Fix: Backport newer lockdown restrictions to older releases. Test Case: Test cases for most of the backports can be found at [3], and [4] is another test case. Some which need e.g. specific hardware to test have not been tested. Regression Potential: Most of these are small, simple fixes with low potential for regression. Users may also lose access to some functionality previously accissible under secure boot. Some changes are more substantial, especially the hw_param changes for xenial, but they are based on well-tested upstream code. The xmon backports also carry a more moderate risk of regression. [1] https://lists.ubuntu.com/archives/kernel-team/2020-June/111050.html [2] https://lore.kernel.org/lkml/20200615104332.901519-1-ja...@zx2c4.com/ [3] https://git.launchpad.net/~sforshee/+git/lockdown-tests [4] https://git.zx2c4.com/american-unsigned-language/tree/american-unsigned-language.sh ** Affects: linux (Ubuntu) Importance: Critical Assignee: Seth Forshee (sforshee) Status: Fix Committed ** Affects: linux (Ubuntu Xenial) Importance: Critical Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Critical Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: linux (Ubuntu Eoan) Importance: Critical Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Critical Assignee: Seth Forshee (sforshee) Status: In Progress ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884159 Title: Update lockdown patches Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: Impact: The lockdown patches have evolved over time, and part of this was restricting more areas of the kernel. Not all of these additions were backported, and some can lead to lockdown bypasses, see [1] and [2]. Fix: Backport newer lockdown restrictions to older releases. Test Case: Test cases for most of the backports can be found at [3], and [4] is another test case. Some which need e.g. specific hardware to test have not been tested. Regression Potential: Most of these are small, simple fixes with low potential for regression. Users may also lose access to some functionality previously accissible under secure boot. Some changes are more substantial, especially the hw_param changes for xenial, but they are based on well-tested upstream code. The xmon backports also carry a more moderate risk of regression. [1] https://lists.ubuntu.com/archives/kernel-team/2020-June/111050.html [2] https://lore.kernel.org/lkml/20200615104332.901519-1-ja...@zx2c4.com/ [3] https://git.launchpad.net/~sforshee/+git/lockdown-tests [4] https://git.zx2c4.com/american-unsigned-language/tree/american-unsigned-language.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1881828] Re: Lenovo X1 Extreme screen never wakes up
I attempted to get a bisect going but failed. These commit logs look promising though as to where the fix lies. ~/git/mainline-crack$ git log --oneline v5.6.6..v5.6.7 -- ./drivers/gpu/drm/nouveau/ 360aba644f1f drm/nouveau/gr/gp107,gp108: implement workaround for HW hanging during init dd4a3179e04c drm/nouveau: workaround runpm fail by disabling PCI power management on certain intel bridges bca4d36a2a11 drm/nouveau/svm: fix vma range check for migration ded30f112b5e drm/nouveau/svm: check for SVM initialized before migrating Playing along from https://wiki.ubuntu.com/Kernel/KernelBisection#Reverse_bisecting_upstream_kernel_versions I did this and got a segfault in git. Whoops. Not sure where to go from here. ~/git/mainline-crack$ git checkout v5.6.7 Updating files: 100% (11314/11314), done. Note: switching to 'v5.6.7'. ... HEAD is now at 55b2af1c23eb Linux 5.6.7 ~/git/mainline-crack$ git bisect start drivers/gpu/drm/nouveau/ Segmentation fault (core dumped) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881828 Title: Lenovo X1 Extreme screen never wakes up Status in linux package in Ubuntu: Confirmed Bug description: Unreliably, but 9 times out of 10, if my screen goes to sleep on my laptop it will never wake back up. Looking in kern.log I see this output, scrolling on repeat, until I long-press the power button to shut off the laptop. Happened occasionally in Ubuntu 19.10, now regularly on 20.04. Persisted with the nvidia proprietary driver as well as the open source one. It has persisted across several official ubuntu packaged kernel revisions. I got kernel taint down to "0" and it kept happening. (Previously virtualbox and nvidia driver were in there.) May 26 20:02:30 hawk-x1 kernel: [28401.972981] No Local Variables are initialized for Method [NVPO] May 26 20:02:30 hawk-x1 kernel: [28401.972986] No Arguments are initialized for method [NVPO] May 26 20:02:30 hawk-x1 kernel: [28401.972991] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.NVPO due to previous error (AE_AML_LOOP_TIMEOUT) (20190816/psparse-529) May 26 20:02:30 hawk-x1 kernel: [28401.973016] ACPI Error: Aborting method \_SB.PCI0.PGON due to previous error (AE_AML_LOOP_TIMEOUT) (20190816/psparse-529) May 26 20:02:30 hawk-x1 kernel: [28401.973033] ACPI Error: Aborting method \_SB.PCI0.PEG0.PG00._ON due to previous error (AE_AML_LOOP_TIMEOUT) (20190816/psparse-529) May 26 20:02:30 hawk-x1 kernel: [28401.973058] acpi device:00: Failed to change power state to D0 May 26 20:02:31 hawk-x1 kernel: [28403.217052] video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) May 26 20:02:31 hawk-x1 kernel: [28403.217064] nouveau :01:00.0: Refused to change power state, currently in D3 May 26 20:02:31 hawk-x1 kernel: [28403.277092] video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) May 26 20:02:31 hawk-x1 kernel: [28403.296906] nouveau :01:00.0: Refused to change power state, currently in D3 May 26 20:02:31 hawk-x1 kernel: [28403.296915] video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) May 26 20:02:31 hawk-x1 kernel: [28403.316894] nouveau :01:00.0: Refused to change power state, currently in D3 May 26 20:02:31 hawk-x1 kernel: [28403.319495] nouveau :01:00.0: tmr: stalled at May 26 20:02:31 hawk-x1 kernel: [28403.319497] [ cut here ] May 26 20:02:31 hawk-x1 kernel: [28403.319498] nouveau :01:00.0: timeout May 26 20:02:31 hawk-x1 kernel: [28403.319551] WARNING: CPU: 2 PID: 2697 at drivers/gpu/drm/nouveau/nvkm/subdev/bar/g84.c:35 g84_bar_flush+0xd6/0xe0 [nouveau] May 26 20:02:31 hawk-x1 kernel: [28403.319552] Modules linked in: xt_conntrack xt_MASQUERADE nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_addrtype bpfilter ccm overlay aufs bnep binfmt_misc nls_iso8859_1 mei_hdcp intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt iwlmvm snd_sof_intel_ipc snd_sof mac80211 uvcvideo snd_sof_xtensa_dsp snd_hda_ext_core videobuf2_vmalloc snd_soc_acpi_intel_match videobuf2_memops snd_soc_acpi btusb libarc4 videobuf2_v4l2 btrtl videobuf2_common btbcm wmi_bmof thinkpad_acpi input_leds joydev snd_hda_codec_realtek btintel snd_soc_core snd_seq_midi videodev bluetooth snd_hda_codec_generic serio_raw snd_seq_midi_event nvram snd_compress ac97_bus intel_wmi_thunderbolt snd_pcm_dmaengine ledtrig_audio mc iwlwifi snd_rawmidi ecdh_generic 8250_dw ecc snd_hda_intel mei_me cfg80211 May 26 20:02:31 hawk-x1 kernel: [28403.319567] snd_intel_dspcfg mei snd_hda_codec snd_seq snd_hda_core ucsi_acpi snd_hwdep
[Kernel-packages] [Bug 1870260] Re: initramfs unpacking failed: Decoding failed", message appears on boot up.
@cpg100: did you made an update-initramfs -u ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870260 Title: initramfs unpacking failed: Decoding failed", message appears on boot up. Status in linux package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: OS : Ubuntu 20.04(20200401) Problem: "initramfs unpacking failed: Decoding failed", message appears on boot up solution: If we edit /etc/initramfs-tools/initramfs.conf and COMPRESS=lz4, to COMPRESS=gzip then the error is fixing . Expected solution: This but in there from a long time I have seen this from Ubuntu 18.04,19.04,19.10 now in 20.04 So please fix it or change it from lz4 to gzip. an early reply is highly appreciated Thank you . --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tamal 1451 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx Package: ubuntu-meta ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=29f895bf-ab7b-4df8-8e9a-c277376a2685 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd11/29/2019:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 5AY34PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in systemd: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in bcmwl package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Won't Fix Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1867465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877270] Re: Devlink - add RoCE disable kernel support
Pushing patches for this bug to this branch:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1877270-pull-roce-disable-from-5.5
** Description changed:
[Impact]
RoCE disable feature was added to the kernel v5.5.
This feature was requested by Mellanox customers that use Ubuntu 20.04,
and it's a very high important to deliver this feature to the customers
in one of ubuntu 20.04 SRU.
[SHORT DESCRIPTION]
RoCE enablement state controls driver support for RoCE traffic.
When RoCE is disabled, there is no gid table, only raw ethernet QPs are
supported and traffic on the well known UDP RoCE port is handled as raw
ethernet traffic.
[Test Case]
To change RoCE enablement state a user must change the driverinit cmode
value and run devlink reload.
User command examples:
- Disable RoCE::
$ devlink dev param set pci/:06:00.0 name enable_roce value false
cmode driverinit
$ devlink dev reload pci/:06:00.0
- Read RoCE enablement state::
$ devlink dev param show pci/:06:00.0 name enable_roce
pci/:06:00.0:
name enable_roce type generic
values:
cmode driverinit value true
[Regression Potential]
This feature shouldn't affect the regression because it's only adding support
for
RoCE enable/disable.
Also,
This feature was tested internally by Mellanox QA teams
those tests logs/results are private unfortunately i can't share it here
[Other Info]
Feature patchset:
- 4383cfcc65e7 net/mlx5: Add devlink reload
+ 4383cfcc65e7 net/mlx5: Add devlink reload
32680da71034 net/mlx5: Remove unneeded variable in mlx5_unload_one
94de879c28d8 IB/mlx5: Load profile according to RoCE enablement state
b5a498baf929 IB/mlx5: Rename profile and init methods
cc9defcbb8fa net/mlx5: Handle "enable_roce" devlink param
e90cde0d76f0 net/mlx5: Document flow_steering_mode devlink param
6c7295e13ffd devlink: Add new "enable_roce" generic device param
- 070c63f20f6c ("net: devlink: allow to change namespaces during
- reload")## This one does not apply cleanly
-
All are in upstream in 5.5, so no pick into Groovy necessary
userspace:
No userspace dependency on this. the feature uses the devlink
param functionality which already exists in UB20.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877270
Title:
Devlink - add RoCE disable kernel support
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Bug description:
[Impact]
RoCE disable feature was added to the kernel v5.5.
This feature was requested by Mellanox customers that use Ubuntu 20.04,
and it's a very high important to deliver this feature to the customers
in one of ubuntu 20.04 SRU.
[SHORT DESCRIPTION]
RoCE enablement state controls driver support for RoCE traffic.
When RoCE is disabled, there is no gid table, only raw ethernet QPs are
supported and traffic on the well known UDP RoCE port is handled as raw
ethernet traffic.
[Test Case]
To change RoCE enablement state a user must change the driverinit
cmode value and run devlink reload.
User command examples:
- Disable RoCE::
$ devlink dev param set pci/:06:00.0 name enable_roce value false
cmode driverinit
$ devlink dev reload pci/:06:00.0
- Read RoCE enablement state::
$ devlink dev param show pci/:06:00.0 name enable_roce
pci/:06:00.0:
name enable_roce type generic
values:
cmode driverinit value true
[Regression Potential]
This feature shouldn't affect the regression because it's only adding support
for
RoCE enable/disable.
Also,
This feature was tested internally by Mellanox QA teams
those tests logs/results are private unfortunately i can't share it here
[Other Info]
Feature patchset:
4383cfcc65e7 net/mlx5: Add devlink reload
32680da71034 net/mlx5: Remove unneeded variable in mlx5_unload_one
94de879c28d8 IB/mlx5: Load profile according to RoCE enablement state
b5a498baf929 IB/mlx5: Rename profile and init methods
cc9defcbb8fa net/mlx5: Handle "enable_roce" devlink param
e90cde0d76f0 net/mlx5: Document flow_steering_mode devlink param
6c7295e13ffd devlink: Add new "enable_roce" generic device param
All are in upstream in 5.5, so no pick into Groovy necessary
userspace:
No userspace dependency on this. the feature uses the devlink
param functionality which already exists in UB20.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877270/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe :
[Kernel-packages] [Bug 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4 kernel
** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Eoan) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826848 Title: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4 kernel Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: [Impact] Failure to run ip_defrag deterministically. [Fix] Use smaller packets and ignore EPERM. [Test case] Run the test multiple times without observing failures. [Regression potential] If the test fix is incorrect, it will cause us to miss real kernel bugs. But as it is now, we are already ignoring its results. == Test failed becuase: ./ip_defrag: sendto overlap: 1400: Operation not permitted selftests: net: ip_defrag.sh ipv6 tx:17 gso:1 (fail) OK ipv4 defrag PASS seed = 1556203721 ipv4 defrag with overlaps PASS seed = 1556203722 ipv6 defrag seed = 1556203756 PASS ipv6 defrag with overlaps seed = 1556203756 ./ip_defrag: sendto overlap: 1400: Operation not permitted not ok 1..17 selftests: net: ip_defrag.sh [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1826848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873194] Re: clipit interface not working in 20.04
Hello, bug is patched upstream. Download deb file from project github page. https://github.com/CristianHenzel/ClipIt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873194 Title: clipit interface not working in 20.04 Status in clipit package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When running clipit in focal fossa the interface will crash when opening the history list via shortcut (ctr + alt + h). Starting it from cli shows this error message: (clipit:7248): Gdk-CRITICAL **: 10:42:40.873: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed Clipit version is 1.4.4+git20190202-1 from https://launchpad.net/ubuntu/focal/+package/clipit Ubuntu version is Ubuntu Focal Fossa (20.04) as of 2nd of May 2020 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-04-29 (1447 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal third-party-packages Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-15 (0 days ago) UserGroups: adm cdrom dip docker kismet kvm lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clipit/+bug/1873194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884100] [NEW] Qualcomm Atheros QCA6174 802.11ac fails in linux-firmware 1.187
Public bug reported: This bug is done for a friend. I do talk to him occasionally and he sends me data. As he's a newbie, he doesn't know how to create a proper bug report. Basically, his notebook has the Qualcomm Atheros QCA6174 802.11ac wireless network adapter (rev 32). He had Ubuntu 19.10 and it worked. He updated to 20.04 and it stopped working. He installed 20.04 from scratch and it did not work. 20.04's linux-firmware is 1.187. This version does not work for Qualcomm Atheros QCA6174 802.11ac. I asked him to download 19.10's linux-firmware package from the ubuntu repositories, which is at 1.183. After he installed, apt-marked hold the package so that it would not be upgrade, and rebooted, his wifi worked. I saw the other bug reports regarding this adapter but they are old, the newer one has expired and it seems to be related to the unsigned kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patola 2713 F pulseaudio /dev/snd/controlC1: patola 2713 F pulseaudio /dev/snd/controlC2: patola 2713 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ICEWM Date: Thu Jun 18 18:09:22 2020 Dependencies: HibernationDevice: RESUME=UUID=b9874cf9-f129-4697-aa86-b24082733ed5 InstallationDate: Installed on 2018-01-08 (892 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=/dev/mapper/ryzenvg-rootlv ro nvidia-drm.modeset=1 noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off tsx=on tsx_async_abort=off mitigations=off RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux-firmware UpgradeStatus: Upgraded to focal on 2020-05-01 (47 days ago) dmi.bios.date: 09/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5220 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5220:bd09/12/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=s mtime.conffile..etc.default.apport: 2018-12-08T09:39:42.468905 ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1884100 Title: Qualcomm Atheros QCA6174 802.11ac fails in linux-firmware 1.187 Status in linux-firmware package in Ubuntu: New Bug description: This bug is done for a friend. I do talk to him occasionally and he sends me data. As he's a newbie, he doesn't know how to create a proper bug report. Basically, his notebook has the Qualcomm Atheros QCA6174 802.11ac wireless network adapter (rev 32). He had Ubuntu 19.10 and it worked. He updated to 20.04 and it stopped working. He installed 20.04 from scratch and it did not work. 20.04's linux-firmware is 1.187. This version does not work for Qualcomm Atheros QCA6174 802.11ac. I asked him to download 19.10's linux-firmware package from the ubuntu repositories, which is at 1.183. After he installed, apt-marked hold the package so that it would not be upgrade, and rebooted, his wifi worked. I saw the other bug reports regarding this adapter but they are old, the newer one has expired and it seems to be related to the unsigned kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion:
[Kernel-packages] [Bug 1884058] Re: kernel warning in epyc2 nested virtualization
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884058 Title: kernel warning in epyc2 nested virtualization Status in linux package in Ubuntu: New Bug description: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884058/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884058] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385059/+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/1884058 Title: kernel warning in epyc2 nested virtualization Status in linux package in Ubuntu: Confirmed Bug description: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 18 18:55 seq crw-rw 1 root audio 116, 33 Jun 18 18:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion:
[Kernel-packages] [Bug 1884058] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385058/+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/1884058 Title: kernel warning in epyc2 nested virtualization Status in linux package in Ubuntu: Confirmed Bug description: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 18 18:55 seq crw-rw 1 root audio 116, 33 Jun 18 18:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
[Kernel-packages] [Bug 1884058] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385051/+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/1884058 Title: kernel warning in epyc2 nested virtualization Status in linux package in Ubuntu: Confirmed Bug description: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 18 18:55 seq crw-rw 1 root audio 116, 33 Jun 18 18:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion:
[Kernel-packages] [Bug 1884058] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385053/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884058 Title: kernel warning in epyc2 nested virtualization Status in linux package in Ubuntu: Confirmed Bug description: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 18 18:55 seq crw-rw 1 root audio 116, 33 Jun 18 18:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion:
[Kernel-packages] [Bug 1884058] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385054/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884058 Title: kernel warning in epyc2 nested virtualization Status in linux package in Ubuntu: Confirmed Bug description: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 18 18:55 seq crw-rw 1 root audio 116, 33 Jun 18 18:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion:
[Kernel-packages] [Bug 1884058] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385057/+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/1884058 Title: kernel warning in epyc2 nested virtualization Status in linux package in Ubuntu: Confirmed Bug description: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 18 18:55 seq crw-rw 1 root audio 116, 33 Jun 18 18:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
[Kernel-packages] [Bug 1884058] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385060/+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/1884058 Title: kernel warning in epyc2 nested virtualization Status in linux package in Ubuntu: Confirmed Bug description: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 18 18:55 seq crw-rw 1 root audio 116, 33 Jun 18 18:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
[Kernel-packages] [Bug 1884058] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385055/+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/1884058 Title: kernel warning in epyc2 nested virtualization Status in linux package in Ubuntu: Confirmed Bug description: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 18 18:55 seq crw-rw 1 root audio 116, 33 Jun 18 18:55 timer AplayDevices: Error: [Errno 2] No such file or directory:
[Kernel-packages] [Bug 1884058] Re: kernel warning in epyc2 nested virtualization
apport-collect info has been collected ** 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/1884058 Title: kernel warning in epyc2 nested virtualization Status in linux package in Ubuntu: Confirmed Bug description: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 18 18:55 seq crw-rw 1 root audio 116, 33 Jun 18 18:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.3
[Kernel-packages] [Bug 1884058] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385049/+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/1884058 Title: kernel warning in epyc2 nested virtualization Status in linux package in Ubuntu: Confirmed Bug description: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 18 18:55 seq crw-rw 1 root audio 116, 33 Jun 18 18:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
[Kernel-packages] [Bug 1884058] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385050/+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/1884058 Title: kernel warning in epyc2 nested virtualization Status in linux package in Ubuntu: Confirmed Bug description: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 18 18:55 seq crw-rw 1 root audio 116, 33 Jun 18 18:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion:
[Kernel-packages] [Bug 1884058] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385052/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884058 Title: kernel warning in epyc2 nested virtualization Status in linux package in Ubuntu: Confirmed Bug description: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 18 18:55 seq crw-rw 1 root audio 116, 33 Jun 18 18:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion:
[Kernel-packages] [Bug 1884058] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1884058/+attachment/5385056/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884058 Title: kernel warning in epyc2 nested virtualization Status in linux package in Ubuntu: Confirmed Bug description: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 18 18:55 seq crw-rw 1 root audio 116, 33 Jun 18 18:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
[Kernel-packages] [Bug 1884058] Re: kernel warning in epyc2 nested virtualization
apport information ** Tags added: apport-collected ** Description changed: [1115784.899520] [ cut here ] [1115784.899551] WARNING: CPU: 17 PID: 799578 at arch/x86/kvm/mmu.c:2237 nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899551] Modules linked in: vhost_net vhost tap nf_tables ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_comment xt_tcpudp xt_state xt_conntrack iptable_mangle iptable_nat iptable_filter bpfilter 8021q garp mrp stp llc binfmt_misc ipmi_ssif amd64_edac_mod edac_mce_amd kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper nls_iso8859_1 input_leds joydev ast ceph drm_vram_helper ttm libceph drm_kms_helper fscache i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt nfnetlink_cttimeout nfnetlink ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler mac_hid openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c sch_fq_codel drm ip_tables x_tables autofs4 hid_generic usbhid ahci crc32_pclmul nvme hid libahci nvme_core bnxt_en i2c_piix4 i40e [1115784.899594] CPU: 17 PID: 799578 Comm: CPU 1/KVM Not tainted 5.4.0-29-generic #33-Ubuntu [1115784.899595] Hardware name: Supermicro AS -1113S-WN10RT/H11SSW-NT, BIOS 2.1 02/21/2020 [1115784.899615] RIP: 0010:nonpaging_update_pte+0x9/0x10 [kvm] [1115784.899617] Code: 00 0f 1f 44 00 00 55 31 c0 48 89 e5 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 <0f> 0b 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 f0 48 89 e5 48 85 c9 [1115784.899618] RSP: 0018:b039ccc1ba80 EFLAGS: 00010202 [1115784.899620] RAX: c07c4f10 RBX: 8f009d2e7000 RCX: b039ccc1bac8 [1115784.899621] RDX: 8f009d2e7000 RSI: 8f00987e6f18 RDI: 8f00a39bbc90 [1115784.899622] RBP: b039ccc1ba80 R08: R09: b039e05a4000 [1115784.899623] R10: 000b R11: 8f00984e0008 R12: 8f00987e6f18 [1115784.899624] R13: 8f00a39bbc90 R14: 0701 R15: b039ccc1bad0 [1115784.899625] FS: 7fecceffd700() GS:8f01ce64() knlGS: [1115784.899626] CS: 0010 DS: ES: CR0: 80050033 [1115784.899627] CR2: 55d27ce2e218 CR3: 007d26852000 CR4: 00340ee0 [1115784.899628] Call Trace: [1115784.899653] kvm_mmu_pte_write+0x435/0x440 [kvm] [1115784.899675] kvm_page_track_write+0x7f/0xb0 [kvm] [1115784.899695] emulator_write_phys+0x40/0x50 [kvm] [1115784.899712] write_emulate+0xe/0x10 [kvm] [1115784.899730] emulator_read_write_onepage+0xf9/0x320 [kvm] [1115784.899746] emulator_read_write+0xdc/0x190 [kvm] [1115784.899763] emulator_write_emulated+0x15/0x20 [kvm] [1115784.899784] segmented_write+0x60/0x90 [kvm] [1115784.899801] writeback+0x187/0x310 [kvm] [1115784.899820] x86_emulate_insn+0xa1c/0x1260 [kvm] [1115784.899837] x86_emulate_instruction+0x358/0x720 [kvm] [1115784.899853] complete_emulated_pio+0x3f/0x70 [kvm] [1115784.899871] kvm_arch_vcpu_ioctl_run+0x551/0x590 [kvm] [1115784.899888] kvm_vcpu_ioctl+0x24b/0x610 [kvm] [1115784.899894] ? __seccomp_filter+0x7e/0x690 [1115784.899898] ? futex_wake+0x8b/0x180 [1115784.899903] do_vfs_ioctl+0x407/0x670 [1115784.899905] ? __secure_computing+0x42/0xe0 [1115784.899907] ksys_ioctl+0x67/0x90 [1115784.899908] __x64_sys_ioctl+0x1a/0x20 [1115784.899911] do_syscall_64+0x57/0x190 [1115784.899914] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1115784.899915] RIP: 0033:0x7fed0138d37b [1115784.899916] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [1115784.899916] RSP: 002b:7fecceffc5b8 EFLAGS: 0246 ORIG_RAX: 0010 [1115784.899917] RAX: ffda RBX: ae80 RCX: 7fed0138d37b [1115784.899917] RDX: RSI: ae80 RDI: 0025 [1115784.899918] RBP: 562bce39e940 R08: 562bcc1affb0 R09: 0200 [1115784.899918] R10: 0001 R11: 0246 R12: [1115784.899919] R13: 562bcc81c960 R14: 0004 R15: [1115784.899920] ---[ end trace 6282d0248ce1f9fe ]--- + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jun 18 18:55 seq + crw-rw 1 root audio 116, 33 Jun 18 18:55 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.3 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + HibernationDevice: RESUME=none + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' +
[Kernel-packages] [Bug 1310717] Re: process segfaults, hung task timeouts
I'm sorry, I can't recall that system very well at this point. "gmain" is the generic name used by any application using glib's g_get_worker_context() function to create worker threads. At this point I can't even recall if I booted that system with X11 / lightdm or if I had configured it to boot to multiuser only. About the only thing I used that system for was tmux and irssi, neither of which are using the thread name 'gmain' in Xenial, so they were probably also not using the name in Saucy. So, it would have been supplied by 'standard' system software, not something I chose to run myself. My pandaboard es killed SD cards pretty quickly, I came away with the impression that SD cards are basically garbage not intended for 'real' system use: segfaults and bus faults were the common symptom, and this may have been a symptom of rubbish SD card too. Thanks ** Changed in: linux-ti-omap4 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1310717 Title: process segfaults, hung task timeouts Status in linux-ti-omap4 package in Ubuntu: Incomplete Bug description: My pandaboard ES runs irssi in a tmux session for me; irssi has died of segfaults twice recently, and dmesg had these warnings: [395523.456237] PLL GO bit not set [395523.456604] omapdss HDMI error: failed to power on device [395523.458251] [drm] Cannot find any crtc or sizes - going 1024x768 [511971.446472] INFO: task gmain:28222 blocked for more than 120 seconds. [511971.446899] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [511971.447387] gmain D c0592de8 0 28222 1414 0x0200 [511971.447479] [] (__schedule+0x65c/0x7ec) from [] (schedule+0x94/0x98) [511971.447570] [] (schedule+0x94/0x98) from [] (exit_mm+0xc0/0x138) [511971.447601] [] (exit_mm+0xc0/0x138) from [] (do_exit+0x220/0x7e8) [511971.447662] [] (do_exit+0x220/0x7e8) from [] (do_group_exit+0x94/0xd0) [511971.447723] [] (do_group_exit+0x94/0xd0) from [] (get_signal_to_deliver+0x4f0/0x568) [511971.447784] [] (get_signal_to_deliver+0x4f0/0x568) from [] (do_signal+0x94/0x4ec) [511971.447814] [] (do_signal+0x94/0x4ec) from [] (do_notify_resume+0x28/0x64) [511971.447875] [] (do_notify_resume+0x28/0x64) from [] (work_pending+0x28/0x2c) [512091.451538] INFO: task gmain:28222 blocked for more than 120 seconds. [512091.451965] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [512091.452453] gmain D c0592de8 0 28222 1414 0x0200 [512091.452514] [] (__schedule+0x65c/0x7ec) from [] (schedule+0x94/0x98) [512091.452575] [] (schedule+0x94/0x98) from [] (exit_mm+0xc0/0x138) [512091.452606] [] (exit_mm+0xc0/0x138) from [] (do_exit+0x220/0x7e8) [512091.452667] [] (do_exit+0x220/0x7e8) from [] (do_group_exit+0x94/0xd0) [512091.452728] [] (do_group_exit+0x94/0xd0) from [] (get_signal_to_deliver+0x4f0/0x568) [512091.452789] [] (get_signal_to_deliver+0x4f0/0x568) from [] (do_signal+0x94/0x4ec) [512091.452819] [] (do_signal+0x94/0x4ec) from [] (do_notify_resume+0x28/0x64) [512091.452880] [] (do_notify_resume+0x28/0x64) from [] (work_pending+0x28/0x2c) [512211.444030] INFO: task gmain:28222 blocked for more than 120 seconds. [512211.444183] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.$ [512211.444366] gmain D c0592de8 0 28222 1414 0x0200 [512211.27] [] (__schedule+0x65c/0x7ec) from [] (schedule+0x94/0x98) [512211.27] [] (schedule+0x94/0x98) from [] (exit_mm+0xc0/0x138) [512211.58] [] (exit_mm+0xc0/0x138) from [] (do_exit+0x220/0x7e8) [512211.58] [] (do_exit+0x220/0x7e8) from [] (do_group_exit+0x94/0xd0) [512211.88] [] (do_group_exit+0x94/0xd0) from [] (get_signal_to_deliver+0x4f0/0x568) [512211.444519] [] (get_signal_to_deliver+0x4f0/0x568) from [] (do_signal+0x94/0x4ec) [512211.444549] [] (do_signal+0x94/0x4ec) from [] (do_notify_resume+0x28/0x64) [512211.444549] [] (do_notify_resume+0x28/0x64) from [] (work_pending+0x28/0x2c) [512331.443237] INFO: task gmain:28222 blocked for more than 120 seconds. [512331.443389] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.$ [512331.443511] gmain D c0592de8 0 28222 1414 0x0200 [512331.443542] [] (__schedule+0x65c/0x7ec) from [] (schedule+0x94/0x98)$ [512331.443572] [] (schedule+0x94/0x98) from [] (exit_mm+0xc0/0x138) [512331.443572] [] (exit_mm+0xc0/0x138) from [] (do_exit+0x220/0x7e8)$ [512331.443603] [] (do_exit+0x220/0x7e8) from [] (do_group_exit+0x94/0xd0) [512331.443634] [] (do_group_exit+0x94/0xd0) from [] (get_signal_to_deliver+0x4f0/0x568)$ [512331.443634] [] (get_signal_to_deliver+0x4f0/0x568) from [] (do_signal+0x94/0x4ec) [512331.443664] [] (do_signal+0x94/0x4ec) from []
