[Kernel-packages] [Bug 1815844] 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 1815844 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1815844 Title: iscsi multipath dm-N device only used on first volume attachment Status in OpenStack nova-compute charm: Invalid Status in OpenStack Compute (nova): Invalid Status in os-brick: Invalid Status in linux package in Ubuntu: Incomplete Bug description: With nova-compute from cloud:xenial-queens and use-multipath=true iscsi multipath is configured and the dm-N devices used on the first attachment but subsequent attachments only use a single path. The back-end storage is a Purestorage array. The multipath.conf is attached The issue is easily reproduced as shown below: jog@pnjostkinfr01:~⟫ openstack volume create pure2 --size 10 --type pure +-+--+ | Field | Value| +-+--+ | attachments | [] | | availability_zone | nova | | bootable| false| | consistencygroup_id | None | | created_at | 2019-02-13T23:07:40.00 | | description | None | | encrypted | False| | id | e286161b-e8e8-47b0-abe3-4df411993265 | | migration_status| None | | multiattach | False| | name| pure2| | properties | | | replication_status | None | | size| 10 | | snapshot_id | None | | source_volid| None | | status | creating | | type| pure | | updated_at | None | | user_id | c1fa4ae9a0b446f2ba64eebf92705d53 | +-+--+ jog@pnjostkinfr01:~⟫ openstack volume show pure2 ++--+ | Field | Value| ++--+ | attachments| [] | | availability_zone | nova | | bootable | false| | consistencygroup_id| None | | created_at | 2019-02-13T23:07:40.00 | | description| None | | encrypted | False| | id | e286161b-e8e8-47b0-abe3-4df411993265 | | migration_status | None | | multiattach| False| | name | pure2| | os-vol-host-attr:host | cinder@cinder-pure#cinder-pure | | os-vol-mig-status-attr:migstat | None | | os-vol-mig-status-attr:name_id | None | | os-vol-tenant-attr:tenant_id | 9be499fd1eee48dfb4dc6faf3cc0a1d7 | | properties | | | replication_status | None | | size | 10 | | snapshot_id| None | | source_volid | None | | status | available| | type | pure | | updated_at | 201
[Kernel-packages] [Bug 1880943] Re: [focal] disk I/O performance regression
Thank you for the suggestion to test mainline. Regarding the kernel parameters: The test is run on the host and not in a virtual machine, for completeness I have removed the iommu and vf related kernel parameters and they do not affect the outcome of the test. Unfortunately using the mainline kernel does not appear to help on the machines in question: # cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.7.0-050700rc7-generic root=UUID=99527048-4021-4a56-a7d3-21c6cb761879 ro # uname -a Linux node-mees 5.7.0-050700rc7-generic #202005242331 SMP Sun May 24 23:33:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux # cpufreq-info -o ... CPU 47 120 kHz ( 41 %) -290 kHz (100 %) - performance # fio /usr/share/doc/fio/examples/fio-seq-write.fio ... Run status group 0 (all jobs): WRITE: bw=63.1MiB/s (66.2MB/s), 63.1MiB/s-63.1MiB/s (66.2MB/s-66.2MB/s), io=60.0GiB (64.4GB), run=973234-973234msec ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1880943 Title: [focal] disk I/O performance regression Status in linux package in Ubuntu: New Bug description: Freshly deployed equal machines with flat disk layout as configured by MAAS, performance governor changed from ondemand to performance. Bionic (4.15.0-101-generic) fio ext4 on spinning rust: Run status group 0 (all jobs): WRITE: bw=1441MiB/s (1511MB/s), 1441MiB/s-1441MiB/s (1511MB/s-1511MB/s), io=1267GiB (1360GB), run=91-91msec Disk stats (read/write): sda: ios=2/332092, merge=0/567, ticks=196/123698912, in_queue=123760992, util=95.91% Bionic (4.15.0-101-generic) fio ext4 on nvme: Run status group 0 (all jobs): WRITE: bw=2040MiB/s (2139MB/s), 2040MiB/s-2040MiB/s (2139MB/s-2139MB/s), io=1793GiB (1925GB), run=91-91msec Disk stats (read/write): nvme0n1: ios=0/2617321, merge=0/465, ticks=0/233900784, in_queue=232549460, util=78.97% Focal (5.4.0-31-generic) fio ext4 on spinning rust: Run status group 0 (all jobs): WRITE: bw=108MiB/s (113MB/s), 108MiB/s-108MiB/s (113MB/s-113MB/s), io=100GiB (107GB), run=947255-947255msec Disk stats (read/write): sda: ios=65/430942, merge=0/980, ticks=1655/5837146, in_queue=4898628, util=48.75% Focal (5.4.0-31-generic) fio ext4 on nvme: status group 0 (all jobs): WRITE: bw=361MiB/s (378MB/s), 361MiB/s-361MiB/s (378MB/s-378MB/s), io=320GiB (344GB), run=907842-907842msec Disk stats (read/write): nvme0n1: ios=0/2847497, merge=0/382, ticks=0/236641266, in_queue=230690420, util=78.95% Freshly deployed equal machines with bcache as configured by MAAS, performance governor changed from ondemand to performance. Bionic (4.15.0-101-generic): Run status group 0 (all jobs): WRITE: bw=2080MiB/s (2181MB/s), 2080MiB/s-2080MiB/s (2181MB/s-2181MB/s), io=1828GiB (1963GB), run=900052-900052msec Disk stats (read/write): bcache3: ios=0/53036, merge=0/0, ticks=0/15519188, in_queue=15522076, util=91.81%, aggrios=0/212383, aggrmerge=0/402, aggrticks=0/59247094, aggrin_queue=59256646, aggrutil=91.82% nvme0n1: ios=0/7169, merge=0/397, ticks=0/0, in_queue=0, util=0.00% sda: ios=0/417598, merge=0/407, ticks=0/118494188, in_queue=118513292, util=91.82% Bionic (5.3.0-53-generic): Run status group 0 (all jobs): WRITE: bw=2725MiB/s (2858MB/s), 2725MiB/s-2725MiB/s (2858MB/s-2858MB/s), io=2395GiB (2572GB), run=91-91msec Disk stats (read/write): bcache3: ios=96/3955, merge=0/0, ticks=4/895876, in_queue=895880, util=2.63%, aggrios=48/222087, aggrmerge=0/391, aggrticks=3/2730760, aggrin_queue=2272248, aggrutil=90.56% nvme0n1: ios=96/2755, merge=0/373, ticks=6/78, in_queue=8, util=1.12% sda: ios=0/441420, merge=0/409, ticks=0/5461443, in_queue=4544488, util=90.56% Focal (5.4.0-31-generic): Run status group 0 (all jobs): WRITE: bw=117MiB/s (123MB/s), 117MiB/s-117MiB/s (123MB/s-123MB/s), io=110GiB (118GB), run=959924-959924msec Disk stats (read/write): bcache3: ios=0/4061, merge=0/0, ticks=0/1571168, in_queue=1571168, util=1.40%, aggrios=0/226807, aggrmerge=0/183, aggrticks=0/2816798, aggrin_queue=2331594, aggrutil=52.79% nvme0n1: ios=0/1474, merge=0/46, ticks=0/50, in_queue=0, util=0.53% sda: ios=0/452140, merge=0/321, ticks=0/5633547, in_queue=4663188, util=52.79% ; fio-seq-write.job for fiotest [global] name=fio-seq-write filename=fio-seq-write rw=write bs=256K direct=0 numjobs=1 time_based=1 runtime=900 [file1] size=10G ioengine=libaio iodepth=16 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 27 11:52 seq crw-rw 1 root audio 116, 33 May 27 11:5
[Kernel-packages] [Bug 1879939] Re: Audio stopped working after 5.4.0-31 kernel update
Just updated to 5.4.0-33.37 and it did not fix it -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879939 Title: Audio stopped working after 5.4.0-31 kernel update Status in linux package in Ubuntu: Confirmed Bug description: After rebooting following a system update where kernel 5.4.0-31 got installed, the main audio output stopped working. HDMI audio and USB headphones still work. Rebooting using the previous kernel (5.4.0-29) restores audio. Description:Ubuntu 20.04 LTS Release:20.04 log of the update that broke audio: Install: linux-image-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-headers-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-modules-extra-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-modules-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-headers-5.4.0-31:amd64 (5.4.0-31.35) Upgrade: bind9-dnsutils:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1), linux-headers-generic:amd64 (5.4.0.29.34, 5.4.0.31.36), linux-libc-dev:amd64 (5.4.0-29.33, 5.4.0-31.35), linux-image-generic:amd64 (5.4.0.29.34, 5.4.0.31.36), bind9-host:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1), dnsutils:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1), linux-generic:amd64 (5.4.0.29.34, 5.4.0.31.36), bind9-libs:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zeyelth1921 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu May 21 13:05:44 2020 HibernationDevice: RESUME=UUID=8ede6c97-084e-4c19-b235-2ba8b2c5565c InstallationDate: Installed on 2017-10-29 (934 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-08 (12 days ago) dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1003 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1003:bd04/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880943] 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/1880943 Title: [focal] disk I/O performance regression Status in linux package in Ubuntu: Confirmed Bug description: Freshly deployed equal machines with flat disk layout as configured by MAAS, performance governor changed from ondemand to performance. Bionic (4.15.0-101-generic) fio ext4 on spinning rust: Run status group 0 (all jobs): WRITE: bw=1441MiB/s (1511MB/s), 1441MiB/s-1441MiB/s (1511MB/s-1511MB/s), io=1267GiB (1360GB), run=91-91msec Disk stats (read/write): sda: ios=2/332092, merge=0/567, ticks=196/123698912, in_queue=123760992, util=95.91% Bionic (4.15.0-101-generic) fio ext4 on nvme: Run status group 0 (all jobs): WRITE: bw=2040MiB/s (2139MB/s), 2040MiB/s-2040MiB/s (2139MB/s-2139MB/s), io=1793GiB (1925GB), run=91-91msec Disk stats (read/write): nvme0n1: ios=0/2617321, merge=0/465, ticks=0/233900784, in_queue=232549460, util=78.97% Focal (5.4.0-31-generic) fio ext4 on spinning rust: Run status group 0 (all jobs): WRITE: bw=108MiB/s (113MB/s), 108MiB/s-108MiB/s (113MB/s-113MB/s), io=100GiB (107GB), run=947255-947255msec Disk stats (read/write): sda: ios=65/430942, merge=0/980, ticks=1655/5837146, in_queue=4898628, util=48.75% Focal (5.4.0-31-generic) fio ext4 on nvme: status group 0 (all jobs): WRITE: bw=361MiB/s (378MB/s), 361MiB/s-361MiB/s (378MB/s-378MB/s), io=320GiB (344GB), run=907842-907842msec Disk stats (read/write): nvme0n1: ios=0/2847497, merge=0/382, ticks=0/236641266, in_queue=230690420, util=78.95% Freshly deployed equal machines with bcache as configured by MAAS, performance governor changed from ondemand to performance. Bionic (4.15.0-101-generic): Run status group 0 (all jobs): WRITE: bw=2080MiB/s (2181MB/s), 2080MiB/s-2080MiB/s (2181MB/s-2181MB/s), io=1828GiB (1963GB), run=900052-900052msec Disk stats (read/write): bcache3: ios=0/53036, merge=0/0, ticks=0/15519188, in_queue=15522076, util=91.81%, aggrios=0/212383, aggrmerge=0/402, aggrticks=0/59247094, aggrin_queue=59256646, aggrutil=91.82% nvme0n1: ios=0/7169, merge=0/397, ticks=0/0, in_queue=0, util=0.00% sda: ios=0/417598, merge=0/407, ticks=0/118494188, in_queue=118513292, util=91.82% Bionic (5.3.0-53-generic): Run status group 0 (all jobs): WRITE: bw=2725MiB/s (2858MB/s), 2725MiB/s-2725MiB/s (2858MB/s-2858MB/s), io=2395GiB (2572GB), run=91-91msec Disk stats (read/write): bcache3: ios=96/3955, merge=0/0, ticks=4/895876, in_queue=895880, util=2.63%, aggrios=48/222087, aggrmerge=0/391, aggrticks=3/2730760, aggrin_queue=2272248, aggrutil=90.56% nvme0n1: ios=96/2755, merge=0/373, ticks=6/78, in_queue=8, util=1.12% sda: ios=0/441420, merge=0/409, ticks=0/5461443, in_queue=4544488, util=90.56% Focal (5.4.0-31-generic): Run status group 0 (all jobs): WRITE: bw=117MiB/s (123MB/s), 117MiB/s-117MiB/s (123MB/s-123MB/s), io=110GiB (118GB), run=959924-959924msec Disk stats (read/write): bcache3: ios=0/4061, merge=0/0, ticks=0/1571168, in_queue=1571168, util=1.40%, aggrios=0/226807, aggrmerge=0/183, aggrticks=0/2816798, aggrin_queue=2331594, aggrutil=52.79% nvme0n1: ios=0/1474, merge=0/46, ticks=0/50, in_queue=0, util=0.53% sda: ios=0/452140, merge=0/321, ticks=0/5633547, in_queue=4663188, util=52.79% ; fio-seq-write.job for fiotest [global] name=fio-seq-write filename=fio-seq-write rw=write bs=256K direct=0 numjobs=1 time_based=1 runtime=900 [file1] size=10G ioengine=libaio iodepth=16 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 27 11:52 seq crw-rw 1 root audio 116, 33 May 27 11:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed May 27 12:44:10 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Dri
[Kernel-packages] [Bug 1880666] Re: Power management: does not suspend
I made a couple of tests by Xubuntu Core 20.04 live USB (downloaded from https://unit193.net/xubuntu/core/). First time was by default settings i.e. 'lock screen when system is going to sleep' checked - I think that is not a good default setting for live - and the other time when it was not checked. Both times it did not suspend. The former did blank screen immediately, the other one after delay of several seconds. No keyboard activity did have an effect so I had to use power button. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880666 Title: Power management: does not suspend Status in linux package in Ubuntu: Incomplete Bug description: I am using Xubuntu 20.04. xfce4-session-logout --suspend exits with 0, but does not suspend. Same thing, if I choose suspend from menu (but it may lock screen depending on settings). Reproduceable: sometimes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1125 F pulseaudio /dev/snd/controlC1: jarnos 1125 F pulseaudio /dev/snd/controlC0: jarnos 1125 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue May 26 11:33:29 2020 InstallationDate: Installed on 2020-05-03 (22 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880666/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865988] Re: Performing function level reset of AMD onboard USB and audio devices causes system lockup
Thanks @vicamo again for your help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865988 Title: Performing function level reset of AMD onboard USB and audio devices causes system lockup Status in linux package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 [Impact] Devices affected: * [1022:149c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller * [1022:1487] Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller Despite advertising FLReset device capabilities, performing a function level reset of either of these devices causes the system to lock up. This is of particular issue where these devices appear in their own IOMMU groups and are well suited to VFIO passthrough. Issue was introduced in AMD's "AGESA Combo-AM4 1.0.0.4 Patch B" microcode update, and affects dozens of motherboard models across various vendors. Additional discussion of this issue: https://www.reddit.com/r/VFIO/comments/eba5mh/workaround_patch_for_passing_through_usb_and/ [Fix] Add a quirk to disable FLR on these devices. Sample patch attached. [Test Case] Peform the test on an impacted system: * B350, B450, X370, X470, X570 motherboards (practically anything with an AM4 socket); * Ryzen 3000-series CPU (2000-series possibly also affected); * BIOS/UEFI firmware that includes "AGESA Combo-AM4 1.0.0.4 Patch B" (check vendor release notes) In the above case where ':10:00.3' is the USB controller '1022:149c', issue a reset command $ echo 1 | sudo tee /sys/bus/pci/devices/\:10\:00.3/reset Impacted systems will not return successfully and become unstable, requiring a reboot. `/var/logs/syslog` will show something resembling the following Mar 4 14:51:26 bunty kernel: [ 1745.043914] xhci_hcd :10:00.3: not ready 1023ms after FLR; waiting Mar 4 14:51:28 bunty kernel: [ 1747.091910] xhci_hcd :10:00.3: not ready 2047ms after FLR; waiting Mar 4 14:51:32 bunty kernel: [ 1750.163972] xhci_hcd :10:00.3: not ready 4095ms after FLR; waiting Mar 4 14:51:37 bunty kernel: [ 1755.283933] xhci_hcd :10:00.3: not ready 8191ms after FLR; waiting Mar 4 14:51:46 bunty kernel: [ 1764.499943] xhci_hcd :10:00.3: not ready 16383ms after FLR; waiting Mar 4 14:52:04 bunty kernel: [ 1782.164126] xhci_hcd :10:00.3: not ready 32767ms after FLR; waiting Mar 4 14:52:39 bunty kernel: [ 1816.979432] xhci_hcd :10:00.3: not ready 65535ms after FLR; giving up Mar 4 14:52:39 bunty kernel: [ 1817.978790] clocksource: timekeeping watchdog on CPU14: Marking clocksource 'tsc' as unstable because the skew is too large: Mar 4 14:52:39 bunty kernel: [ 1817.978806] clocksource: 'hpet' wd_now: f63fcfe wd_last: d468894 mask: Mar 4 14:52:39 bunty kernel: [ 1817.978809] clocksource: 'tsc' cs_now: 60e67e17758 cs_last: 60d2a81ce24 mask: Mar 4 14:52:39 bunty kernel: [ 1817.978818] tsc: Marking TSC unstable due to clocksource watchdog Mar 4 14:52:40 bunty kernel: [ 1817.978892] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Mar 4 14:52:40 bunty kernel: [ 1817.978894] sched_clock: Marking unstable (1817664630139, 314261908)<-(1817981099530, -2209419) [Regression Risk] Unknown --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 19.10 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40+amdnoflr-generic root=UUID=f2f3748c-f017-47ae-aa38-943e5f5189e0 ro amd_iommu=on ProcVersionSignature: Ubuntu 5.3.0-40.32+amdnoflr-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40+amdnoflr-generic N/A linux-backports-modules-5.3.0-40+amdnoflr-generic N/A linux-firmware 1.183.3 Tags: eoan Uname: Linux 5.3.0-40+amdnoflr-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 11/14/2019
[Kernel-packages] [Bug 1879939] Re: Audio stopped working after 5.4.0-31 kernel update
The fix was in the -32 kernel, but I don't know why this fix is reverted
from -33 kernel, and I just checked the -34 kernel, the fix is in the
-34 kernel. The fix is:
commit 9b419c6ae76ad59f6fc4529fc03ddbc12a22cdec
Author: Takashi Iwai
Date: Fri Apr 24 08:12:22 2020 +0200
ALSA: hda: Match both PCI ID and SSID for driver blacklist
BugLink: https://bugs.launchpad.net/bugs/1878040
commit 977dfef40c8996b69afe23a9094d184049efb7bb upstream.
The commit 3c6fd1f07ed0 ("ALSA: hda: Add driver blacklist") added a
new blacklist for the devices that are known to have empty codecs, and
one of the entries was ASUS ROG Zenith II (PCI SSID 1043:874f).
However, it turned out that the very same PCI SSID is used for the
previous model that does have the valid HD-audio codecs and the change
broke the sound on it.
Since the empty codec problem appear on the certain AMD platform (PCI
ID 1022:1487), this patch changes the blacklist matching to both PCI
ID and SSID using pci_match_id(). Also, the entry that was removed by
the previous fix for ASUS ROG Zenigh II is re-added.
Link: https://lore.kernel.org/r/20200424061222.19792-1-ti...@suse.de
Signed-off-by: Takashi Iwai
Signed-off-by: Greg Kroah-Hartman
Signed-off-by: Kamal Mostafa
Signed-off-by: Stefan Bader
diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c
index bdb1a9dbe7f4..8bcf0324d7f8 100644
--- a/sound/pci/hda/hda_intel.c
+++ b/sound/pci/hda/hda_intel.c
@@ -2025,9 +2025,10 @@ static void pcm_mmap_prepare(struct snd_pcm_substream
*substream,
* some HD-audio PCI entries are exposed without any codecs, and such devices
* should be ignored from the beginning.
*/
-static const struct snd_pci_quirk driver_blacklist[] = {
- SND_PCI_QUIRK(0x1462, 0xcb59, "MSI TRX40 Creator", 0),
- SND_PCI_QUIRK(0x1462, 0xcb60, "MSI TRX40", 0),
+static const struct pci_device_id driver_blacklist[] = {
+ { PCI_DEVICE_SUB(0x1022, 0x1487, 0x1043, 0x874f) }, /* ASUS ROG Zenith
II / Strix */
+ { PCI_DEVICE_SUB(0x1022, 0x1487, 0x1462, 0xcb59) }, /* MSI TRX40
Creator */
+ { PCI_DEVICE_SUB(0x1022, 0x1487, 0x1462, 0xcb60) }, /* MSI TRX40 */
{}
};
@@ -2047,7 +2048,7 @@ static int azx_probe(struct pci_dev *pci,
bool schedule_probe;
int err;
- if (snd_pci_quirk_lookup(pci, driver_blacklist)) {
+ if (pci_match_id(driver_blacklist, pci)) {
dev_info(&pci->dev, "Skipping the blacklisted device\n");
return -ENODEV;
}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879939
Title:
Audio stopped working after 5.4.0-31 kernel update
Status in linux package in Ubuntu:
Confirmed
Bug description:
After rebooting following a system update where kernel 5.4.0-31 got
installed, the main audio output stopped working. HDMI audio and USB
headphones still work. Rebooting using the previous kernel (5.4.0-29)
restores audio.
Description:Ubuntu 20.04 LTS
Release:20.04
log of the update that broke audio:
Install: linux-image-5.4.0-31-generic:amd64 (5.4.0-31.35),
linux-headers-5.4.0-31-generic:amd64 (5.4.0-31.35),
linux-modules-extra-5.4.0-31-generic:amd64 (5.4.0-31.35),
linux-modules-5.4.0-31-generic:amd64 (5.4.0-31.35),
linux-headers-5.4.0-31:amd64 (5.4.0-31.35)
Upgrade: bind9-dnsutils:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1),
linux-headers-generic:amd64 (5.4.0.29.34, 5.4.0.31.36), linux-libc-dev:amd64
(5.4.0-29.33, 5.4.0-31.35), linux-image-generic:amd64 (5.4.0.29.34,
5.4.0.31.36), bind9-host:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1),
dnsutils:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1), linux-generic:amd64
(5.4.0.29.34, 5.4.0.31.36), bind9-libs:amd64 (1:9.16.1-0ubuntu2,
1:9.16.1-0ubuntu2.1)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-modules-extra-5.4.0-31-generic 5.4.0-31.35
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: zeyelth1921 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Thu May 21 13:05:44 2020
HibernationDevice: RESUME=UUID=8ede6c97-084e-4c19-b235-2ba8b2c5565c
InstallationDate: Installed on 2017-10-29 (934 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: System manufacturer System Product Name
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.4.0-31-generic N/A
linux-backports-modules-5.4.0-31-generic N/A
linux-firmware1.187
RfKill:
[Kernel-packages] [Bug 1879688] Re: shiftfs: fix btrfs snapshot deletion
** Also affects: linux (Ubuntu Groovy) Importance: Undecided Assignee: Christian Brauner (cbrauner) Status: Confirmed ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) 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/1879688 Title: shiftfs: fix btrfs snapshot deletion Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: New Status in linux source package in Focal: New Status in linux source package in Groovy: Confirmed Bug description: SRU Justification Impact: Stéphane discovered a problem during NorthSec which makes heavy use of shiftfs. In containers with a btrfs root filesystem that make use of shiftfs userns root is not able to delete subvolumes that have been created by another users which it would be able to do otherwise. This makes it impossible for LXD to delete nested containers. To reproduce this as root in the container: btrfs subvolume create my-subvol chown 1000:1000 my-subvol btrfs subvolume delete my-subvol The deletion will fail when it should have succeeded. Fix: For improved security we drop all capabilities before we forward btrfs ioctls in shiftfs. To fix the above problem we can retain the CAP_DAC_OVERRIDE capability only if we are userns root. Regression Potential: Limited to shiftfs. Even though we drop all capabilities in all capability sets we really mostly care about dropping CAP_SYS_ADMIN and we mostly do this for ioctl that e.g. allow you to traverse the btrfs filesystem and with CAP_SYS_ADMIN retained in the underlay would allow you to list subvolumes you shouldn't be able to list. This fix only retains CAP_DAC_OVERRIDE and only for the deletion of subvolumes and only by userns root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880666] Re: Power management: does not suspend
Please use Ubuntu proper to test: http://cdimages.ubuntu.com/daily- live/current/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880666 Title: Power management: does not suspend Status in linux package in Ubuntu: Incomplete Bug description: I am using Xubuntu 20.04. xfce4-session-logout --suspend exits with 0, but does not suspend. Same thing, if I choose suspend from menu (but it may lock screen depending on settings). Reproduceable: sometimes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1125 F pulseaudio /dev/snd/controlC1: jarnos 1125 F pulseaudio /dev/snd/controlC0: jarnos 1125 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue May 26 11:33:29 2020 InstallationDate: Installed on 2020-05-03 (22 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. OptiPlex 745 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=f2d9359d-8b8e-46c4-9f37-452c3dd06417 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880666/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881072] Re: "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed
This issue can be found in ubuntu_kvm_unit_tests on the same node as well. -- 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/1881072 Title: "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Issue found on 4.15.0-1061-kvm, with KVM instance zeppo, moe. The ubuntu_kvm_smoke_test will fail with: uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:ee:15:c8. Traces can be found in syslog. systemd[1]: Started Daemon for generating UUIDs. kernel: kauditd_printk_skb: 9 callbacks suppressed kernel: audit: type=1400 audit(1590647581.375:20): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1291 comm="apparmor_parser" kernel: audit: type=1400 audit(1590647581.691:21): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1294 comm="apparmor_parser" kernel: audit: type=1400 audit(1590647581.927:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1297 comm="apparmor_parser" kernel: audit: type=1400 audit(1590647582.155:23): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1300 comm="apparmor_parser" systemd[1]: Started Virtual machine log manager. libvirtd[693]: 2020-05-28 06:33:02.188+: 731: info : libvirt version: 4.0.0, package: 1ubuntu8.17 (Marc Deslauriers Wed, 06 May 2020 14:18:23 -0400) systemd-networkd[613]: vnet0: Link UP systemd-networkd[613]: vnet0: Gained carrier networkd-dispatcher[662]: WARNING:Unknown index 7 seen, reloading interface list kernel: virbr0: port 2(vnet0) entered blocking state kernel: virbr0: port 2(vnet0) entered disabled state kernel: device vnet0 entered promiscuous mode kernel: virbr0: port 2(vnet0) entered blocking state kernel: virbr0: port 2(vnet0) entered listening state systemd-timesyncd[542]: Network configuration changed, trying to establish connection. systemd-timesyncd[542]: Synchronized to time server 10.246.72.3:123 (10.246.72.3). libvirtd[693]: 2020-05-28 06:33:02.188+: 731: info : hostname: zeppo libvirtd[693]: 2020-05-28 06:33:02.188+: 731: warning : qemuInterfaceOpenVhostNet:687 : Unable to open vhost-net. Opened so far 0, requested 1 systemd-udevd[1306]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. dnsmasq[911]: reading /etc/resolv.conf dnsmasq[911]: using nameserver 127.0.0.53#53 systemd-timesyncd[542]: Network configuration changed, trying to establish connection. systemd-timesyncd[542]: Synchronized to time server 10.246.72.3:123 (10.246.72.3). dnsmasq[911]: reading /etc/resolv.conf dnsmasq[911]: using nameserver 127.0.0.53#53 kernel: audit: type=1400 audit(1590647582.424:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1316 comm="apparmor_parser" kernel: BUG: unable to handle kernel paging request at 56b8 kernel: IP: 0xc01efb02 kernel: PGD 0 P4D 0 kernel: Oops: [#1] SMP PTI kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_filter ip6_tables iptable_filter loop fuse kvm_intel ip_tables x_tables btrfs xor zstd_decompress zstd_compress xxhash lzo_compress raid6_pq pata_acpi kernel: CPU: 1 PID: 1323 Comm: CPU 0/KVM Not tainted 4.15.0-1061-kvm #62-Ubuntu kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 kernel: RIP: 0010:0xc01efb02 kernel: RSP: 0018:ade780fcbcb0 EFLAGS: 00010002 kernel: RAX: 0001 RBX: RCX: kernel: RDX: 6c14 RSI: RDI: kernel: RBP: ade780fcbcb0 R08: R09: kernel: R10: R11: R12: kernel: R13: R14: R15: kernel: FS: 7f6ab9c34700() GS:938c7fd0() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 56b8 CR3: 000138aac000 CR4: 26a0 kernel: Call Trace: kernel: 0xc01f0205 kernel: 0xba031ee1 kernel: 0xba039cac kernel: ? 0xba039cac kernel: 0xba01cad1
[Kernel-packages] [Bug 1881072] Re: "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed
This ubuntu_kvm_smoke_test has passed on bare-metal AMD64 with Bionic kernel 4.15.0-102.103 -- 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/1881072 Title: "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Issue found on 4.15.0-1061-kvm, with KVM instance zeppo, moe. The ubuntu_kvm_smoke_test will fail with: uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:ee:15:c8. Traces can be found in syslog. systemd[1]: Started Daemon for generating UUIDs. kernel: kauditd_printk_skb: 9 callbacks suppressed kernel: audit: type=1400 audit(1590647581.375:20): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1291 comm="apparmor_parser" kernel: audit: type=1400 audit(1590647581.691:21): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1294 comm="apparmor_parser" kernel: audit: type=1400 audit(1590647581.927:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1297 comm="apparmor_parser" kernel: audit: type=1400 audit(1590647582.155:23): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1300 comm="apparmor_parser" systemd[1]: Started Virtual machine log manager. libvirtd[693]: 2020-05-28 06:33:02.188+: 731: info : libvirt version: 4.0.0, package: 1ubuntu8.17 (Marc Deslauriers Wed, 06 May 2020 14:18:23 -0400) systemd-networkd[613]: vnet0: Link UP systemd-networkd[613]: vnet0: Gained carrier networkd-dispatcher[662]: WARNING:Unknown index 7 seen, reloading interface list kernel: virbr0: port 2(vnet0) entered blocking state kernel: virbr0: port 2(vnet0) entered disabled state kernel: device vnet0 entered promiscuous mode kernel: virbr0: port 2(vnet0) entered blocking state kernel: virbr0: port 2(vnet0) entered listening state systemd-timesyncd[542]: Network configuration changed, trying to establish connection. systemd-timesyncd[542]: Synchronized to time server 10.246.72.3:123 (10.246.72.3). libvirtd[693]: 2020-05-28 06:33:02.188+: 731: info : hostname: zeppo libvirtd[693]: 2020-05-28 06:33:02.188+: 731: warning : qemuInterfaceOpenVhostNet:687 : Unable to open vhost-net. Opened so far 0, requested 1 systemd-udevd[1306]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. dnsmasq[911]: reading /etc/resolv.conf dnsmasq[911]: using nameserver 127.0.0.53#53 systemd-timesyncd[542]: Network configuration changed, trying to establish connection. systemd-timesyncd[542]: Synchronized to time server 10.246.72.3:123 (10.246.72.3). dnsmasq[911]: reading /etc/resolv.conf dnsmasq[911]: using nameserver 127.0.0.53#53 kernel: audit: type=1400 audit(1590647582.424:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1316 comm="apparmor_parser" kernel: BUG: unable to handle kernel paging request at 56b8 kernel: IP: 0xc01efb02 kernel: PGD 0 P4D 0 kernel: Oops: [#1] SMP PTI kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_filter ip6_tables iptable_filter loop fuse kvm_intel ip_tables x_tables btrfs xor zstd_decompress zstd_compress xxhash lzo_compress raid6_pq pata_acpi kernel: CPU: 1 PID: 1323 Comm: CPU 0/KVM Not tainted 4.15.0-1061-kvm #62-Ubuntu kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 kernel: RIP: 0010:0xc01efb02 kernel: RSP: 0018:ade780fcbcb0 EFLAGS: 00010002 kernel: RAX: 0001 RBX: RCX: kernel: RDX: 6c14 RSI: RDI: kernel: RBP: ade780fcbcb0 R08: R09: kernel: R10: R11: R12: kernel: R13: R14: R15: kernel: FS: 7f6ab9c34700() GS:938c7fd0() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 56b8 CR3: 000138aac000 CR4: 26a0 kernel: Call Trace: kernel: 0xc01f0205 kernel: 0xba031ee1 kernel: 0xba039cac kernel: ? 0xba039cac kernel: 0x
[Kernel-packages] [Bug 1872059] Update Released
The verification of the Stable Release Update for apport 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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Invalid Status in apport source package in Focal: Fix Released Status in linux-firmware source package in Focal: Invalid Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. Test Case - 1) On an Ubuntu 20.04 LTS system run 'apport-cli linux-firmware'. 2) Choose 'View report' 3) Observe that 'ProcFB' is not collected With the version of apport from -proposed 'ProcFB' will be in the report. Regression Potential None, as we are just adding a symlink from linux-firmware to the linux source package hook. Original Description ProblemType: BugDistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: allSourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M 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 audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
This bug was fixed in the package apport - 2.20.11-0ubuntu27.2 --- apport (2.20.11-0ubuntu27.2) focal; urgency=medium * gtk/apport-gtk: upgrade regular expression used to match URLs in free text (LP: #1871185) apport (2.20.11-0ubuntu27.1) focal; urgency=medium * debian/apport.install: Add in a source package hook for linux-meta-raspi which provides linux-raspi and linux-raspi2. (LP: #1876952) * data/general-hooks/ubuntu.py: collect ImageMediaBuild information which exists on preinstalled RPi images. (LP: #1876945) * Add in a source package hook symlink for linux-firmware. (LP: #1872059) * debian/tests/control: Depend on python3-twisted, not python-twisted-core -- Brian Murray Tue, 12 May 2020 15:34:22 -0700 ** Changed in: apport (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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Invalid Status in apport source package in Focal: Fix Released Status in linux-firmware source package in Focal: Invalid Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. Test Case - 1) On an Ubuntu 20.04 LTS system run 'apport-cli linux-firmware'. 2) Choose 'View report' 3) Observe that 'ProcFB' is not collected With the version of apport from -proposed 'ProcFB' will be in the report. Regression Potential None, as we are just adding a symlink from linux-firmware to the linux source package hook. Original Description ProblemType: BugDistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: allSourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M 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 audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
Hi, I still have the same issue with UVD not responding: uname -a Linux dim-VPCSA2S9R 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal inxi -G Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel Device-2: Advanced Micro Devices [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] driver: radeon v: kernel Display: x11 server: X.Org 1.20.8 driver: radeon resolution: 1600x900~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) v: 3.3 Mesa 20.0.4 dpkg -l | grep linux-firmware ii linux-firmware 1.187 all Firmware for Linux kernel drivers -- 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/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Released Status in linux-firmware source package in Eoan: Fix Released Bug description: === SRU Justification === [Impact] Firmware update of radeon/oland_rlc.bin breaks some radeon cards. [Fix] Revert the new firmware. [Regression Potential] Low. The old firmware has been used for a long time. === Original Bug Report === when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Feb 28 11:50:50 20
[Kernel-packages] [Bug 1880943] Re: [focal] disk I/O performance regression
Would it be possible for you to do a kernel bisection? First, find the last -rc kernel works and the first -rc kernel doesn’t work from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the working version you found) $ git bisect bad $(the non-working version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If it still have the same issue, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the offending commit. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880943 Title: [focal] disk I/O performance regression Status in linux package in Ubuntu: Confirmed Bug description: Freshly deployed equal machines with flat disk layout as configured by MAAS, performance governor changed from ondemand to performance. Bionic (4.15.0-101-generic) fio ext4 on spinning rust: Run status group 0 (all jobs): WRITE: bw=1441MiB/s (1511MB/s), 1441MiB/s-1441MiB/s (1511MB/s-1511MB/s), io=1267GiB (1360GB), run=91-91msec Disk stats (read/write): sda: ios=2/332092, merge=0/567, ticks=196/123698912, in_queue=123760992, util=95.91% Bionic (4.15.0-101-generic) fio ext4 on nvme: Run status group 0 (all jobs): WRITE: bw=2040MiB/s (2139MB/s), 2040MiB/s-2040MiB/s (2139MB/s-2139MB/s), io=1793GiB (1925GB), run=91-91msec Disk stats (read/write): nvme0n1: ios=0/2617321, merge=0/465, ticks=0/233900784, in_queue=232549460, util=78.97% Focal (5.4.0-31-generic) fio ext4 on spinning rust: Run status group 0 (all jobs): WRITE: bw=108MiB/s (113MB/s), 108MiB/s-108MiB/s (113MB/s-113MB/s), io=100GiB (107GB), run=947255-947255msec Disk stats (read/write): sda: ios=65/430942, merge=0/980, ticks=1655/5837146, in_queue=4898628, util=48.75% Focal (5.4.0-31-generic) fio ext4 on nvme: status group 0 (all jobs): WRITE: bw=361MiB/s (378MB/s), 361MiB/s-361MiB/s (378MB/s-378MB/s), io=320GiB (344GB), run=907842-907842msec Disk stats (read/write): nvme0n1: ios=0/2847497, merge=0/382, ticks=0/236641266, in_queue=230690420, util=78.95% Freshly deployed equal machines with bcache as configured by MAAS, performance governor changed from ondemand to performance. Bionic (4.15.0-101-generic): Run status group 0 (all jobs): WRITE: bw=2080MiB/s (2181MB/s), 2080MiB/s-2080MiB/s (2181MB/s-2181MB/s), io=1828GiB (1963GB), run=900052-900052msec Disk stats (read/write): bcache3: ios=0/53036, merge=0/0, ticks=0/15519188, in_queue=15522076, util=91.81%, aggrios=0/212383, aggrmerge=0/402, aggrticks=0/59247094, aggrin_queue=59256646, aggrutil=91.82% nvme0n1: ios=0/7169, merge=0/397, ticks=0/0, in_queue=0, util=0.00% sda: ios=0/417598, merge=0/407, ticks=0/118494188, in_queue=118513292, util=91.82% Bionic (5.3.0-53-generic): Run status group 0 (all jobs): WRITE: bw=2725MiB/s (2858MB/s), 2725MiB/s-2725MiB/s (2858MB/s-2858MB/s), io=2395GiB (2572GB), run=91-91msec Disk stats (read/write): bcache3: ios=96/3955, merge=0/0, ticks=4/895876, in_queue=895880, util=2.63%, aggrios=48/222087, aggrmerge=0/391, aggrticks=3/2730760, aggrin_queue=2272248, aggrutil=90.56% nvme0n1: ios=96/2755, merge=0/373, ticks=6/78, in_queue=8, util=1.12% sda: ios=0/441420, merge=0/409, ticks=0/5461443, in_queue=4544488, util=90.56% Focal (5.4.0-31-generic): Run status group 0 (all jobs): WRITE: bw=117MiB/s (123MB/s), 117MiB/s-117MiB/s (123MB/s-123MB/s), io=110GiB (118GB), run=959924-959924msec Disk stats (read/write): bcache3: ios=0/4061, merge=0/0, ticks=0/1571168, in_queue=1571168, util=1.40%, aggrios=0/226807, aggrmerge=0/183, aggrticks=0/2816798, aggrin_queue=2331594, aggrutil=52.79% nvme0n1: ios=0/1474, merge=0/46, ticks=0/50, in_queue=0, util=0.53% sda: ios=0/452140, merge=0/321, ticks=0/5633547, in_queue=4663188, util=52.79% ; fio-seq-write.job for fiotest [global] name=fio-seq-write filename=fio-seq-write rw=write bs=256K direct=0 numjobs=1 time_based=1 runtime=900 [file1] size=10G ioengine=libaio iodepth=16 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 27 11:52 seq crw-rw 1 root audio 116, 33 May 27 11:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer
[Kernel-packages] [Bug 1878899] Re: Call trace from __video_do_ioctl
Same, happens on loading the v4l2loopback module: [ 1039.168432] v4l2loopback driver version 0.12.3 loaded [ 1039.172977] [ cut here ] [ 1039.172994] WARNING: CPU: 3 PID: 8520 at drivers/media/v4l2-core/v4l2-ioctl.c:1064 v4l_querycap+0x8b/0xa0 [videodev] [ 1039.172995] Modules linked in: v4l2loopback(OE) snd_seq_dummy iptable_mangle xt_CHECKSUM iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_tcpudp bridge stp llc iptable_filter bpfilter binfmt_misc nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi edac_mce_amd snd_hda_intel snd_intel_dspcfg kvm_amd snd_hda_codec ccp snd_hda_core snd_usb_audio kvm snd_usbmidi_lib snd_hwdep serio_raw snd_pcm fam15h_power k10temp snd_seq_midi snd_seq_midi_event snd_rawmidi gspca_zc3xx gspca_vc032x uvcvideo gspca_main snd_seq input_leds videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common joydev videodev snd_seq_device mc cdc_acm snd_timer snd soundcore mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt amdgpu amd_iommu_v2 gpu_sched uas usb_storage hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel radeon i2c_algo_bit ttm aesni_intel crypto_simd drm_kms_helper [ 1039.173027] cryptd syscopyarea glue_helper sysfillrect sysimgblt fb_sys_fops i2c_piix4 ahci drm libahci r8169 realtek video [last unloaded: v4l2loopback] [ 1039.173035] CPU: 3 PID: 8520 Comm: v4l_id Tainted: GW OE 5.4.0-29-generic #33-Ubuntu [ 1039.173036] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./G1.Sniper A88X-CF, BIOS F7 01/08/2014 [ 1039.173042] RIP: 0010:v4l_querycap+0x8b/0xa0 [videodev] [ 1039.173044] Code: 54 81 ca 00 00 00 80 48 b9 00 00 20 00 00 00 20 00 48 0b 4b 54 21 d6 39 f2 75 13 48 89 4b 54 5b 41 5c 41 5d 41 5e 41 5f 5d c3 <0f> 0b eb d0 0f 0b 48 89 4b 54 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f [ 1039.173045] RSP: 0018:bc64429c3c70 EFLAGS: 00010297 [ 1039.173047] RAX: RBX: bc64429c3d88 RCX: 0001 [ 1039.173048] RDX: 85008003 RSI: RDI: [ 1039.173048] RBP: bc64429c3c98 R08: R09: 000a [ 1039.173049] R10: R11: R12: 92f309255000 [ 1039.173050] R13: 92f317d7e200 R14: 92f234abe6a0 R15: c0fd8380 [ 1039.173052] FS: 7fc41b97e580() GS:92f31fb8() knlGS: [ 1039.173053] CS: 0010 DS: ES: CR0: 80050033 [ 1039.173053] CR2: 7fc41b830cc0 CR3: 0007a7e0 CR4: 000406e0 [ 1039.173054] Call Trace: [ 1039.173064] __video_do_ioctl+0x1a7/0x410 [videodev] [ 1039.173070] video_usercopy+0x2b5/0x670 [videodev] [ 1039.173076] ? v4l_s_fmt+0x670/0x670 [videodev] [ 1039.173082] video_ioctl2+0x15/0x20 [videodev] [ 1039.173087] v4l2_ioctl+0x4c/0x60 [videodev] [ 1039.173091] do_vfs_ioctl+0x407/0x670 [ 1039.173095] ? __secure_computing+0x42/0xe0 [ 1039.173096] ksys_ioctl+0x67/0x90 [ 1039.173098] __x64_sys_ioctl+0x1a/0x20 [ 1039.173100] do_syscall_64+0x57/0x190 [ 1039.173103] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 1039.173105] RIP: 0033:0x7fc41b83737b [ 1039.173107] 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 [ 1039.173108] RSP: 002b:7ffd63439488 EFLAGS: 0246 ORIG_RAX: 0010 [ 1039.173109] RAX: ffda RBX: 7ffd63439608 RCX: 7fc41b83737b [ 1039.173110] RDX: 7ffd63439490 RSI: 80685600 RDI: 0003 [ 1039.173110] RBP: 0003 R08: R09: [ 1039.173111] R10: R11: 0246 R12: 55a68fffa440 [ 1039.173112] R13: 7ffd63439600 R14: R15: [ 1039.173114] ---[ end trace d94124d807433b7d ]--- [ 1039.173126] [ cut here ] [ 1039.173132] WARNING: CPU: 3 PID: 8520 at drivers/media/v4l2-core/v4l2-ioctl.c:1069 v4l_querycap+0x8f/0xa0 [videodev] [ 1039.173132] Modules linked in: v4l2loopback(OE) snd_seq_dummy iptable_mangle xt_CHECKSUM iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_tcpudp bridge stp llc iptable_filter bpfilter binfmt_misc nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi edac_mce_amd snd_hda_intel snd_intel_dspcfg kvm_amd snd_hda_codec ccp snd_hda_core snd_usb_audio kvm snd_usbmidi_lib snd_hwdep serio_raw snd_pcm fam15h_power k10temp snd_seq_midi snd_seq_midi_event snd_rawmidi gspca_zc3xx gspca_vc032x uvcvideo gspca_main snd_seq input_leds videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common joydev videodev snd_seq_device mc cdc_acm snd_timer snd soundcore mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_table
[Kernel-packages] [Bug 1881015] Re: Fn Lock light does not come on to indicate when Fn Lock is enabled
Here is some more information that I collected. I tried toggling fn-lock while at different stages of booting. * In the grub menu, the light does not toggle. * If I choose to boot windows, then while windows is booting, the light does not toggle. (ie, during the "swirling dots" screen.) * Once windows gets to the login screen, the light does toggle. This implies the light only works once windows has loaded a driver or similar. * If I instead choose to boot Ubuntu, then the light does not toggle. Not during boot, at the login screen, or after logged in. * If I enter the BIOS setup, then the light does toggle there. If I exit and boot into Ubuntu then the light no longer toggles. I strongly suspect there is at least some OS involvement with the fn- lock LED working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881015 Title: Fn Lock light does not come on to indicate when Fn Lock is enabled Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo E595 running Ubuntu 20.04. The "Fn Lock" feature on the keyboard works in terms of how it modifies subsequent presses of the F1-F12 keys, but the little light on the Esc key doesn't show the current state. Example: 1. I press F5 a few times, and the screen brightness is adjusted. 2. I press Fn+Esc, and "Fn Lock" is now on, but the light hasn't changed. 3. I press F5 again, or several times, and it acts as a normal F5 (ie my browser might refresh the page). 4. I press Fn+Esc again, and "Fn Lock" is now off, but again the light hasn't changed. So, "Fn Lock" works in the sense that it modifies what keypresses do, but the little light on the Esc key doesn't come on. Under Windows the light does toggle, to show the current status. The behaviour is the same on Xorg and Wayland. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.31.36 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: paul 2138 F pulseaudio /dev/snd/controlC0: paul 2138 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 27 21:37:47 2020 InstallationDate: Installed on 2020-05-13 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NFCTO1WW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=f7c34228-ee6f-4043-931c-f4752ad503c8 ro quiet splash nomodeset vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET36W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET36W(1.16):bd03/30/2020:svnLENOVO:pn20NFCTO1WW:pvrThinkPadE595:rvnLENOVO:rn20NFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E595 dmi.product.name: 20NFCTO1WW dmi.product.sku: LENOVO_MT_20NF_BU_Think_FM_ThinkPad E595 dmi.product.version: ThinkPad E595 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784240] [NEW] Driver doesn't correctly probe Samsung U28D590D 28-inch 4k after recent update
You have been subscribed to a public bug: This monitor was correctly detected and worked properly at maximum resolution for the last 2 years, but X no longer correctly identifies the monitor and now only proposes a maximum display resolution of 1368x768 since a recent update. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Jul 29 11:10:25 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:67ef] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:9460] InstallationDate: Installed on 2016-05-20 (800 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/Whiteygu-lvm--root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8 dmi.board.name: GA-990FXA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Jul 29 09:18:04 2018 xserver.configfile: default xserver.errors: AMDGPU(0): Failed to open amdgpu hybrid version xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: amdgpu ** Affects: linux (Ubuntu) Importance: High Status: Incomplete ** Tags: amd64 apport-bug compiz-0.9 regression-update resolution ubuntu xenial -- Driver doesn't correctly probe Samsung U28D590D 28-inch 4k after recent update https://bugs.launchpad.net/bugs/1784240 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 1881072] Re: "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed
This ubuntu_kvm_smoke_test has failed on bare-metal i386 with Bionic kernel 4.15.0-102.103 kernel: [ 205.203786] BUG: unable to handle kernel paging request at 4ee4 kernel: [ 205.203865] IP: vmx_vcpu_run+0x24c/0x590 [kvm_intel] kernel: [ 205.203908] *pdpt = 32cee001 *pde = kernel: [ 205.203958] Oops: [#1] SMP PTI kernel: [ 205.203988] Modules linked in: vhost_net vhost tap xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter devlink intel_rapl x86_pkg_temp_thermal joydev input_leds intel_powerclamp coretemp intel_cstate dcdbas ipmi_ssif intel_rapl_perf ipmi_si mei_me ipmi_devintf acpi_power_meter kvm_intel mei mac_hid shpchp ipmi_msghandler acpi_pad kvm irqbypass lpc_ich sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq kernel: [ 205.204461] libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid mgag200 i2c_algo_bit ttm crc32_pclmul drm_kms_helper pcbc syscopyarea sysfillrect aesni_intel sysimgblt aes_i586 fb_sys_fops crypto_simd cryptd drm tg3 ahci libahci ptp pps_core wmi kernel: [ 205.204612] CPU: 3 PID: 2193 Comm: CPU 0/KVM Not tainted 4.15.0-102-generic #103-Ubuntu kernel: [ 205.204663] Hardware name: Dell Inc. PowerEdge R320/0DY523, BIOS 1.2.4 05/11/2012 kernel: [ 205.204715] EIP: vmx_vcpu_run+0x24c/0x590 [kvm_intel] kernel: [ 205.204748] EFLAGS: 00010002 CPU: 3 kernel: [ 205.204771] EAX: 0001 EBX: ECX: EDX: 6c14 kernel: [ 205.204810] ESI: EDI: EBP: f3313de8 ESP: f3313dd0 kernel: [ 205.204848] DS: 0068 ES: 0068 FS: 00d8 GS: 00e0 SS: 0068 kernel: [ 205.204883] CR0: 80050033 CR2: 4ee4 CR3: 27b34000 CR4: 000426f0 kernel: [ 205.204922] Call Trace: kernel: [ 205.204973] vcpu_enter_guest+0x2da/0x1200 [kvm] kernel: [ 205.205026] ? kvm_arch_vcpu_load+0x7d/0x250 [kvm] kernel: [ 205.205079] kvm_arch_vcpu_ioctl_run+0xc1/0x3c0 [kvm] kernel: [ 205.205131] ? kvm_arch_vcpu_ioctl_run+0xc1/0x3c0 [kvm] kernel: [ 205.205182] kvm_vcpu_ioctl+0x26c/0x5b0 [kvm] kernel: [ 205.205214] ? futex_wake+0x7d/0x150 kernel: [ 205.205256] ? kvm_set_memory_region+0x40/0x40 [kvm] kernel: [ 205.205290] do_vfs_ioctl+0x93/0x6b0 kernel: [ 205.205316] SyS_ioctl+0x58/0x70 kernel: [ 205.205340] do_fast_syscall_32+0x7f/0x200 kernel: [ 205.205370] entry_SYSENTER_32+0x6b/0xbe kernel: [ 205.205396] EIP: 0xb7f1fd09 kernel: [ 205.205414] EFLAGS: 00200292 CPU: 3 kernel: [ 205.205438] EAX: ffda EBX: 0015 ECX: ae80 EDX: kernel: [ 205.205478] ESI: 02ce7220 EDI: EBP: b7f12000 ESP: b32a6eb8 kernel: [ 205.205517] DS: 007b ES: 007b FS: GS: 0033 SS: 007b kernel: [ 205.207327] Code: 81 f4 01 00 00 31 c0 31 db 31 c9 31 d2 31 f6 31 ff 31 ed 5d 5a 8b 45 f0 89 4d e8 e8 df 71 ff ff 84 c0 8b 4d e8 0f 84 94 02 00 00 <8b> 81 e4 4e 00 00 8b 91 e8 4e 00 00 89 4d e8 e8 d0 7a ff ff e8 kernel: [ 205.211667] EIP: vmx_vcpu_run+0x24c/0x590 [kvm_intel] SS:ESP: 0068:f3313dd0 kernel: [ 205.214131] CR2: 4ee4 kernel: [ 205.216577] ---[ end trace 9ab07b7d6f771993 ]--- -- 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/1881072 Title: "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Issue found on 4.15.0-1061-kvm, with KVM instance zeppo, moe. The ubuntu_kvm_smoke_test will fail with: uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:ee:15:c8. Traces can be found in syslog. systemd[1]: Started Daemon for generating UUIDs. kernel: kauditd_printk_skb: 9 callbacks suppressed kernel: audit: type=1400 audit(1590647581.375:20): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1291 comm="apparmor_parser" kernel: audit: type=1400 audit(1590647581.691:21): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1294 comm="apparmor_parser" kernel: audit: type=1400 audit(1590647581.927:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1297 comm="apparmor_parser" kernel: audit: type=1400 audit(1590647582.155:23): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-
[Kernel-packages] [Bug 1881096] [NEW] Deflate counters reported by lscpumf are not valid or available with perf
You have been subscribed to a public bug: ---Problem Description--- ubuntu 20.04: perf on z15: some counters reported with lscpumf are not usable with perf stat -e ---uname output--- Linux ubu204 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = z15 8561 ---Steps to Reproduce--- lscpumf -c gives a list of available counters, but a few of them are not usable: DFLT_ACCESS,DFLT_CYCLES,DFLT_CC,DFLT_CCERROR perf list is also not offering these counters. A solution will be a backport to 20.04, and tried to made available for next SRU , code needed before 06-12. Addl Info from Dev: I have downloaded the following repository https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal and checked out branch master-next. Both patches appended apply without warning and the compilation showed no error. For the perf tool: e7950166e40271c02 perf vendor events s390: Add new deflate counters for IBM z15 For the s390 kernel d68d5d51dc898895b s390/cpum_cf: Add new extended counters for IBM z15 All accepted for kernel 5.7 rc1 Please include both patches into Ubuntu 20.04 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-185899 severity-medium targetmilestone-inin2004 -- Deflate counters reported by lscpumf are not valid or available with perf https://bugs.launchpad.net/bugs/1881096 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 1784240] Re: Driver doesn't correctly probe Samsung U28D590D 28-inch 4k after recent update
is it still an issue on 20.04? ** No longer affects: mesa (Ubuntu) ** Package changed: xorg-server (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784240 Title: Driver doesn't correctly probe Samsung U28D590D 28-inch 4k after recent update Status in linux package in Ubuntu: Incomplete Bug description: This monitor was correctly detected and worked properly at maximum resolution for the last 2 years, but X no longer correctly identifies the monitor and now only proposes a maximum display resolution of 1368x768 since a recent update. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Jul 29 11:10:25 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:67ef] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:9460] InstallationDate: Installed on 2016-05-20 (800 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/Whiteygu-lvm--root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8 dmi.board.name: GA-990FXA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Jul 29 09:18:04 2018 xserver.configfile: default xserver.errors: AMDGPU(0): Failed to open amdgpu hybrid version xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881096] perf vendor events s390: Add new deflate counters for IBM z15
Default Comment by Bridge ** Attachment added: "perf vendor events s390: Add new deflate counters for IBM z15" https://bugs.launchpad.net/bugs/1881096/+attachment/5377756/+files/0001-perf-vendor-events-s390-Add-new-deflate-counters-for.patch ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** 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/1881096 Title: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf Status in linux package in Ubuntu: New Bug description: ---Problem Description--- ubuntu 20.04: perf on z15: some counters reported with lscpumf are not usable with perf stat -e ---uname output--- Linux ubu204 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = z15 8561 ---Steps to Reproduce--- lscpumf -c gives a list of available counters, but a few of them are not usable: DFLT_ACCESS,DFLT_CYCLES,DFLT_CC,DFLT_CCERROR perf list is also not offering these counters. A solution will be a backport to 20.04, and tried to made available for next SRU , code needed before 06-12. Addl Info from Dev: I have downloaded the following repository https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal and checked out branch master-next. Both patches appended apply without warning and the compilation showed no error. For the perf tool: e7950166e40271c02 perf vendor events s390: Add new deflate counters for IBM z15 For the s390 kernel d68d5d51dc898895b s390/cpum_cf: Add new extended counters for IBM z15 All accepted for kernel 5.7 rc1 Please include both patches into Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881096] Re: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf
** Summary changed: - Deflate counters reported by lscpumf are not valid or available with perf + [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881096 Title: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- ubuntu 20.04: perf on z15: some counters reported with lscpumf are not usable with perf stat -e ---uname output--- Linux ubu204 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = z15 8561 ---Steps to Reproduce--- lscpumf -c gives a list of available counters, but a few of them are not usable: DFLT_ACCESS,DFLT_CYCLES,DFLT_CC,DFLT_CCERROR perf list is also not offering these counters. A solution will be a backport to 20.04, and tried to made available for next SRU , code needed before 06-12. Addl Info from Dev: I have downloaded the following repository https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal and checked out branch master-next. Both patches appended apply without warning and the compilation showed no error. For the perf tool: e7950166e40271c02 perf vendor events s390: Add new deflate counters for IBM z15 For the s390 kernel d68d5d51dc898895b s390/cpum_cf: Add new extended counters for IBM z15 All accepted for kernel 5.7 rc1 Please include both patches into Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1881096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 455954] Re: [K8M800] AntSpotlight screensaver causes system to lock up immediately
** Changed in: mesa (Ubuntu) Status: Confirmed => 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/455954 Title: [K8M800] AntSpotlight screensaver causes system to lock up immediately Status in linux package in Ubuntu: Won't Fix Status in mesa package in Ubuntu: Won't Fix Status in xserver-xorg-video-openchrome package in Ubuntu: Fix Released Bug description: Note: this bug just reappeared in Xubuntu 11.10. I filed this as a new bug #871471. Binary package hint: xscreensaver Selecting AntSpotlight in either xscreensaver or Gnome Screensaver causes this system to freeze immediately. Ubuntu version and kernel version, etc. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=9.10 DISTRIB_CODENAME=karmic DISTRIB_DESCRIPTION="Ubuntu karmic (development branch)" Linux cupid 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux model name: Mobile AMD Sempron(tm) Processor 2800+ At the moment, neither xscreensaver nor Gnome Screensaver is installed, but the package containing this screensaver (xscreensaver- gl) is still installed. (I am about to remove it). Since memory may be an issue, I'll enclose a copy of /proc/meminfo ProblemType: Bug Architecture: i386 Date: Mon Oct 19 18:07:43 2009 DistroRelease: Ubuntu 9.10 Package: xscreensaver-gl 5.08-0ubuntu5 ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: xscreensaver Uname: Linux 2.6.31-14-generic i686 XsessionErrors: (gnome-settings-daemon:2256): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (polkit-gnome-authentication-agent-1:2332): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:2313): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/455954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878338] Re: Laptop freezes whenever it runs out of battery
I never let battery on my laptop runs out... So what was the old behavior? ** 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/1878338 Title: Laptop freezes whenever it runs out of battery Status in linux package in Ubuntu: Incomplete Bug description: New behaviour for Ubuntu 20.04 LTS - as soon as it runs out of battery, the laptop locks up. Any audio that was playing will be played repeatedly on a short loop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vadi 3163 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 07:40:48 2020 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=8c0e25d4-6e36-428e-b354-4c71b99db752 InstallationDate: Installed on 2017-02-15 (1182 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E7470 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-07 (5 days ago) dmi.bios.date: 10/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.8 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.8:bd10/08/2019:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881096] Re: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: ubuntu-z-systems Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881096 Title: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- ubuntu 20.04: perf on z15: some counters reported with lscpumf are not usable with perf stat -e ---uname output--- Linux ubu204 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = z15 8561 ---Steps to Reproduce--- lscpumf -c gives a list of available counters, but a few of them are not usable: DFLT_ACCESS,DFLT_CYCLES,DFLT_CC,DFLT_CCERROR perf list is also not offering these counters. A solution will be a backport to 20.04, and tried to made available for next SRU , code needed before 06-12. Addl Info from Dev: I have downloaded the following repository https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal and checked out branch master-next. Both patches appended apply without warning and the compilation showed no error. For the perf tool: e7950166e40271c02 perf vendor events s390: Add new deflate counters for IBM z15 For the s390 kernel d68d5d51dc898895b s390/cpum_cf: Add new extended counters for IBM z15 All accepted for kernel 5.7 rc1 Please include both patches into Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1881096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878338] Re: Laptop freezes whenever it runs out of battery
It suspended. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878338 Title: Laptop freezes whenever it runs out of battery Status in linux package in Ubuntu: Incomplete Bug description: New behaviour for Ubuntu 20.04 LTS - as soon as it runs out of battery, the laptop locks up. Any audio that was playing will be played repeatedly on a short loop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vadi 3163 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 07:40:48 2020 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=8c0e25d4-6e36-428e-b354-4c71b99db752 InstallationDate: Installed on 2017-02-15 (1182 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E7470 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-07 (5 days ago) dmi.bios.date: 10/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.8 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.8:bd10/08/2019:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880834] Re: qeth: utilize virtual MAC for Layer2 OSD devices
I found one little issue in the backports (Julian). They contain a cherry-pick line, but I expected a backport line. If it's okay for you I just change from: (cherry picked from commit 21b1702af12eb62bb40d994c9c1546ecacfc8456) to (backported from commit 21b1702af12eb62bb40d994c9c1546ecacfc8456) (same for the 2nd backport). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880834 Title: qeth: utilize virtual MAC for Layer2 OSD devices Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: ---Problem Description--- qeth on a DPM-managed IBM Z machine does not obtain its MAC Address for L2 OSD interfaces from the OSA Network Adapter. Instead it uses a random MAC Address. This causes connectivity issues in setups where a reliable & pre-determined MAC Address is required - ie. when doing network configuration via DHCP. ---uname output--- Ubuntu 18.04 / vmlinuz-4.15.0-101-generic Machine Type = IBM z14 GA2 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- - Bring up a qeth L2 OSD interface in DPM-managed LPAR. - Inspect the interface's MAC Address. It should be the same as displayed in the DPM Panels. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Attach sysctl -a output output to the bug. Backport of "s390/qeth: improve fallback to random MAC address" Backport of "s390/qeth: utilize virtual MAC for Layer2 OSD devices" This ticket is for 18.04 only. Already available with 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1880834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864871] Re: Failed to init Intel sound card in 20.04
@Hui, added whole output as attachment attachment You can see important lines also from here: [3.598868] snd_hda_intel :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [3.753859] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 [3.754706] sof-audio-pci :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [3.755874] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [3.755881] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [3.756003] sof-audio-pci :00:1f.3: use msi interrupt mode [3.756309] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.766388] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [3.766390] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.803652] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [3.803655] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [3.803657] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [3.804013] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864871/+attachment/5377835/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864871 Title: Failed to init Intel sound card in 20.04 Status in linux package in Ubuntu: Confirmed Bug description: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card there is no sound available because sound card not detected (only dummy output available in sound settings): $ alsamixer cannot open mixer: No such file or directory $ lspci -nnk |grep -A2 audio lspci: Unable to load libkmod resources: error -12 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] Subsystem: Lenovo Device [17aa:3816] Kernel driver in use: sof-audio-pci 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:02a3] Subsystem: Lenovo Device [17aa:3819] $ pacmd list-cards 0 card(s) available. $ dmesg |grep sof [0.755398] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [0.755400] software IO TLB: mapped [mem 0x7d91d000-0x8191d000] (64MB) [2.142149] systemd[1]: Mounting Mount unit for software-boutique, revision 54... [2.333772] systemd[1]: Mounted Mount unit for software-boutique, revision 54. [2.770307] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [2.770316] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [2.770473] sof-audio-pci :00:1f.3: use msi interrupt mode [2.770696] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.779359] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [2.779360] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [2.817051] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [2.817054] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [2.817057] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [2.817058] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 I've found similar bug reported here: https://bugs.archlinux.org/task/64720 As a workaround I've added `snd_hda_intel.dmic_detect=0` to boot options and after that sound card successfully detected and started working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 26 19:22:05 2020 InstallationDate: Installed on 2020-02-25 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:0c02 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20RR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=94f1e507-a44a-46a8-9163-548d27303afb ro quiet splash vt.handoff=7 RelatedPacka
[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()
OK so object 0x211 looks like the curlprit, I just can't see the pool name being dumped - do you know which pool is triggering this issue? If you can identify the poolt then we can next dump the potentially corrupt object using: sudo zdb - / 529 -- 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/1861235 Title: zfs recv PANIC at range_tree.c:304:range_tree_find_impl() Status in Linux: New Status in zfs-linux package in Ubuntu: Incomplete Status in zfs-linux source package in Bionic: New Bug description: Same as bug 1861228 but with a newer kernel installed. [ 790.702566] VERIFY(size != 0) failed [ 790.702590] PANIC at range_tree.c:304:range_tree_find_impl() [ 790.702611] Showing stack for process 28685 [ 790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 2.0 12/17/2015 [ 790.702616] Call Trace: [ 790.702626] dump_stack+0x6d/0x8e [ 790.702637] spl_dumpstack+0x42/0x50 [spl] [ 790.702640] spl_panic+0xc8/0x110 [spl] [ 790.702645] ? __switch_to_asm+0x41/0x70 [ 790.702714] ? arc_prune_task+0x1a/0x40 [zfs] [ 790.702740] ? dbuf_dirty+0x43d/0x850 [zfs] [ 790.702745] ? getrawmonotonic64+0x43/0xd0 [ 790.702746] ? getrawmonotonic64+0x43/0xd0 [ 790.702775] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702778] ? getrawmonotonic64+0x43/0xd0 [ 790.702805] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702807] ? mutex_lock+0x12/0x40 [ 790.702833] ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs] [ 790.702866] range_tree_find_impl+0x88/0x90 [zfs] [ 790.702870] ? spl_kmem_zalloc+0xdc/0x1a0 [spl] [ 790.702902] range_tree_clear+0x4f/0x60 [zfs] [ 790.702930] dnode_free_range+0x11f/0x5a0 [zfs] [ 790.702957] dmu_object_free+0x53/0x90 [zfs] [ 790.702983] dmu_free_long_object+0x9f/0xc0 [zfs] [ 790.703010] receive_freeobjects.isra.12+0x7a/0x100 [zfs] [ 790.703036] receive_writer_thread+0x6d2/0xa60 [zfs] [ 790.703040] ? set_curr_task_fair+0x2b/0x60 [ 790.703043] ? spl_kmem_free+0x33/0x40 [spl] [ 790.703048] ? kfree+0x165/0x180 [ 790.703073] ? receive_free.isra.13+0xc0/0xc0 [zfs] [ 790.703078] thread_generic_wrapper+0x74/0x90 [spl] [ 790.703081] kthread+0x121/0x140 [ 790.703084] ? __thread_exit+0x20/0x20 [spl] [ 790.703085] ? kthread_create_worker_on_cpu+0x70/0x70 [ 790.703088] ret_from_fork+0x35/0x40 [ 967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds. [ 967.636979] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637076] txg_quiesce D0 14810 2 0x8000 [ 967.637080] Call Trace: [ 967.637089] __schedule+0x24e/0x880 [ 967.637092] schedule+0x2c/0x80 [ 967.637106] cv_wait_common+0x11e/0x140 [spl] [ 967.637114] ? wait_woken+0x80/0x80 [ 967.637122] __cv_wait+0x15/0x20 [spl] [ 967.637210] txg_quiesce_thread+0x2cb/0x3d0 [zfs] [ 967.637278] ? txg_delay+0x1b0/0x1b0 [zfs] [ 967.637286] thread_generic_wrapper+0x74/0x90 [spl] [ 967.637291] kthread+0x121/0x140 [ 967.637297] ? __thread_exit+0x20/0x20 [spl] [ 967.637299] ? kthread_create_worker_on_cpu+0x70/0x70 [ 967.637304] ret_from_fork+0x35/0x40 [ 967.637326] INFO: task zfs:28590 blocked for more than 120 seconds. [ 967.637371] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637467] zfs D0 28590 28587 0x8080 [ 967.637470] Call Trace: [ 967.637474] __schedule+0x24e/0x880 [ 967.637477] schedule+0x2c/0x80 [ 967.637486] cv_wait_common+0x11e/0x140 [spl] [ 967.637491] ? wait_woken+0x80/0x80 [ 967.637498] __cv_wait+0x15/0x20 [spl] [ 967.637554] dmu_recv_stream+0xa51/0xef0 [zfs] [ 967.637630] zfs_ioc_recv_impl+0x306/0x1100 [zfs] [ 967.637679] ? dbuf_read+0x34a/0x920 [zfs] [ 967.637725] ? dbuf_rele+0x36/0x40 [zfs] [ 967.637728] ? _cond_resched+0x19/0x40 [ 967.637798] zfs_ioc_recv_new+0x33d/0x410 [zfs] [ 967.637809] ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl] [ 967.637816] ? spl_vmem_alloc+0x19/0x20 [spl] [ 967.637828] ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair] [ 967.637834] ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair] [ 967.637840] ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair] [ 967.637905] zfsdev_ioctl+0x451/0x610 [zfs] [ 967.637913] do_vfs_ioctl+0xa8/0x630 [ 967.637917] ? __audit_syscall_entry+0xbc/0x110 [ 967.637924] ? syscall_trace_enter+0x1da/0x2d0 [ 967.637927] SyS_ioctl+0x79/0x90 [ 967.637930] do_syscall_64+0x73/0x130 [ 967.637935] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 967.637938] RIP: 0033:0x7fc3
[Kernel-packages] [Bug 1881109] [NEW] [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be triggered by scsi errors.
You have been subscribed to a public bug: We can reproduce a crash in the block layer with lots of stress on lots of SCSI disks (on an XIV storage server). We seem to have several scsi stalls in the logs/errors (needs to be analyzed further) but in the end we do crash with this this calltrace. [20832.901147] Failing address: 7fe00dea8000 TEID: 7fe00dea8403 [20832.901159] Fault in home space mode while using kernel ASCE. [20832.901171] AS:01d3cccf400b R2:03fd0020800b R3:03fd0020c007 S:03fc1cc78800 P:0400 [20832.901264] Oops: 0011 ilc:2 [#1] SMP [20832.901280] Modules linked in: vhost_net vhost macvtap macvlan tap xfs xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge aufs overlay dm_service_time dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua s390_trng chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio 8021q garp mrp stp llc sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_mirror dm_region_hash dm_log qeth_l2 pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup [20832.901516] CPU: 29 PID: 389709 Comm: CPU 0/KVM Kdump: loaded Not tainted 5.4.0-29-generic #33-Ubuntu [20832.901530] Hardware name: IBM 8561 T01 708 (LPAR) [20832.901542] Krnl PSW : 0404e0018000 01d3cbd559be (try_to_wake_up+0x4e/0x700) [20832.901575]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [20832.901744] Krnl GPRS: 03fc917cd988 7fe0 7fe0001e 0003 [20832.901750] 004c 040003fd005a4600 0003 [20832.901753]0003 7fe00dea8454 7fe00dea7b00 [20832.901754]03f44bd9b300 01d3cc587088 7fe0021c7ae0 7fe0021c7a60 [20832.901767] Krnl Code: 01d3cbd559b2: 41902954la %r9,2388(%r2) 01d3cbd559b6: 582003acl %r2,940 #01d3cbd559ba: a718lhi %r1,0 >01d3cbd559be: ba129000cs %r1,%r2,0(%r9) 01d3cbd559c2: a77401c9brc 7,01d3cbd55d54 01d3cbd559c6: e310b0080004lg %r1,8(%r11) 01d3cbd559cc: b9800018ngr %r1,%r8 01d3cbd559d0: a774001fbrc 7,01d3cbd55a0e [20832.901784] Call Trace: [20832.901816] ([<01d3cc57e0ac>] cleanup_critical+0x0/0x474) [20832.901823] [<01d3cc1d16ba>] rq_qos_wake_function+0x8a/0xa0 [20832.901827] [<01d3cbd74bde>] __wake_up_common+0x9e/0x1b0 [20832.901829] [<01d3cbd750e4>] __wake_up_common_lock+0x94/0xe0 [20832.901830] [<01d3cbd7515a>] __wake_up+0x2a/0x40 [20832.901835] [<01d3cc1e8640>] wbt_done+0x90/0xe0 [20832.901837] [<01d3cc1d17be>] __rq_qos_done+0x3e/0x60 [20832.901841] [<01d3cc1bd5b0>] blk_mq_free_request+0xe0/0x140 [20832.901848] [<01d3cc35fc60>] dm_softirq_done+0x140/0x230 [20832.901849] [<01d3cc1bbfbc>] blk_done_softirq+0xbc/0xe0 [20832.901850] [<01d3cc57e710>] __do_softirq+0x100/0x360 [20832.901853] [<01d3cbd2525e>] irq_exit+0x9e/0xc0 [20832.901856] [<01d3cbcb0b18>] do_IRQ+0x78/0xb0 [20832.901859] [<01d3cc57dc28>] ext_int_handler+0x128/0x12c [20832.901860] [<01d3cc57d306>] sie_exit+0x0/0x46 [20832.901866] ([<01d3cbce944a>] __vcpu_run+0x27a/0xc30) [20832.901870] [<01d3cbcf29a8>] kvm_arch_vcpu_ioctl_run+0x2d8/0x840 [20832.901875] [<01d3cbcdd242>] kvm_vcpu_ioctl+0x282/0x770 [20832.901880] [<01d3cbf85f66>] do_vfs_ioctl+0x376/0x690 [20832.901881] [<01d3cbf86304>] ksys_ioctl+0x84/0xb0 [20832.901883] [<01d3cbf8639a>] __s390x_sys_ioctl+0x2a/0x40 [20832.901885] [<01d3cc57d5f2>] system_call+0x2a6/0x2c8 [20832.901885] Last Breaking-Event-Address: [20832.901889] [<01d3cbd5607e>] wake_up_process+0xe/0x20 [20832.901897] Kernel panic - not syncing: Fatal exception in interrupt Addl. comment: In all dumps we've seen so far a crash similar to what Christian posted in comment #2 would happen soon after the SCSI Midlayer went through Error Recovery, after issuing SCSI Aborts and potentially SCSI Device and Target resets. >From our most recent repro: [20226.914939] sd 1:0:3:16687: [sdatp] tag#1256 Done: TIMEOUT_ERROR Result: hostbyte=DID_OK driverbyte=DRIVER_OK [20226.914948] sd 1:0:3:16687
[Kernel-packages] [Bug 1881107] [NEW] zfs: backport AES-GCM performance accelleration
Public bug reported: == SRU Justification == Upstream commit 31b160f0a6c673c8f926233af2ed6d5354808393 contains AES- GCM acceleration changes that significantly improve encrypted performance. Tests on a memory backed pool show performance improvements of ~15-22% for AES-CCM writes, ~17-20% AES-CCM reads, 34-36% AES-GCM writes and ~79-80% AES-GCM reads on a Sandybridge x86-64 CPU, so this looks like a promising optimization that will benefit a lot of users. == The fix == Backport of upstream 31b160f0a6c673c8f926233af2ed6d5354808393 - this is already backported in Groovy ZFS 0.8.3-1ubuntu13 == Test case == Run ZFS performance tests from ubuntu_performance_zfs_encryption ubuntu kernel team autotests. With the fix the encryption runs significantly faster, as noted earlier in the SRU justification. == Regression Potential == This fix alters the crypto engine and adds in new optimizations for CPUs that have capable instruction sets. There is a risk that this new crypto code is erroneous. ** Affects: zfs-linux (Ubuntu) Importance: Medium Assignee: Colin Ian King (colin-king) Status: Fix Released ** Affects: zfs-linux (Ubuntu Focal) Importance: Medium Assignee: Colin Ian King (colin-king) Status: In Progress ** Affects: zfs-linux (Ubuntu Groovy) Importance: Medium Assignee: Colin Ian King (colin-king) Status: Fix Released ** Changed in: zfs-linux (Ubuntu) Status: New => In Progress ** Changed in: zfs-linux (Ubuntu) Importance: Undecided => Medium ** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Also affects: zfs-linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Groovy) Importance: Medium Assignee: Colin Ian King (colin-king) Status: In Progress ** Changed in: zfs-linux (Ubuntu Focal) Status: New => In Progress ** Changed in: zfs-linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: zfs-linux (Ubuntu Focal) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: zfs-linux (Ubuntu Groovy) Status: In Progress => Fix Released -- 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/1881107 Title: zfs: backport AES-GCM performance accelleration Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: In Progress Status in zfs-linux source package in Groovy: Fix Released Bug description: == SRU Justification == Upstream commit 31b160f0a6c673c8f926233af2ed6d5354808393 contains AES- GCM acceleration changes that significantly improve encrypted performance. Tests on a memory backed pool show performance improvements of ~15-22% for AES-CCM writes, ~17-20% AES-CCM reads, 34-36% AES-GCM writes and ~79-80% AES-GCM reads on a Sandybridge x86-64 CPU, so this looks like a promising optimization that will benefit a lot of users. == The fix == Backport of upstream 31b160f0a6c673c8f926233af2ed6d5354808393 - this is already backported in Groovy ZFS 0.8.3-1ubuntu13 == Test case == Run ZFS performance tests from ubuntu_performance_zfs_encryption ubuntu kernel team autotests. With the fix the encryption runs significantly faster, as noted earlier in the SRU justification. == Regression Potential == This fix alters the crypto engine and adds in new optimizations for CPUs that have capable instruction sets. There is a risk that this new crypto code is erroneous. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881109] [NEW] [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be triggered by scsi errors.
Public bug reported: We can reproduce a crash in the block layer with lots of stress on lots of SCSI disks (on an XIV storage server). We seem to have several scsi stalls in the logs/errors (needs to be analyzed further) but in the end we do crash with this this calltrace. [20832.901147] Failing address: 7fe00dea8000 TEID: 7fe00dea8403 [20832.901159] Fault in home space mode while using kernel ASCE. [20832.901171] AS:01d3cccf400b R2:03fd0020800b R3:03fd0020c007 S:03fc1cc78800 P:0400 [20832.901264] Oops: 0011 ilc:2 [#1] SMP [20832.901280] Modules linked in: vhost_net vhost macvtap macvlan tap xfs xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge aufs overlay dm_service_time dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua s390_trng chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio 8021q garp mrp stp llc sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_mirror dm_region_hash dm_log qeth_l2 pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup [20832.901516] CPU: 29 PID: 389709 Comm: CPU 0/KVM Kdump: loaded Not tainted 5.4.0-29-generic #33-Ubuntu [20832.901530] Hardware name: IBM 8561 T01 708 (LPAR) [20832.901542] Krnl PSW : 0404e0018000 01d3cbd559be (try_to_wake_up+0x4e/0x700) [20832.901575]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [20832.901744] Krnl GPRS: 03fc917cd988 7fe0 7fe0001e 0003 [20832.901750] 004c 040003fd005a4600 0003 [20832.901753]0003 7fe00dea8454 7fe00dea7b00 [20832.901754]03f44bd9b300 01d3cc587088 7fe0021c7ae0 7fe0021c7a60 [20832.901767] Krnl Code: 01d3cbd559b2: 41902954la %r9,2388(%r2) 01d3cbd559b6: 582003acl %r2,940 #01d3cbd559ba: a718lhi %r1,0 >01d3cbd559be: ba129000cs %r1,%r2,0(%r9) 01d3cbd559c2: a77401c9brc 7,01d3cbd55d54 01d3cbd559c6: e310b0080004lg %r1,8(%r11) 01d3cbd559cc: b9800018ngr %r1,%r8 01d3cbd559d0: a774001fbrc 7,01d3cbd55a0e [20832.901784] Call Trace: [20832.901816] ([<01d3cc57e0ac>] cleanup_critical+0x0/0x474) [20832.901823] [<01d3cc1d16ba>] rq_qos_wake_function+0x8a/0xa0 [20832.901827] [<01d3cbd74bde>] __wake_up_common+0x9e/0x1b0 [20832.901829] [<01d3cbd750e4>] __wake_up_common_lock+0x94/0xe0 [20832.901830] [<01d3cbd7515a>] __wake_up+0x2a/0x40 [20832.901835] [<01d3cc1e8640>] wbt_done+0x90/0xe0 [20832.901837] [<01d3cc1d17be>] __rq_qos_done+0x3e/0x60 [20832.901841] [<01d3cc1bd5b0>] blk_mq_free_request+0xe0/0x140 [20832.901848] [<01d3cc35fc60>] dm_softirq_done+0x140/0x230 [20832.901849] [<01d3cc1bbfbc>] blk_done_softirq+0xbc/0xe0 [20832.901850] [<01d3cc57e710>] __do_softirq+0x100/0x360 [20832.901853] [<01d3cbd2525e>] irq_exit+0x9e/0xc0 [20832.901856] [<01d3cbcb0b18>] do_IRQ+0x78/0xb0 [20832.901859] [<01d3cc57dc28>] ext_int_handler+0x128/0x12c [20832.901860] [<01d3cc57d306>] sie_exit+0x0/0x46 [20832.901866] ([<01d3cbce944a>] __vcpu_run+0x27a/0xc30) [20832.901870] [<01d3cbcf29a8>] kvm_arch_vcpu_ioctl_run+0x2d8/0x840 [20832.901875] [<01d3cbcdd242>] kvm_vcpu_ioctl+0x282/0x770 [20832.901880] [<01d3cbf85f66>] do_vfs_ioctl+0x376/0x690 [20832.901881] [<01d3cbf86304>] ksys_ioctl+0x84/0xb0 [20832.901883] [<01d3cbf8639a>] __s390x_sys_ioctl+0x2a/0x40 [20832.901885] [<01d3cc57d5f2>] system_call+0x2a6/0x2c8 [20832.901885] Last Breaking-Event-Address: [20832.901889] [<01d3cbd5607e>] wake_up_process+0xe/0x20 [20832.901897] Kernel panic - not syncing: Fatal exception in interrupt Addl. comment: In all dumps we've seen so far a crash similar to what Christian posted in comment #2 would happen soon after the SCSI Midlayer went through Error Recovery, after issuing SCSI Aborts and potentially SCSI Device and Target resets. >From our most recent repro: [20226.914939] sd 1:0:3:16687: [sdatp] tag#1256 Done: TIMEOUT_ERROR Result: hostbyte=DID_OK driverbyte=DRIVER_OK [20226.914948] sd 1:0:3:16687: [sdatp] tag#1256 CD
[Kernel-packages] [Bug 1878147] Re: Realtek 8723DE [10ec:d723] subsystem [10ec:d738] disconnects unsolicitedly when Bluetooth is paired: Reason: 23=IEEE8021X_FAILED
** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: Incomplete => 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/1878147 Title: Realtek 8723DE [10ec:d723] subsystem [10ec:d738] disconnects unsolicitedly when Bluetooth is paired: Reason: 23=IEEE8021X_FAILED Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Eoan: Invalid Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Invalid Status in linux source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux-oem-osp1 source package in Focal: Invalid Status in linux source package in Groovy: Confirmed Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux-oem-osp1 source package in Groovy: Invalid Bug description: [ 7.002889] wlp5s0: authenticate with a4:56:30:cc:0f:30 [ 7.146619] wlp5s0: send auth to a4:56:30:cc:0f:30 (try 1/3) [ 7.258747] wlp5s0: authenticated [ 7.262852] wlp5s0: associate with a4:56:30:cc:0f:30 (try 1/3) [ 7.266190] wlp5s0: RX AssocResp from a4:56:30:cc:0f:30 (capab=0x431 status=0 aid=4) [ 7.266205] rtw_pci :05:00.0: sta a4:56:30:cc:0f:30 joined with macid 0 [ 7.266425] rtw_pci :05:00.0: failed to send h2c command [ 7.266437] wlp5s0: associated [ 7.299291] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s0: link becomes ready That error "failed to send h2c command" is only observed multiple times in current oem-osp1 kernel for multiple times during the test rounds, and is never found with the OOT module built from https://github.com/rtlwifi-linux/rtw88_8723de/tree/master-coex-trial2. And so is following error when reproduced against Ubuntu kernels: [ 207.523312] wlp5s0: deauthenticated from a4:56:30:cc:0f:30 (Reason: 23=IEEE8021X_FAILED). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem-osp1 5.0.0.1050.53 ProcVersionSignature: Ubuntu 5.0.0-1050.55-oem-osp1 5.0.21 Uname: Linux 5.0.0-1050-oem-osp1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1667 F pulseaudio u 3061 F pulseaudio /dev/snd/controlC0: gdm1667 F pulseaudio u 3061 F pulseaudio Date: Tue May 12 14:59:32 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-grenn+X39 InstallationDate: Installed on 2020-04-10 (31 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04d9:0024 Holtek Semiconductor, Inc. Bus 001 Device 003: ID 0bda:d739 Realtek Semiconductor Corp. Bus 001 Device 005: ID 062a:4c01 Creative Labs Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3888 ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1050-oem-osp1 root=UUID=17e0a095-201d-4dca-a2e7-6e16dcd6a797 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1050-oem-osp1 N/A linux-backports-modules-5.0.0-1050-oem-osp1 N/A linux-firmware 1.173.18 SourcePackage: linux-oem-osp1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.19.29 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.19.29:bd02/13/2020:svnDellInc.:pnVostro3888:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3888 dmi.product.sku: 09B2 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1878147/+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 1867885] Re: Suspend does not work on Thinkpad X1 Yoga
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867885 Title: Suspend does not work on Thinkpad X1 Yoga Status in linux package in Ubuntu: Fix Released Bug description: After upgrading to the Kernel version 5.3.0-42-generic on Ubuntu 19.10 on my Thinkpad X1 Yoga I could not wake it up from suspend anymore. I downgraded to 5.3.0-40-generic and it works again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-15 (62 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QFS10B00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-42-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: 02/21/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET46W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QFS10B00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET46W(1.29):bd02/21/2020:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20QFS10B00 dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878147] Re: Realtek 8723DE [10ec:d723] subsystem [10ec:d738] disconnects unsolicitedly when Bluetooth is paired: Reason: 23=IEEE8021X_FAILED
Created new PPA for working backports: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1878147.20200518081444.7664 Verified on unstable/oem-5.6/focal/oem-osp1-bionic for 200 runs for each. Note in the end I can no longer reproduce [Case 1] from comment #9, and since it's confirmed that the third patch is critical to this issue for some reason, the final patch sets to be backported will include all three of them with additional patches to address conflicts. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878147 Title: Realtek 8723DE [10ec:d723] subsystem [10ec:d738] disconnects unsolicitedly when Bluetooth is paired: Reason: 23=IEEE8021X_FAILED Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Eoan: Invalid Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Invalid Status in linux source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux-oem-osp1 source package in Focal: Invalid Status in linux source package in Groovy: Confirmed Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux-oem-osp1 source package in Groovy: Invalid Bug description: [ 7.002889] wlp5s0: authenticate with a4:56:30:cc:0f:30 [ 7.146619] wlp5s0: send auth to a4:56:30:cc:0f:30 (try 1/3) [ 7.258747] wlp5s0: authenticated [ 7.262852] wlp5s0: associate with a4:56:30:cc:0f:30 (try 1/3) [ 7.266190] wlp5s0: RX AssocResp from a4:56:30:cc:0f:30 (capab=0x431 status=0 aid=4) [ 7.266205] rtw_pci :05:00.0: sta a4:56:30:cc:0f:30 joined with macid 0 [ 7.266425] rtw_pci :05:00.0: failed to send h2c command [ 7.266437] wlp5s0: associated [ 7.299291] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s0: link becomes ready That error "failed to send h2c command" is only observed multiple times in current oem-osp1 kernel for multiple times during the test rounds, and is never found with the OOT module built from https://github.com/rtlwifi-linux/rtw88_8723de/tree/master-coex-trial2. And so is following error when reproduced against Ubuntu kernels: [ 207.523312] wlp5s0: deauthenticated from a4:56:30:cc:0f:30 (Reason: 23=IEEE8021X_FAILED). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem-osp1 5.0.0.1050.53 ProcVersionSignature: Ubuntu 5.0.0-1050.55-oem-osp1 5.0.21 Uname: Linux 5.0.0-1050-oem-osp1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1667 F pulseaudio u 3061 F pulseaudio /dev/snd/controlC0: gdm1667 F pulseaudio u 3061 F pulseaudio Date: Tue May 12 14:59:32 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-grenn+X39 InstallationDate: Installed on 2020-04-10 (31 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04d9:0024 Holtek Semiconductor, Inc. Bus 001 Device 003: ID 0bda:d739 Realtek Semiconductor Corp. Bus 001 Device 005: ID 062a:4c01 Creative Labs Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3888 ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1050-oem-osp1 root=UUID=17e0a095-201d-4dca-a2e7-6e16dcd6a797 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1050-oem-osp1 N/A linux-backports-modules-5.0.0-1050-oem-osp1 N/A linux-firmware 1.173.18 SourcePackage: linux-oem-osp1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.19.29 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.19.29:bd02/13/2020:svnDellInc.:pnVostro3888:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr: dmi.product.fam
[Kernel-packages] [Bug 1881097] [NEW] [Thinkpad X1C7][Thinkpad X1C8]F1 and F4 Hotkey LED Light Stays ON/OFF when USB Headset is attached.
You have been subscribed to a public bug: Problem Description: Using Ubuntu 20.04 on a Thinkpad X1C7 machine. Speaker(F1) and Microphone(F4) Hotkey LED Light Stays ON/OFF when USB Headset is attached. - $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 Ubuntu Software: 3.36.1 - Expected Result: When LED light of Speaker(F1)/Microphone (F4) hotkeys is ON/OFF and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED light state will change accordingly. Actual Result: 1. When LED light of Speaker(F1)/Microphone (F4) hotkeys is OFF and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED light will STAY OFF and remains in OFF State always on the duration that the USB headset is attached to the machine. 2. If LED light of Speaker(F1)/Microphone (F4) hotkeys is ON and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED will STAY ON and remains in ON State on the duration that the USB headset is attached to the machine. 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: ubuntu 1410 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 18:48:04 2020 InstallationDate: Installed on 2020-05-28 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20U9SITR38 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=ab59da99-085b-4f8d-af14-4fc4240a8f83 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: 02/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET11C (1.01C ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9SITR38 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET11C(1.01C):bd02/12/2020:svnLENOVO:pn20U9SITR38:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9SITR38:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9SITR38 dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- [Thinkpad X1C7][Thinkpad X1C8]F1 and F4 Hotkey LED Light Stays ON/OFF when USB Headset is attached. https://bugs.launchpad.net/bugs/1881097 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 1877757] Re: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU
Please test this kernel. https://people.canonical.com/~hwang4/renoir/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877757 Title: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU Status in linux package in Ubuntu: Confirmed Bug description: New focal installation on a new Acer Swift 3 laptop with core i7-1065G7. No sound detected, KDE/pavucontrol shows Dummy output. External headset also not detected. I've googled around and tried to reinstall alsa and pulseaudio, tried alsa force-reload as well. Nothing helps. With snd_hda_intel.dmic_detect=0 speakers start working but microphone is not detected. External headset detected with both headphones and mic. I use this as a workaround for a time being. I've checked https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 bug. It is closed and use recent kernel and firmware but it does not fix my issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 18:56:15 2020 InstallationDate: Installed on 2020-04-24 (15 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Swift SF314-57G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=faf6a132-de60-44fa-a1a7-4cce8ef83b87 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd09/24/2019:svnAcer:pnSwiftSF314-57G:pvrV1.09:rvnIL:rnFloris_IL:rvrV1.09:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57G dmi.product.sku: dmi.product.version: V1.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881097] Re: [Thinkpad X1C7][Thinkpad X1C8]F1 and F4 Hotkey LED Light Stays ON/OFF when USB Headset is attached.
** 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/1881097 Title: [Thinkpad X1C7][Thinkpad X1C8]F1 and F4 Hotkey LED Light Stays ON/OFF when USB Headset is attached. Status in linux package in Ubuntu: New Bug description: Problem Description: Using Ubuntu 20.04 on a Thinkpad X1C7 machine. Speaker(F1) and Microphone(F4) Hotkey LED Light Stays ON/OFF when USB Headset is attached. - $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Ubuntu Software: 3.36.1 - Expected Result: When LED light of Speaker(F1)/Microphone (F4) hotkeys is ON/OFF and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED light state will change accordingly. Actual Result: 1. When LED light of Speaker(F1)/Microphone (F4) hotkeys is OFF and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED light will STAY OFF and remains in OFF State always on the duration that the USB headset is attached to the machine. 2. If LED light of Speaker(F1)/Microphone (F4) hotkeys is ON and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED will STAY ON and remains in ON State on the duration that the USB headset is attached to the machine. 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: ubuntu 1410 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 18:48:04 2020 InstallationDate: Installed on 2020-05-28 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20U9SITR38 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=ab59da99-085b-4f8d-af14-4fc4240a8f83 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: 02/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET11C (1.01C ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9SITR38 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET11C(1.01C):bd02/12/2020:svnLENOVO:pn20U9SITR38:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9SITR38:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9SITR38 dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864871] Re: Failed to init Intel sound card in 20.04
@Faith, Please upgrade linux-firmware 'sudo apt-get update; sudo apt install linux-firmware', then check if there is sof-cnl.ri in the /lib/firmware/intel/sof. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864871 Title: Failed to init Intel sound card in 20.04 Status in linux package in Ubuntu: Confirmed Bug description: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card there is no sound available because sound card not detected (only dummy output available in sound settings): $ alsamixer cannot open mixer: No such file or directory $ lspci -nnk |grep -A2 audio lspci: Unable to load libkmod resources: error -12 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] Subsystem: Lenovo Device [17aa:3816] Kernel driver in use: sof-audio-pci 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:02a3] Subsystem: Lenovo Device [17aa:3819] $ pacmd list-cards 0 card(s) available. $ dmesg |grep sof [0.755398] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [0.755400] software IO TLB: mapped [mem 0x7d91d000-0x8191d000] (64MB) [2.142149] systemd[1]: Mounting Mount unit for software-boutique, revision 54... [2.333772] systemd[1]: Mounted Mount unit for software-boutique, revision 54. [2.770307] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [2.770316] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [2.770473] sof-audio-pci :00:1f.3: use msi interrupt mode [2.770696] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.779359] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [2.779360] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [2.817051] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [2.817054] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [2.817057] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [2.817058] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 I've found similar bug reported here: https://bugs.archlinux.org/task/64720 As a workaround I've added `snd_hda_intel.dmic_detect=0` to boot options and after that sound card successfully detected and started working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 26 19:22:05 2020 InstallationDate: Installed on 2020-02-25 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:0c02 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20RR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=94f1e507-a44a-46a8-9163-548d27303afb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 SourcePackage: linux-5.4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CQCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IML dmi.modalias: dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML: dmi.product.family: ThinkBook 13s-IML dmi.product.name: 20RR dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML dmi.product.version: Lenovo ThinkBook 13s-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1881109] Re: [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be triggered by scsi errors.
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881109 Title: [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be triggered by scsi errors. Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: We can reproduce a crash in the block layer with lots of stress on lots of SCSI disks (on an XIV storage server). We seem to have several scsi stalls in the logs/errors (needs to be analyzed further) but in the end we do crash with this this calltrace. [20832.901147] Failing address: 7fe00dea8000 TEID: 7fe00dea8403 [20832.901159] Fault in home space mode while using kernel ASCE. [20832.901171] AS:01d3cccf400b R2:03fd0020800b R3:03fd0020c007 S:03fc1cc78800 P:0400 [20832.901264] Oops: 0011 ilc:2 [#1] SMP [20832.901280] Modules linked in: vhost_net vhost macvtap macvlan tap xfs xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge aufs overlay dm_service_time dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua s390_trng chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio 8021q garp mrp stp llc sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_mirror dm_region_hash dm_log qeth_l2 pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup [20832.901516] CPU: 29 PID: 389709 Comm: CPU 0/KVM Kdump: loaded Not tainted 5.4.0-29-generic #33-Ubuntu [20832.901530] Hardware name: IBM 8561 T01 708 (LPAR) [20832.901542] Krnl PSW : 0404e0018000 01d3cbd559be (try_to_wake_up+0x4e/0x700) [20832.901575]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [20832.901744] Krnl GPRS: 03fc917cd988 7fe0 7fe0001e 0003 [20832.901750] 004c 040003fd005a4600 0003 [20832.901753]0003 7fe00dea8454 7fe00dea7b00 [20832.901754]03f44bd9b300 01d3cc587088 7fe0021c7ae0 7fe0021c7a60 [20832.901767] Krnl Code: 01d3cbd559b2: 41902954la %r9,2388(%r2) 01d3cbd559b6: 582003acl %r2,940 #01d3cbd559ba: a718lhi %r1,0 >01d3cbd559be: ba129000cs %r1,%r2,0(%r9) 01d3cbd559c2: a77401c9brc 7,01d3cbd55d54 01d3cbd559c6: e310b0080004lg %r1,8(%r11) 01d3cbd559cc: b9800018ngr %r1,%r8 01d3cbd559d0: a774001fbrc 7,01d3cbd55a0e [20832.901784] Call Trace: [20832.901816] ([<01d3cc57e0ac>] cleanup_critical+0x0/0x474) [20832.901823] [<01d3cc1d16ba>] rq_qos_wake_function+0x8a/0xa0 [20832.901827] [<01d3cbd74bde>] __wake_up_common+0x9e/0x1b0 [20832.901829] [<01d3cbd750e4>] __wake_up_common_lock+0x94/0xe0 [20832.901830] [<01d3cbd7515a>] __wake_up+0x2a/0x40 [20832.901835] [<01d3cc1e8640>] wbt_done+0x90/0xe0 [20832.901837] [<01d3cc1d17be>] __rq_qos_done+0x3e/0x60 [20832.901841] [<01d3cc1bd5b0>] blk_mq_free_request+0xe0/0x140 [20832.901848] [<01d3cc35fc60>] dm_softirq_done+0x140/0x230 [20832.901849] [<01d3cc1bbfbc>] blk_done_softirq+0xbc/0xe0 [20832.901850] [<01d3cc57e710>] __do_softirq+0x100/0x360 [20832.901853] [<01d3cbd2525e>] irq_exit+0x9e/0xc0 [20832.901856] [<01d3cbcb0b18>] do_IRQ+0x78/0xb0 [20832.901859] [<01d3cc57dc28>] ext_int_handler+0x128/0x12c [20832.901860] [<01d3cc57d306>] sie_exit+0x0/0x46 [20832.901866] ([<01d3cbce944a>] __vcpu_run+0x27a/0xc30) [20832.901870] [<01d3cbcf29a8>] kvm_arch_vcpu_ioctl_run+0x2d8/0x840 [20832.901875] [<01d3cbcdd242>] kvm_vcpu_ioctl+0x282/0x770 [20832.901880] [<01d3cbf85f66>] do_vfs_ioctl+0x376/0x690 [20832.901881] [<01d3cbf86304>] ksys_ioctl+0x84/0xb0 [20832.901883] [<01d3cbf8639a>] __s390x_sys_ioctl+0x2a/0x40 [20832.901885] [<01d3cc57d5f2>] system
[Kernel-packages] [Bug 1881097] 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/1881097 Title: [Thinkpad X1C7][Thinkpad X1C8]F1 and F4 Hotkey LED Light Stays ON/OFF when USB Headset is attached. Status in linux package in Ubuntu: Confirmed Bug description: Problem Description: Using Ubuntu 20.04 on a Thinkpad X1C7 machine. Speaker(F1) and Microphone(F4) Hotkey LED Light Stays ON/OFF when USB Headset is attached. - $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Ubuntu Software: 3.36.1 - Expected Result: When LED light of Speaker(F1)/Microphone (F4) hotkeys is ON/OFF and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED light state will change accordingly. Actual Result: 1. When LED light of Speaker(F1)/Microphone (F4) hotkeys is OFF and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED light will STAY OFF and remains in OFF State always on the duration that the USB headset is attached to the machine. 2. If LED light of Speaker(F1)/Microphone (F4) hotkeys is ON and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED will STAY ON and remains in ON State on the duration that the USB headset is attached to the machine. 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: ubuntu 1410 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 18:48:04 2020 InstallationDate: Installed on 2020-05-28 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20U9SITR38 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=ab59da99-085b-4f8d-af14-4fc4240a8f83 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: 02/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET11C (1.01C ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9SITR38 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET11C(1.01C):bd02/12/2020:svnLENOVO:pn20U9SITR38:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9SITR38:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9SITR38 dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround
I installed 5.7.0-5 from that link but it looks like the bcmwl module still fails to compile: Building module: cleaning build area... make -j4 KERNELRELEASE=5.7.0-5-generic -C /lib/modules/5.7.0-5-generic/build M=/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build(bad exit status: 2) ERROR (dkms apport): kernel package linux-headers-5.7.0-5-generic is not supported Error! Bad return status for module build on kernel: 5.7.0-5-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808418 Title: Thinkpad T430u won't boot without noapic workaround Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: I've used Ubuntu on this specific machine for years without problems, but starting with the 4.13 kernel that came with the 17.10 HWE and continuing into 18.04 kernels my computer would no longer boot, hanging at various screens: - A blank screen with a flashing cursor - A screen with this message: Loading Linux 4.13.0.36-generic ... Loading initial ramdisk ... - A screen with kernel messages, ending in: APCI: EC: interrupt blocked I've encountered the bug in a number of kernels, including: - 4.13.0-32 - 4.13.0-36 - 4.13.0-37 - 4.15.0-24 - 4.15.0-34 - 4.15.0-36 - 4.15.0-38 - 4.15.0-42 - 4.20.0-rc7 I was able to work around the issue by adding noapic to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic" I'm not entirely sure of the consequences of this workaround, but one thing I've noticed is significantly reduced battery life. This bug seems very similar to what's described here for the Thinkpad E485/E585: https://evilazrael.de/node/401 I'll attach screenshots of various times I've encountered this bug over the last year. $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy linux-image-4.15.0-42-generic linux-image-4.15.0-42-generic: Installed: 4.15.0-42.45 Candidate: 4.15.0-42.45 Version table: *** 4.15.0-42.45 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bryan 2349 F pulseaudio CurrentDesktop: XFCE Date: Thu Dec 13 15:31:15 2018 HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac InstallationDate: Installed on 2014-05-08 (1680 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 3351CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago) dmi.bios.date: 06/01/2018 dmi.bios.vendor: LENOVO dmi.bios.version: H6ETA0WW (2.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 3351CTO dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430u dmi.product.name: 3351CTO dmi.product.version: ThinkPad T430u dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804589] Re: AMD-Vi write error
It’d be great if Canonical also used their Dell and AMD contacts to get this 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/1804589 Title: AMD-Vi write error Status in linux package in Ubuntu: Confirmed Bug description: AMD-Vi write error. [0.777408] AMD-Vi: Unable to write to IOMMU perf counter. [0.777529] pci :00:00.2: can't derive routing for PCI INT A [0.777530] pci :00:00.2: PCI INT A: not connected [0.778000] iommu: Adding device :00:01.0 to group 0 [0.778231] iommu: Adding device :00:01.2 to group 1 [0.778463] iommu: Adding device :00:01.6 to group 2 [0.778690] iommu: Adding device :00:08.0 to group 3 [0.778914] iommu: Adding device :00:08.1 to group 4 [0.778940] iommu: Adding device :00:08.2 to group 3 [0.779154] iommu: Adding device :00:14.0 to group 5 [0.779176] iommu: Adding device :00:14.3 to group 5 [0.779444] iommu: Adding device :00:18.0 to group 6 [0.779474] iommu: Adding device :00:18.1 to group 6 [0.779495] iommu: Adding device :00:18.2 to group 6 [0.779516] iommu: Adding device :00:18.3 to group 6 [0.779544] iommu: Adding device :00:18.4 to group 6 [0.779566] iommu: Adding device :00:18.5 to group 6 [0.779586] iommu: Adding device :00:18.6 to group 6 [0.779606] iommu: Adding device :00:18.7 to group 6 [0.779835] iommu: Adding device :15:00.0 to group 7 [0.779869] iommu: Adding device :15:00.1 to group 7 [0.779903] iommu: Adding device :15:00.2 to group 7 [0.779933] iommu: Adding device :16:04.0 to group 7 [0.779956] iommu: Adding device :16:05.0 to group 7 [0.779977] iommu: Adding device :16:06.0 to group 7 [0.77] iommu: Adding device :16:07.0 to group 7 [0.780031] iommu: Adding device :1b:00.0 to group 7 [0.780058] iommu: Adding device :1c:00.0 to group 7 [0.780296] iommu: Adding device :2e:00.0 to group 8 [0.780592] iommu: Adding device :38:00.0 to group 9 [0.780672] iommu: Using direct mapping for device :38:00.0 [0.780767] iommu: Adding device :38:00.1 to group 10 [0.780807] iommu: Adding device :38:00.2 to group 10 [0.780847] iommu: Adding device :38:00.3 to group 10 [0.780887] iommu: Adding device :38:00.4 to group 10 [0.780934] iommu: Adding device :38:00.6 to group 10 [0.780965] iommu: Adding device :39:00.0 to group 3 [0.781307] AMD-Vi: Found IOMMU at :00:00.2 cap 0x40 [0.781308] AMD-Vi: Extended features (0x4f77ef22294ada): [0.781308] PPR NX GT IA GA PC GA_vAPIC [0.781311] AMD-Vi: Interrupt remapping enabled [0.781311] AMD-Vi: virtual APIC enabled [0.781534] AMD-Vi: Lazy IO/TLB flushing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804589] Re: AMD-Vi write error
I am also seeing this with current Linux (5.7-rc7) on an MSI B350M MORTAR and a Dell OptiPlex 5055. Both are AMD Ryzen systems, so this seems to affect all of those. The IOMMU subsystem maintainer responded to report this issue to the mainboard vendor, so they fix the firmware [1]. Everybody experiencing this, please contact the mainboard vendor to fix this. I already did, and the more contact them, the higher it will rise in their ticketing system. [1]: https://lists.linuxfoundation.org/pipermail/iommu/2018-July/028925.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/1804589 Title: AMD-Vi write error Status in linux package in Ubuntu: Confirmed Bug description: AMD-Vi write error. [0.777408] AMD-Vi: Unable to write to IOMMU perf counter. [0.777529] pci :00:00.2: can't derive routing for PCI INT A [0.777530] pci :00:00.2: PCI INT A: not connected [0.778000] iommu: Adding device :00:01.0 to group 0 [0.778231] iommu: Adding device :00:01.2 to group 1 [0.778463] iommu: Adding device :00:01.6 to group 2 [0.778690] iommu: Adding device :00:08.0 to group 3 [0.778914] iommu: Adding device :00:08.1 to group 4 [0.778940] iommu: Adding device :00:08.2 to group 3 [0.779154] iommu: Adding device :00:14.0 to group 5 [0.779176] iommu: Adding device :00:14.3 to group 5 [0.779444] iommu: Adding device :00:18.0 to group 6 [0.779474] iommu: Adding device :00:18.1 to group 6 [0.779495] iommu: Adding device :00:18.2 to group 6 [0.779516] iommu: Adding device :00:18.3 to group 6 [0.779544] iommu: Adding device :00:18.4 to group 6 [0.779566] iommu: Adding device :00:18.5 to group 6 [0.779586] iommu: Adding device :00:18.6 to group 6 [0.779606] iommu: Adding device :00:18.7 to group 6 [0.779835] iommu: Adding device :15:00.0 to group 7 [0.779869] iommu: Adding device :15:00.1 to group 7 [0.779903] iommu: Adding device :15:00.2 to group 7 [0.779933] iommu: Adding device :16:04.0 to group 7 [0.779956] iommu: Adding device :16:05.0 to group 7 [0.779977] iommu: Adding device :16:06.0 to group 7 [0.77] iommu: Adding device :16:07.0 to group 7 [0.780031] iommu: Adding device :1b:00.0 to group 7 [0.780058] iommu: Adding device :1c:00.0 to group 7 [0.780296] iommu: Adding device :2e:00.0 to group 8 [0.780592] iommu: Adding device :38:00.0 to group 9 [0.780672] iommu: Using direct mapping for device :38:00.0 [0.780767] iommu: Adding device :38:00.1 to group 10 [0.780807] iommu: Adding device :38:00.2 to group 10 [0.780847] iommu: Adding device :38:00.3 to group 10 [0.780887] iommu: Adding device :38:00.4 to group 10 [0.780934] iommu: Adding device :38:00.6 to group 10 [0.780965] iommu: Adding device :39:00.0 to group 3 [0.781307] AMD-Vi: Found IOMMU at :00:00.2 cap 0x40 [0.781308] AMD-Vi: Extended features (0x4f77ef22294ada): [0.781308] PPR NX GT IA GA PC GA_vAPIC [0.781311] AMD-Vi: Interrupt remapping enabled [0.781311] AMD-Vi: virtual APIC enabled [0.781534] AMD-Vi: Lazy IO/TLB flushing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881072] Re: "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed
** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1881072 Title: "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Bionic: New Bug description: Issue found on 4.15.0-1061-kvm, with KVM instance zeppo, moe. The ubuntu_kvm_smoke_test will fail with: uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:ee:15:c8. Traces can be found in syslog. systemd[1]: Started Daemon for generating UUIDs. kernel: kauditd_printk_skb: 9 callbacks suppressed kernel: audit: type=1400 audit(1590647581.375:20): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1291 comm="apparmor_parser" kernel: audit: type=1400 audit(1590647581.691:21): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1294 comm="apparmor_parser" kernel: audit: type=1400 audit(1590647581.927:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1297 comm="apparmor_parser" kernel: audit: type=1400 audit(1590647582.155:23): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1300 comm="apparmor_parser" systemd[1]: Started Virtual machine log manager. libvirtd[693]: 2020-05-28 06:33:02.188+: 731: info : libvirt version: 4.0.0, package: 1ubuntu8.17 (Marc Deslauriers Wed, 06 May 2020 14:18:23 -0400) systemd-networkd[613]: vnet0: Link UP systemd-networkd[613]: vnet0: Gained carrier networkd-dispatcher[662]: WARNING:Unknown index 7 seen, reloading interface list kernel: virbr0: port 2(vnet0) entered blocking state kernel: virbr0: port 2(vnet0) entered disabled state kernel: device vnet0 entered promiscuous mode kernel: virbr0: port 2(vnet0) entered blocking state kernel: virbr0: port 2(vnet0) entered listening state systemd-timesyncd[542]: Network configuration changed, trying to establish connection. systemd-timesyncd[542]: Synchronized to time server 10.246.72.3:123 (10.246.72.3). libvirtd[693]: 2020-05-28 06:33:02.188+: 731: info : hostname: zeppo libvirtd[693]: 2020-05-28 06:33:02.188+: 731: warning : qemuInterfaceOpenVhostNet:687 : Unable to open vhost-net. Opened so far 0, requested 1 systemd-udevd[1306]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. dnsmasq[911]: reading /etc/resolv.conf dnsmasq[911]: using nameserver 127.0.0.53#53 systemd-timesyncd[542]: Network configuration changed, trying to establish connection. systemd-timesyncd[542]: Synchronized to time server 10.246.72.3:123 (10.246.72.3). dnsmasq[911]: reading /etc/resolv.conf dnsmasq[911]: using nameserver 127.0.0.53#53 kernel: audit: type=1400 audit(1590647582.424:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-2c239120-7dc0-4e83-8c24-1eb5a3081877" pid=1316 comm="apparmor_parser" kernel: BUG: unable to handle kernel paging request at 56b8 kernel: IP: 0xc01efb02 kernel: PGD 0 P4D 0 kernel: Oops: [#1] SMP PTI kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_filter ip6_tables iptable_filter loop fuse kvm_intel ip_tables x_tables btrfs xor zstd_decompress zstd_compress xxhash lzo_compress raid6_pq pata_acpi kernel: CPU: 1 PID: 1323 Comm: CPU 0/KVM Not tainted 4.15.0-1061-kvm #62-Ubuntu kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 kernel: RIP: 0010:0xc01efb02 kernel: RSP: 0018:ade780fcbcb0 EFLAGS: 00010002 kernel: RAX: 0001 RBX: RCX: kernel: RDX: 6c14 RSI: RDI: kernel: RBP: ade780fcbcb0 R08: R09: kernel: R10: R11: R12: kernel: R13: R14: R15: kernel: FS: 7f6ab9c34700() GS:938c7fd0() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 56b8 CR3: 000138aac000 CR4: 26a0 kernel: Call Trace: kernel: 0xc01f0205 kernel: 0xba031ee1 kernel: 0xba039
[Kernel-packages] [Bug 1804589] Re: AMD-Vi write error
Just a note, on the Dell OptiPlex 5055 Ryzen CPU/0P03DX, BIOS 1.1.20 05/31/2019 (AGESA SummitPI-AM4 1.0.0.7a) I am only seeing the interrupt warning. Performance counters are supported there. [0.870894] pci :00:00.2: AMD-Vi: IOMMU performance counters supported [0.871377] pci :00:00.2: can't derive routing for PCI INT A [0.871732] pci :00:00.2: PCI INT A: not connected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804589 Title: AMD-Vi write error Status in linux package in Ubuntu: Confirmed Bug description: AMD-Vi write error. [0.777408] AMD-Vi: Unable to write to IOMMU perf counter. [0.777529] pci :00:00.2: can't derive routing for PCI INT A [0.777530] pci :00:00.2: PCI INT A: not connected [0.778000] iommu: Adding device :00:01.0 to group 0 [0.778231] iommu: Adding device :00:01.2 to group 1 [0.778463] iommu: Adding device :00:01.6 to group 2 [0.778690] iommu: Adding device :00:08.0 to group 3 [0.778914] iommu: Adding device :00:08.1 to group 4 [0.778940] iommu: Adding device :00:08.2 to group 3 [0.779154] iommu: Adding device :00:14.0 to group 5 [0.779176] iommu: Adding device :00:14.3 to group 5 [0.779444] iommu: Adding device :00:18.0 to group 6 [0.779474] iommu: Adding device :00:18.1 to group 6 [0.779495] iommu: Adding device :00:18.2 to group 6 [0.779516] iommu: Adding device :00:18.3 to group 6 [0.779544] iommu: Adding device :00:18.4 to group 6 [0.779566] iommu: Adding device :00:18.5 to group 6 [0.779586] iommu: Adding device :00:18.6 to group 6 [0.779606] iommu: Adding device :00:18.7 to group 6 [0.779835] iommu: Adding device :15:00.0 to group 7 [0.779869] iommu: Adding device :15:00.1 to group 7 [0.779903] iommu: Adding device :15:00.2 to group 7 [0.779933] iommu: Adding device :16:04.0 to group 7 [0.779956] iommu: Adding device :16:05.0 to group 7 [0.779977] iommu: Adding device :16:06.0 to group 7 [0.77] iommu: Adding device :16:07.0 to group 7 [0.780031] iommu: Adding device :1b:00.0 to group 7 [0.780058] iommu: Adding device :1c:00.0 to group 7 [0.780296] iommu: Adding device :2e:00.0 to group 8 [0.780592] iommu: Adding device :38:00.0 to group 9 [0.780672] iommu: Using direct mapping for device :38:00.0 [0.780767] iommu: Adding device :38:00.1 to group 10 [0.780807] iommu: Adding device :38:00.2 to group 10 [0.780847] iommu: Adding device :38:00.3 to group 10 [0.780887] iommu: Adding device :38:00.4 to group 10 [0.780934] iommu: Adding device :38:00.6 to group 10 [0.780965] iommu: Adding device :39:00.0 to group 3 [0.781307] AMD-Vi: Found IOMMU at :00:00.2 cap 0x40 [0.781308] AMD-Vi: Extended features (0x4f77ef22294ada): [0.781308] PPR NX GT IA GA PC GA_vAPIC [0.781311] AMD-Vi: Interrupt remapping enabled [0.781311] AMD-Vi: virtual APIC enabled [0.781534] AMD-Vi: Lazy IO/TLB flushing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880834] Re: qeth: utilize virtual MAC for Layer2 OSD devices
Kernel SRU request submitted: https://lists.ubuntu.com/archives/kernel-team/2020-May/thread.html#110417 Updating status to 'In Progress'. ** Description changed: + SRU Justification: + == + + [Impact] + + * A qeth device on a DPM-managed (HMC) IBM Z machine does not obtain its + MAC address for layer2 OSD interfaces from the OSA Network Adapter, + instead it uses a random MAC address. + + * This can cause connectivity issues in environments where reliable and + pre-determined MAC addresses are required, ie. when doing network + configuration based on DHCP. + + [Fix] + + * Backport 1: https://launchpadlibrarian.net/481647649/0001-s390-qeth- + improve-fallback-to-random-MAC-address.patch + + * Backport 2: https://launchpadlibrarian.net/481647657/0002-s390-qeth- + utilize-virtual-MAC-for-Layer2-OSD-devices.patch + + [Test Case] + + * Bring up a qeth L2 OSD interface in DPM-managed (HMC) LPAR + + * Inspect the interface's MAC address. It should be the same as + displayed in the HMC DPM panels. + + * Due to the fact that a system is needed where the HMC is in DPM moce + (rather than in classic mode) this needs to be tested by IBM. + + [Regression Potential] + + * There is a certain risk for a regression, since OSA devices are the + standard netweork devices on s390x. + + * But static network configurations are still more popular for the + usually long running workload on s390x and not dynamic assignments. + + * On the other hand qeth devices are s390x only, so this will at least + not affect common code or code for other architectures. + + * The modifications are limited to drivers/s390/net/qeth_*. + + * The patches are upstream since quite a while, which speaks for their + stability. + + [Other Info] + + * The upstream patch 21b1702af12e "s390/qeth: improve fallback to random + MAC address" got upstream accepted with 4.18, hence is already in all + Ubuntu release that are newer than bionic + + * And the upstream patch b144b99fff69 "s390/qeth: utilize virtual MAC + for Layer2 OSD devices" got upstream accepted with 5.0, hence is also + already in all Ubuntu release that are newer than bionic. + + __ + ---Problem Description--- qeth on a DPM-managed IBM Z machine does not obtain its MAC Address for L2 OSD interfaces from the OSA Network Adapter. Instead it uses a random MAC Address. - This causes connectivity issues in setups where a reliable & pre-determined MAC Address is required - ie. when doing network configuration via DHCP. - + This causes connectivity issues in setups where a reliable & pre- + determined MAC Address is required - ie. when doing network + configuration via DHCP. + ---uname output--- Ubuntu 18.04 / vmlinuz-4.15.0-101-generic - - Machine Type = IBM z14 GA2 - + + Machine Type = IBM z14 GA2 + ---Debugger--- A debugger is not configured - + ---Steps to Reproduce--- - - Bring up a qeth L2 OSD interface in DPM-managed LPAR. + - Bring up a qeth L2 OSD interface in DPM-managed LPAR. - Inspect the interface's MAC Address. It should be the same as displayed in the DPM Panels. - + Stack trace output: - no - + no + Oops output: - no - + no + System Dump Info: - The system is not configured to capture a system dump. - + The system is not configured to capture a system dump. + -Attach sysctl -a output output to the bug. - Backport of "s390/qeth: improve fallback to random MAC address" - Backport of "s390/qeth: utilize virtual MAC for Layer2 OSD devices" - This ticket is for 18.04 only. Already available with 20.04 ** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: ubuntu-z-systems Status: Triaged => 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/1880834 Title: qeth: utilize virtual MAC for Layer2 OSD devices Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: == [Impact] * A qeth device on a DPM-managed (HMC) IBM Z machine does not obtain its MAC address for layer2 OSD interfaces from the OSA Network Adapter, instead it uses a random MAC address. * This can cause connectivity issues in environments where reliable and pre-determined MAC addresses are required, ie. when doing network configuration based on DHCP. [Fix] * Backport 1: https://launchpadlibrarian.net/481647649/0001-s390-qeth- improve-fallback-to-random-MAC-address.patch * Backport 2: https://launchpadlibrarian.net/481647657/0002-s390-qeth- utilize-virtual-MAC-for-Layer2-OSD-devices.patch [Test Case] * Bring up a qeth L2 OSD interface in DPM-managed (HMC) LPAR * Inspect the interface's MAC address. It should be the same as displayed in the HMC DPM panels. * Due to the fact that a system is needed where the H
[Kernel-packages] [Bug 1881124] [NEW] I2C bus on Dell Edge Gateway stops working after upgrading to Ubuntu-4.4.0-180.210
Public bug reported: I2C stops working after kernel upgrade: [ 13.812210] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x [ 13.855837] i2c_designware 80860F41:01: timeout in enabling adapter [ 14.856276] i2c_designware 80860F41:01: controller timed out [ 14.856288] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x This is caused by the commit commit 5568c3f29fbd0ec0d9bb0f805bacc5755180c5cb Author: Andy Shevchenko Date: Fri Dec 4 23:49:18 2015 +0200 Revert "ACPI / LPSS: allow to use specific PM domain during ->probe()" BugLink: https://bugs.launchpad.net/bugs/1878232 commit b5f88dd1d6efc472e35ca1b21a44e662c5422088 upstream. The specific power domain can't be used in a way provided by the commit 01ac170ba29a, i.e. pointer to platform device is a subject to change during unbound / bind cycle. This reverts commit 01ac170ba29a9903ee590e1ef2d8e6b27b49a16c. Fixes: 3df2da968744 (Revert "ACPI / LPSS: introduce a 'proxy' device to power on LPSS for DMA") Signed-off-by: Andy Shevchenko Signed-off-by: Rafael J. Wysocki Signed-off-by: Greg Kroah-Hartman Signed-off-by: Ian May Signed-off-by: Kleber Sacilotto de Souza ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: Confirmed ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Jesse Sung (wenchien) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881124 Title: I2C bus on Dell Edge Gateway stops working after upgrading to Ubuntu-4.4.0-180.210 Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: I2C stops working after kernel upgrade: [ 13.812210] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x [ 13.855837] i2c_designware 80860F41:01: timeout in enabling adapter [ 14.856276] i2c_designware 80860F41:01: controller timed out [ 14.856288] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x This is caused by the commit commit 5568c3f29fbd0ec0d9bb0f805bacc5755180c5cb Author: Andy Shevchenko Date: Fri Dec 4 23:49:18 2015 +0200 Revert "ACPI / LPSS: allow to use specific PM domain during ->probe()" BugLink: https://bugs.launchpad.net/bugs/1878232 commit b5f88dd1d6efc472e35ca1b21a44e662c5422088 upstream. The specific power domain can't be used in a way provided by the commit 01ac170ba29a, i.e. pointer to platform device is a subject to change during unbound / bind cycle. This reverts commit 01ac170ba29a9903ee590e1ef2d8e6b27b49a16c. Fixes: 3df2da968744 (Revert "ACPI / LPSS: introduce a 'proxy' device to power on LPSS for DMA") Signed-off-by: Andy Shevchenko Signed-off-by: Rafael J. Wysocki Signed-off-by: Greg Kroah-Hartman Signed-off-by: Ian May Signed-off-by: Kleber Sacilotto de Souza To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866484] Re: focal/linux-azure: 5.4.0-1006.6 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1866484
Title:
focal/linux-azure: 5.4.0-1006.6 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-release series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
Invalid
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Focal:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1866488
packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
phase: Complete
phase-changed: Friday, 20. March 2020 21:56 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1866484/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865482] Re: eoan/linux-aws: 5.3.0-1013.14 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1865482
Title:
eoan/linux-aws: 5.3.0-1013.14 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-aws package in Ubuntu:
Invalid
Status in linux-aws source package in Eoan:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865111
packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
phase: Complete
phase-changed: Tuesday, 17. March 2020 11:55 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
bionic/linux-aws-5.3: bug 1865481
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865482/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865419] Re: bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1865419
Title:
bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Invalid
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Invalid
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865269
packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
phase: Complete
phase-changed: Monday, 16. March 2020 11:37 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865419/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865480] Re: bionic/linux-oracle: 4.15.0-1035.39 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1865480
Title:
bionic/linux-oracle: 4.15.0-1035.39 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-oracle package in Ubuntu:
Fix Released
Status in linux-oracle source package in Bionic:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865109
packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
phase: Complete
phase-changed: Tuesday, 17. March 2020 21:17 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
xenial/linux-oracle: bug 1865479
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865480/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865479] Re: xenial/linux-oracle: 4.15.0-1035.38~16.04.1 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1865479
Title:
xenial/linux-oracle: 4.15.0-1035.38~16.04.1 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-oracle package in Ubuntu:
Invalid
Status in linux-oracle source package in Xenial:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865480
packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
phase: Complete
phase-changed: Tuesday, 17. March 2020 21:27 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865479/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865438] Re: eoan/linux-kvm: 5.3.0-1012.13 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
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/1865438
Title:
eoan/linux-kvm: 5.3.0-1012.13 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-kvm package in Ubuntu:
Invalid
Status in linux-kvm source package in Eoan:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865111
packages:
main: linux-kvm
meta: linux-meta-kvm
phase: Complete
phase-changed: Tuesday, 17. March 2020 11:55 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865438/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865269] Re: bionic/linux-aws: 4.15.0-1063.67 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1865269
Title:
bionic/linux-aws: 4.15.0-1063.67 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-aws package in Ubuntu:
Invalid
Status in linux-aws source package in Bionic:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865109
packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
phase: Complete
phase-changed: Tuesday, 17. March 2020 12:09 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
bionic/linux-aws-fips: bug 1865419
bionic/linux-aws/aws-kernel: bug 1865268
xenial/linux-aws-hwe: bug 1865421
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865269/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865199] Re: xenial/linux-fips: 4.4.0-1031.36 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1865199
Title:
xenial/linux-fips: 4.4.0-1031.36 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Invalid
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Invalid
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865106
packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
phase: Complete
phase-changed: Monday, 16. March 2020 15:16 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865199/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865201] Re: bionic/linux-ibm-gt: 4.15.0-1051.57 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1865201
Title:
bionic/linux-ibm-gt: 4.15.0-1051.57 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Invalid
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Invalid
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865109
packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
phase: Complete
phase-changed: Monday, 16. March 2020 11:30 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865201/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865251] Re: xenial/linux-gcp: 4.15.0-1058.62 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
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/1865251
Title:
xenial/linux-gcp: 4.15.0-1058.62 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-gcp package in Ubuntu:
Invalid
Status in linux-gcp source package in Xenial:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865109
packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
phase: Complete
phase-changed: Tuesday, 17. March 2020 12:31 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
xenial/linux-gcp/gcp-kernel: bug 1865249
xenial/linux-gcp/gke-kernel: bug 1865250
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865251/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1865197
Title:
trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Invalid
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-azure package in Ubuntu:
Invalid
Status in linux-azure source package in Trusty:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1867860
packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
phase: Complete
phase-changed: Monday, 23. March 2020 21:49 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865197/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804591] Re: tsc: Fast TSC calibration failed
This is a common problem on AMD Zen systems. Patches were posted to LKML (Linux Kernel Mailing List) in February 2019, but version 2 still needs to rewrite a comment, and v3 wasn’t posted since then. [1]: https://lkml.org/lkml/2019/2/14/1145 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804591 Title: tsc: Fast TSC calibration failed Status in linux package in Ubuntu: Confirmed Bug description: [0.00] APIC: Switch to symmetric I/O mode setup [0.004000] Switched APIC routing to physical flat. [0.004000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [0.024000] tsc: Fast TSC calibration failed [0.032000] tsc: PIT calibration matches HPET. 1 loops [0.032000] tsc: Detected 3600.039 MHz processor [0.032000] clocksource: tsc-early: mask: 0x max_cycles: 0x33e47874cac, max_idle_ns: 440795311274 ns [0.032000] Calibrating delay loop (skipped), value calculated using timer frequency.. 7200.07 BogoMIPS (lpj=14400156) [0.032000] pid_max: default: 32768 minimum: 301 [0.032000] Security Framework initialized [0.032000] Yama: becoming mindful. [0.032000] AppArmor: AppArmor initialized --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: 1438 F pulseaudio /dev/snd/controlC0: 1438 F pulseaudio CurrentDesktop: LXQt DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-22 (2 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Micro-Star International Co., Ltd. MS-7A39 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=x ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 09/28/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.I0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M GAMING PRO (MS-7A39) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.I0:bd09/28/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A39:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MGAMINGPRO(MS-7A39):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A39 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865245] Re: xenial/linux-aws: 4.4.0-1104.115 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1865245
Title:
xenial/linux-aws: 4.4.0-1104.115 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-aws package in Ubuntu:
Invalid
Status in linux-aws source package in Xenial:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865106
packages:
main: linux-aws
meta: linux-meta-aws
phase: Complete
phase-changed: Tuesday, 17. March 2020 12:28 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
xenial/linux-aws/aws-kernel: bug 1865244
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865245/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865247] Re: bionic/linux-kvm: 4.15.0-1056.57 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
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/1865247
Title:
bionic/linux-kvm: 4.15.0-1056.57 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-kvm package in Ubuntu:
Invalid
Status in linux-kvm source package in Bionic:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865109
packages:
main: linux-kvm
meta: linux-meta-kvm
phase: Complete
phase-changed: Tuesday, 17. March 2020 11:51 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865247/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865495] Re: xenial/linux-deeplens: 4.15.0-1019.19 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1865495
Title:
xenial/linux-deeplens: 4.15.0-1019.19 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Fix Released
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Invalid
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Invalid
Status in Kernel SRU Workflow security-signoff series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Invalid
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865142
packages:
main: linux-deeplens
meta: linux-meta-deeplens
phase: Complete
phase-changed: Monday, 16. March 2020 15:52 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865495/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865246] Re: trusty/linux-aws: 4.4.0-1064.68 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1865246
Title:
trusty/linux-aws: 4.4.0-1064.68 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Invalid
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-aws package in Ubuntu:
Invalid
Status in linux-aws source package in Trusty:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865106
packages:
main: linux-aws
meta: linux-meta-aws
phase: Complete
phase-changed: Monday, 16. March 2020 16:15 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865246/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865493] Re: eoan/linux-oracle: 5.3.0-1011.12 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1865493
Title:
eoan/linux-oracle: 5.3.0-1011.12 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-oracle package in Ubuntu:
Invalid
Status in linux-oracle source package in Eoan:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865111
packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
phase: Complete
phase-changed: Tuesday, 17. March 2020 11:56 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
bionic/linux-oracle-5.3: bug 1865492
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865493/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865106] Re: xenial/linux: 4.4.0-176.206 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1865106
Title:
xenial/linux: 4.4.0-176.206 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Fix Released
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
bugs-spammed: true
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Complete
phase-changed: Tuesday, 17. March 2020 12:24 UTC
reason: {}
trackers:
trusty/linux-aws: bug 1865246
trusty/linux-lts-xenial: bug 1865143
xenial/linux-aws: bug 1865245
xenial/linux-cascade: bug 1863314
xenial/linux-fips: bug 1865199
xenial/linux-kvm: bug 1865243
xenial/linux-raspi2: bug 1863324
xenial/linux-snapdragon: bug 1863329
xenial/linux/caracalla-kernel: bug 1865103
xenial/linux/pc-kernel: bug 1865104
xenial/linux/stlouis-kernel: bug 1865105
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865106/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864726] Re: bionic/linux-raspi2: 4.15.0-1057.61 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1864726
Title:
bionic/linux-raspi2: 4.15.0-1057.61 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Fix Released
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Invalid
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-raspi2 package in Ubuntu:
Invalid
Status in linux-raspi2 source package in Bionic:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865109
packages:
main: linux-raspi2
meta: linux-meta-raspi2
phase: Complete
phase-changed: Tuesday, 17. March 2020 11:49 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
bionic/linux-raspi2/pi-kernel: bug 1864725
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864726/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864729] Re: bionic/linux-snapdragon: 4.15.0-1074.81 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-snapdragon in Ubuntu.
https://bugs.launchpad.net/bugs/1864729
Title:
bionic/linux-snapdragon: 4.15.0-1074.81 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Fix Released
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Invalid
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-snapdragon package in Ubuntu:
Invalid
Status in linux-snapdragon source package in Bionic:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865109
packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
phase: Complete
phase-changed: Tuesday, 17. March 2020 11:49 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1864727
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864729/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865491] Re: eoan/linux-gcp: 5.3.0-1014.15 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
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/1865491
Title:
eoan/linux-gcp: 5.3.0-1014.15 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-gcp package in Ubuntu:
Invalid
Status in linux-gcp source package in Eoan:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865111
packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
phase: Complete
phase-changed: Tuesday, 17. March 2020 11:56 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
bionic/linux-gcp-5.3: bug 1865488
bionic/linux-gke-5.3: bug 1865490
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865491/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865431] Re: bionic/linux-gcp: 5.0.0-1033.34 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
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/1865431
Title:
bionic/linux-gcp: 5.0.0-1033.34 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Invalid
Status in linux-gcp package in Ubuntu:
Invalid
Status in linux-gcp source package in Bionic:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865110
packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
phase: Complete
phase-changed: Tuesday, 17. March 2020 12:34 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
bionic/linux-gcp/gcp-kernel: bug 1865430
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865431/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861294] Re: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu
@alberto-pretto: any news? My wife's Lenovo with Intel GPU started to freeze from time to time... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861294 Title: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu Status in linux package in Ubuntu: Incomplete Bug description: Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630 (Coffeelake 3x8 GT2). I had chrome, slack and vmware-player running in Gnome. While doing some git clone, screen+mouse+keyboard froze for 2 minutes after which xorg and everything else recovered. I saw this in dmesg: kernel: show_signal_msg: 2 callbacks suppressed kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000] kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller kernel: nvme nvme0: 12/0/0 default/read/poll queues While writing this bug report, the system froze again, and this time it didn't recover. After a cold reset I didn't see any other GpuWatchdog messages in journalctl. Ubuntu applied a BIOS firmware update before the first freeze, so my BIOS was updated as part of the cold reset I did. Not sure if this is relevant to reproducing the freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865203] Re: bionic/linux-fips: 4.15.0-1025.30 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1865203
Title:
bionic/linux-fips: 4.15.0-1025.30 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Invalid
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Invalid
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865109
packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
phase: Complete
phase-changed: Monday, 16. March 2020 11:30 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865203/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865243] Re: xenial/linux-kvm: 4.4.0-1068.75 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
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/1865243
Title:
xenial/linux-kvm: 4.4.0-1068.75 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-kvm package in Ubuntu:
Invalid
Status in linux-kvm source package in Xenial:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865106
packages:
main: linux-kvm
meta: linux-meta-kvm
phase: Complete
phase-changed: Tuesday, 17. March 2020 12:28 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865243/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863329] Re: xenial/linux-snapdragon: 4.4.0-1134.142 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-snapdragon in Ubuntu.
https://bugs.launchpad.net/bugs/1863329
Title:
xenial/linux-snapdragon: 4.4.0-1134.142 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Fix Released
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Invalid
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-snapdragon package in Ubuntu:
Invalid
Status in linux-snapdragon source package in Xenial:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865106
packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
phase: Complete
phase-changed: Tuesday, 17. March 2020 12:28 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1863326
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863269] Re: eoan/linux-raspi2: 5.3.0-1019.21 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1863269
Title:
eoan/linux-raspi2: 5.3.0-1019.21 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Fix Released
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Invalid
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-raspi2 package in Ubuntu:
Invalid
Status in linux-raspi2 source package in Eoan:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865111
packages:
main: linux-raspi2
meta: linux-meta-raspi2
phase: Complete
phase-changed: Tuesday, 17. March 2020 11:55 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
bionic/linux-raspi2-5.3: bug 1863268
eoan/linux-raspi2/pi-kernel: bug 1863266
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863269/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874374] Re: thinkbook 14-iil elan touchpad does not work
*** This bug is a duplicate of bug 1853277 *** https://bugs.launchpad.net/bugs/1853277 ** This bug has been marked a duplicate of bug 1853277 Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874374 Title: thinkbook 14-iil elan touchpad does not work Status in linux package in Ubuntu: Confirmed Bug description: Here is the output of cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=062a Product=4c01 Version=0110 N: Name="MOSART Semi. 2.4G Keyboard Mouse" P: Phys=usb-:00:14.0-4/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.0/0003:062A:4C01.0001/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=062a Product=4c01 Version=0110 N: Name="MOSART Semi. 2.4G Keyboard Mouse" P: Phys=usb-:00:14.0-4/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input6 U: Uniq= H: Handlers=mouse0 event6 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0003 Vendor=062a Product=4c01 Version=0110 N: Name="MOSART Semi. 2.4G Keyboard Mouse Consumer Control" P: Phys=usb-:00:14.0-4/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input7 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=1f B: KEY=3f000301ff 0 0 48317aff32d bfd6 1 130ff38b17c000 677bfad9415fed 19ed6804400 1002 B: REL=1040 B: ABS=1 B: MSC=10 I: Bus=0003 Vendor=062a Product=4c01 Version=0110 N: Name="MOSART Semi. 2.4G Keyboard Mouse System Control" P: Phys=usb-:00:14.0-4/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input8 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=13 B: KEY=c000 10 0 B: MSC=10 I: Bus=0003 Vendor=062a Product=4c01 Version=0110 N: Name="MOSART Semi. 2.4G Keyboard Mouse" P: Phys=usb-:00:14.0-4/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=9 B: ABS=100 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input10 U: Uniq= H: Handlers=rfkill kbd event10 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=04f2 Product=b6d9 Version=2699 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-6/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/input/input11 U: Uniq= H: Handlers=kbd event11 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs
[Kernel-packages] [Bug 1862011] Re: linux-oem: -proposed tracker
** Tags added: kernel-release-tracking-bug-live ** Changed in: linux-oem (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1862011 Title: linux-oem: -proposed tracker Status in Kernel SRU Workflow: New Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861109] Re: xenial/linux-cascade: 4.4.0-1014.16 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1861109
Title:
xenial/linux-cascade: 4.4.0-1014.16 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Invalid
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Invalid
Status in Kernel SRU Workflow security-signoff series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Invalid
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1861122
packages:
main: linux-cascade
meta: linux-meta-cascade
signed: linux-signed-cascade
phase: Complete
phase-changed: Monday, 24. February 2020 16:41 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
xenial/linux-cascade/cascade-kernel: bug 1861108
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861109/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858472] Re: linux-aws: -proposed tracker
** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1858472 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-lrm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858469] Re: linux-raspi2: -proposed tracker
** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1858469 Title: linux-raspi2: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Eoan: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881124] Re: I2C bus on Dell Edge Gateway stops working after upgrading to Ubuntu-4.4.0-180.210
** Tags added: oem-priority originate-from-1880661 plano ** Changed in: hwe-next Status: New => In Progress ** Changed in: hwe-next Assignee: (unassigned) => Jesse Sung (wenchien) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881124 Title: I2C bus on Dell Edge Gateway stops working after upgrading to Ubuntu-4.4.0-180.210 Status in HWE Next: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: I2C stops working after kernel upgrade: [ 13.812210] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x [ 13.855837] i2c_designware 80860F41:01: timeout in enabling adapter [ 14.856276] i2c_designware 80860F41:01: controller timed out [ 14.856288] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x This is caused by the commit commit 5568c3f29fbd0ec0d9bb0f805bacc5755180c5cb Author: Andy Shevchenko Date: Fri Dec 4 23:49:18 2015 +0200 Revert "ACPI / LPSS: allow to use specific PM domain during ->probe()" BugLink: https://bugs.launchpad.net/bugs/1878232 commit b5f88dd1d6efc472e35ca1b21a44e662c5422088 upstream. The specific power domain can't be used in a way provided by the commit 01ac170ba29a, i.e. pointer to platform device is a subject to change during unbound / bind cycle. This reverts commit 01ac170ba29a9903ee590e1ef2d8e6b27b49a16c. Fixes: 3df2da968744 (Revert "ACPI / LPSS: introduce a 'proxy' device to power on LPSS for DMA") Signed-off-by: Andy Shevchenko Signed-off-by: Rafael J. Wysocki Signed-off-by: Greg Kroah-Hartman Signed-off-by: Ian May Signed-off-by: Kleber Sacilotto de Souza To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1881124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
Same problem here Fresh 20.04 install on Lenovo x260 (intel graphics) Kernel 5.4.0-31-generic System boots fine with no HDMI/MDP cables connected but hangs if either are plugged in. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Incomplete Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864871] Re: Failed to init Intel sound card in 20.04
@Hui, > sudo apt-get update; sudo apt install linux-firmware ... linux-firmware is already the newest version (1.187). 0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded. > [ ! -d "/lib/firmware/intel/sof" ] && echo "Directory /path/to/dir DOES NOT > exists." Directory /path/to/dir DOES NOT exists. There is no directory named "sof" in this /lib/firmware/intel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864871 Title: Failed to init Intel sound card in 20.04 Status in linux package in Ubuntu: Confirmed Bug description: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card there is no sound available because sound card not detected (only dummy output available in sound settings): $ alsamixer cannot open mixer: No such file or directory $ lspci -nnk |grep -A2 audio lspci: Unable to load libkmod resources: error -12 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] Subsystem: Lenovo Device [17aa:3816] Kernel driver in use: sof-audio-pci 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:02a3] Subsystem: Lenovo Device [17aa:3819] $ pacmd list-cards 0 card(s) available. $ dmesg |grep sof [0.755398] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [0.755400] software IO TLB: mapped [mem 0x7d91d000-0x8191d000] (64MB) [2.142149] systemd[1]: Mounting Mount unit for software-boutique, revision 54... [2.333772] systemd[1]: Mounted Mount unit for software-boutique, revision 54. [2.770307] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [2.770316] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [2.770473] sof-audio-pci :00:1f.3: use msi interrupt mode [2.770696] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.779359] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [2.779360] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [2.817051] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [2.817054] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [2.817057] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [2.817058] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 I've found similar bug reported here: https://bugs.archlinux.org/task/64720 As a workaround I've added `snd_hda_intel.dmic_detect=0` to boot options and after that sound card successfully detected and started working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 26 19:22:05 2020 InstallationDate: Installed on 2020-02-25 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:0c02 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20RR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=94f1e507-a44a-46a8-9163-548d27303afb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 SourcePackage: linux-5.4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CQCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IML dmi.modalias: dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML: dmi.product.family: ThinkBook 13s-IML dmi.product.name: 20RR dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML dmi.product.version: Lenovo ThinkBook 13s-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpa
[Kernel-packages] [Bug 1858851] Re: focal/linux-oem-5.4: -proposed tracker
** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1858851 Title: focal/linux-oem-5.4: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-release series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-oem-5.4 package in Ubuntu: Invalid Status in linux-oem-5.4 source package in Focal: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1858856 packages: lrm: linux-restricted-modules-oem-5.4 main: linux-oem-5.4 meta: linux-meta-oem-5.4 signed: linux-signed-oem-5.4 phase: Holding before Packaging phase-changed: Wednesday, 08. January 2020 20:01 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858851/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881134] [NEW] amdgpu crashes in mode_support_and_system_configuration
Public bug reported: When switching window from gnome-terminal to firefox, the amdgpu kernel driver suddenly crashed. This caused screen to freeze completely, but ssh to the machine still worked ok. There is a similar bug filed in https://bugzilla.kernel.org/show_bug.cgi?id=206987 but not much activity. I'm not sure if there is an amdgpu specific bugtracker somewhere. Below is a decoded call trace and I've attached the full dmesg output. [455834.384976] simd exception: [#1] SMP NOPTI [455834.384980] CPU: 1 PID: 2411 Comm: Xorg Tainted: GW OE 5.4.0-31-generic #35-Ubuntu ... [455834.385061] Call Trace: [455834.385120] mode_support_and_system_configuration (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calc_auto.c:176) amdgpu [455834.385174] ? calculate_inits_and_adj_vp (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:950 (discriminator 12)) amdgpu [455834.385230] dcn_validate_bandwidth (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.c:1034) amdgpu [455834.385283] dc_validate_global_state (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:2093) amdgpu [455834.385338] amdgpu_dm_atomic_check (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:7413) amdgpu [455834.385351] drm_atomic_check_only (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_atomic.c:1179) drm [455834.385361] drm_atomic_commit (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_atomic.c:1220) drm [455834.385370] drm_mode_obj_set_property_ioctl (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_mode_object.c:496 /build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_mode_object.c:533) drm [455834.385379] ? drm_mode_obj_find_prop_id (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_mode_object.c:512) drm [455834.385386] drm_ioctl_kernel (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_ioctl.c:793) drm [455834.385394] drm_ioctl (/build/linux-FFoizL/linux-5.4.0/include/linux/thread_info.h:119 /build/linux-FFoizL/linux-5.4.0/include/linux/thread_info.h:152 /build/linux-FFoizL/linux-5.4.0/include/linux/uaccess.h:151 /build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_ioctl.c:888) drm [455834.385402] ? drm_mode_obj_find_prop_id (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_mode_object.c:512) drm [455834.385406] ? recalc_sigpending (/build/linux-FFoizL/linux-5.4.0/kernel/signal.c:184) [455834.385440] amdgpu_drm_ioctl (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c:1293) amdgpu [455834.385443] do_vfs_ioctl (/build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:47 /build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:510 /build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:697) [455834.385444] ? recalc_sigpending (/build/linux-FFoizL/linux-5.4.0/kernel/signal.c:184) [455834.385446] ? _copy_from_user (/build/linux-FFoizL/linux-5.4.0/arch/x86/include/asm/uaccess_64.h:46 /build/linux-FFoizL/linux-5.4.0/arch/x86/include/asm/uaccess_64.h:71 /build/linux-FFoizL/linux-5.4.0/lib/usercopy.c:14) [455834.385448] ksys_ioctl (/build/linux-FFoizL/linux-5.4.0/include/linux/file.h:43 /build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:715) [455834.385449] __x64_sys_ioctl (/build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:719) [455834.385451] do_syscall_64 (/build/linux-FFoizL/linux-5.4.0/arch/x86/entry/common.c:290) [455834.385455] entry_SYSCALL_64_after_hwframe (/build/linux-FFoizL/linux-5.4.0/arch/x86/entry/entry_64.S:184) [455834.385456] RIP: 0033:0x7faf3181837b ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: petteri1198 F pulseaudio /dev/snd/controlC0: petteri1198 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ICEWM Date: Thu May 28 17:09:28 2020 InstallationDate: Installed on 2020-05-20 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-31-generic root=UUID=81e6e5d0-6a69-412b-8f6c-d6d765ae32de ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dm
[Kernel-packages] [Bug 1879630] Re: No sound output from HDMI audio
** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- 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/1879630 Title: No sound output from HDMI audio Status in snapd: New Status in linux-raspi package in Ubuntu: New Bug description: There is no sound output from HDMI audio. System: Intel NUC7CJYH Image: 20200519.2 Steps to reproduce: 1. $ sudo snap install alsa-utils 2. $ sudo amixer set Master 100 unmute 3. $ sudo amixer set IEC958 100 unmute 4. $ sudo speaker-test -c2 There is no sound output from HDMI audio. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1879630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858856] Re: focal/linux: -proposed tracker
** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858856 Title: focal/linux: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-release series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Packaging phase-changed: Wednesday, 08. January 2020 20:02 UTC reason: prepare-package: Pending -- version not specified trackers: focal/linux-oem-5.4: bug 1858851 focal/linux/pc-kernel: bug 1858849, bug 1858852, bug 1858854 focal/linux/pc-lowlatency-kernel: bug 1858853, bug 1858850, bug 1858855 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861109] Re: xenial/linux-cascade: 4.4.0-1014.16 -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1861122
packages:
main: linux-cascade
meta: linux-meta-cascade
signed: linux-signed-cascade
phase: Complete
phase-changed: Monday, 24. February 2020 16:41 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
+ reason: {}
trackers:
xenial/linux-cascade/cascade-kernel: bug 1861108
variant: debs
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1861109
Title:
xenial/linux-cascade: 4.4.0-1014.16 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Invalid
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Invalid
Status in Kernel SRU Workflow security-signoff series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Invalid
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1861122
packages:
main: linux-cascade
meta: linux-meta-cascade
signed: linux-signed-cascade
phase: Complete
phase-changed: Monday, 24. February 2020 16:41 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
xenial/linux-cascade/cascade-kernel: bug 1861108
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861109/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863314] Re: xenial/linux-cascade: 4.4.0-1015.17 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1863314
Title:
xenial/linux-cascade: 4.4.0-1015.17 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Invalid
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Invalid
Status in Kernel SRU Workflow security-signoff series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Invalid
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865106
packages:
main: linux-cascade
meta: linux-meta-cascade
signed: linux-signed-cascade
phase: Complete
phase-changed: Monday, 16. March 2020 14:51 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
xenial/linux-cascade/cascade-kernel: bug 1863313
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863314/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863324] Re: xenial/linux-raspi2: 4.4.0-1130.139 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1863324
Title:
xenial/linux-raspi2: 4.4.0-1130.139 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Fix Released
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Invalid
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-raspi2 package in Ubuntu:
Invalid
Status in linux-raspi2 source package in Xenial:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1865106
packages:
main: linux-raspi2
meta: linux-meta-raspi2
phase: Complete
phase-changed: Tuesday, 17. March 2020 12:27 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
xenial/linux-raspi2/pi2-kernel: bug 1863322
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863324/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804591] Re: tsc: Fast TSC calibration failed
Thank you Paul for the pointer. I've just sent a ping in that thread..let's see how it goes. Cheers, Guilherme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804591 Title: tsc: Fast TSC calibration failed Status in linux package in Ubuntu: Confirmed Bug description: [0.00] APIC: Switch to symmetric I/O mode setup [0.004000] Switched APIC routing to physical flat. [0.004000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [0.024000] tsc: Fast TSC calibration failed [0.032000] tsc: PIT calibration matches HPET. 1 loops [0.032000] tsc: Detected 3600.039 MHz processor [0.032000] clocksource: tsc-early: mask: 0x max_cycles: 0x33e47874cac, max_idle_ns: 440795311274 ns [0.032000] Calibrating delay loop (skipped), value calculated using timer frequency.. 7200.07 BogoMIPS (lpj=14400156) [0.032000] pid_max: default: 32768 minimum: 301 [0.032000] Security Framework initialized [0.032000] Yama: becoming mindful. [0.032000] AppArmor: AppArmor initialized --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: 1438 F pulseaudio /dev/snd/controlC0: 1438 F pulseaudio CurrentDesktop: LXQt DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-22 (2 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Micro-Star International Co., Ltd. MS-7A39 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=x ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 09/28/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.I0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M GAMING PRO (MS-7A39) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.I0:bd09/28/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A39:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350MGAMINGPRO(MS-7A39):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A39 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881134] 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/1881134 Title: amdgpu crashes in mode_support_and_system_configuration Status in linux package in Ubuntu: Confirmed Bug description: When switching window from gnome-terminal to firefox, the amdgpu kernel driver suddenly crashed. This caused screen to freeze completely, but ssh to the machine still worked ok. There is a similar bug filed in https://bugzilla.kernel.org/show_bug.cgi?id=206987 but not much activity. I'm not sure if there is an amdgpu specific bugtracker somewhere. Below is a decoded call trace and I've attached the full dmesg output. [455834.384976] simd exception: [#1] SMP NOPTI [455834.384980] CPU: 1 PID: 2411 Comm: Xorg Tainted: GW OE 5.4.0-31-generic #35-Ubuntu ... [455834.385061] Call Trace: [455834.385120] mode_support_and_system_configuration (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calc_auto.c:176) amdgpu [455834.385174] ? calculate_inits_and_adj_vp (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:950 (discriminator 12)) amdgpu [455834.385230] dcn_validate_bandwidth (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.c:1034) amdgpu [455834.385283] dc_validate_global_state (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:2093) amdgpu [455834.385338] amdgpu_dm_atomic_check (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:7413) amdgpu [455834.385351] drm_atomic_check_only (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_atomic.c:1179) drm [455834.385361] drm_atomic_commit (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_atomic.c:1220) drm [455834.385370] drm_mode_obj_set_property_ioctl (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_mode_object.c:496 /build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_mode_object.c:533) drm [455834.385379] ? drm_mode_obj_find_prop_id (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_mode_object.c:512) drm [455834.385386] drm_ioctl_kernel (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_ioctl.c:793) drm [455834.385394] drm_ioctl (/build/linux-FFoizL/linux-5.4.0/include/linux/thread_info.h:119 /build/linux-FFoizL/linux-5.4.0/include/linux/thread_info.h:152 /build/linux-FFoizL/linux-5.4.0/include/linux/uaccess.h:151 /build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_ioctl.c:888) drm [455834.385402] ? drm_mode_obj_find_prop_id (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_mode_object.c:512) drm [455834.385406] ? recalc_sigpending (/build/linux-FFoizL/linux-5.4.0/kernel/signal.c:184) [455834.385440] amdgpu_drm_ioctl (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c:1293) amdgpu [455834.385443] do_vfs_ioctl (/build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:47 /build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:510 /build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:697) [455834.385444] ? recalc_sigpending (/build/linux-FFoizL/linux-5.4.0/kernel/signal.c:184) [455834.385446] ? _copy_from_user (/build/linux-FFoizL/linux-5.4.0/arch/x86/include/asm/uaccess_64.h:46 /build/linux-FFoizL/linux-5.4.0/arch/x86/include/asm/uaccess_64.h:71 /build/linux-FFoizL/linux-5.4.0/lib/usercopy.c:14) [455834.385448] ksys_ioctl (/build/linux-FFoizL/linux-5.4.0/include/linux/file.h:43 /build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:715) [455834.385449] __x64_sys_ioctl (/build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:719) [455834.385451] do_syscall_64 (/build/linux-FFoizL/linux-5.4.0/arch/x86/entry/common.c:290) [455834.385455] entry_SYSCALL_64_after_hwframe (/build/linux-FFoizL/linux-5.4.0/arch/x86/entry/entry_64.S:184) [455834.385456] RIP: 0033:0x7faf3181837b ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: petteri1198 F pulseaudio /dev/snd/controlC0: petteri1198 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ICEWM Date: Thu May 28 17:09:28 2020 InstallationDate: Installed on 2020-05-20 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-31-generic root=UUID=81e6e5d0-6a69-412b-8f6c-d6d765ae32de ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-rest
[Kernel-packages] [Bug 1881107] Re: zfs: backport AES-GCM performance accelleration
benchmarked on Haswell Intel 8 thread CPU: Benchmarks: original 15:29:15 INFO | zfs_encryption_aes_128_ccm_wr_rate_mbytes_per_second_average 79.6500 15:29:15 INFO | zfs_encryption_aes_128_ccm_rd_rate_mbytes_per_second_average 68.9800 15:29:15 INFO | zfs_encryption_aes_192_ccm_wr_rate_mbytes_per_second_average 79.4400 15:29:15 INFO | zfs_encryption_aes_192_ccm_rd_rate_mbytes_per_second_average 67.0700 15:29:15 INFO | zfs_encryption_aes_256_ccm_wr_rate_mbytes_per_second_average 78.2600 15:29:15 INFO | zfs_encryption_aes_256_ccm_rd_rate_mbytes_per_second_average 64.2200 15:29:15 INFO | zfs_encryption_aes_128_gcm_wr_rate_mbytes_per_second_average 79.2000 15:29:15 INFO | zfs_encryption_aes_128_gcm_rd_rate_mbytes_per_second_average 79.4600 15:29:15 INFO | zfs_encryption_aes_192_gcm_wr_rate_mbytes_per_second_average 78.9500 15:29:15 INFO | zfs_encryption_aes_192_gcm_rd_rate_mbytes_per_second_average 77.5500 15:29:15 INFO | zfs_encryption_aes_256_gcm_wr_rate_mbytes_per_second_average 78.3500 15:29:15 INFO | zfs_encryption_aes_256_gcm_rd_rate_mbytes_per_second_average 76.0900 Benchmarks: optimized 15:13:33 INFO | zfs_encryption_aes_128_ccm_wr_rate_mbytes_per_second_average 89.2900 15:13:33 INFO | zfs_encryption_aes_128_ccm_rd_rate_mbytes_per_second_average 73.2800 15:13:33 INFO | zfs_encryption_aes_192_ccm_wr_rate_mbytes_per_second_average 88.9800 15:13:33 INFO | zfs_encryption_aes_192_ccm_rd_rate_mbytes_per_second_average 70.9100 15:13:33 INFO | zfs_encryption_aes_256_ccm_wr_rate_mbytes_per_second_average 88.3000 15:13:33 INFO | zfs_encryption_aes_256_ccm_rd_rate_mbytes_per_second_average 68.4500 15:13:33 INFO | zfs_encryption_aes_128_gcm_wr_rate_mbytes_per_second_average 113.1000 15:13:33 INFO | zfs_encryption_aes_128_gcm_rd_rate_mbytes_per_second_average 353.2000 15:13:33 INFO | zfs_encryption_aes_192_gcm_wr_rate_mbytes_per_second_average 112.7000 15:13:33 INFO | zfs_encryption_aes_192_gcm_rd_rate_mbytes_per_second_average 349.7000 15:13:33 INFO | zfs_encryption_aes_256_gcm_wr_rate_mbytes_per_second_average 111.6000 15:13:33 INFO | zfs_encryption_aes_256_gcm_rd_rate_mbytes_per_second_average 344.6000 ** Description changed: == SRU Justification == Upstream commit 31b160f0a6c673c8f926233af2ed6d5354808393 contains AES- GCM acceleration changes that significantly improve encrypted performance. Tests on a memory backed pool show performance improvements of ~15-22% for AES-CCM writes, ~17-20% AES-CCM reads, 34-36% AES-GCM writes and ~79-80% AES-GCM reads on a Sandybridge x86-64 CPU, so this looks like a promising optimization that will benefit a lot of users. == The fix == Backport of upstream 31b160f0a6c673c8f926233af2ed6d5354808393 - this is already backported in Groovy ZFS 0.8.3-1ubuntu13 == Test case == Run ZFS performance tests from ubuntu_performance_zfs_encryption ubuntu kernel team autotests. With the fix the encryption runs significantly faster, as noted earlier in the SRU justification. + Also test with the 4 types of ZFS ubuntu autotests, should not fail any + of these. + == Regression Potential == This fix alters the crypto engine and adds in new optimizations for CPUs that have capable instruction sets. There is a risk that this new crypto code is erroneous. -- 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/1881107 Title: zfs: backport AES-GCM performance accelleration Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: In Progress Status in zfs-linux source package in Groovy: Fix Released Bug description: == SRU Justification == Upstream commit 31b160f0a6c673c8f926233af2ed6d5354808393 contains AES- GCM acceleration changes that significantly improve encrypted performance. Tests on a memory backed pool show performance improvements of ~15-22% for AES-CCM writes, ~17-20% AES-CCM reads, 34-36% AES-GCM writes and ~79-80% AES-GCM reads on a Sandybridge x86-64 CPU, so this looks like a promising optimization that will benefit a lot of users. == The fix == Backport of upstream 31b160f0a6c673c8f926233af2ed6d5354808393 - this is already backported in Groovy ZFS 0.8.3-1ubuntu13 == Test case == Run ZFS performance tests from ubuntu_performance_zfs_encryption ubuntu kernel team autotests. With the fix the encryption runs significantly faster, as noted earlier in the SRU justification. Also test with the 4 types of ZFS ubuntu autotests, should not fail any of these. == Regression Potential == This fix alters the crypto engine and adds in new optimizations for CPUs that have capable instruction sets. There is a risk that this new crypto code is erroneous. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881107/+subscriptions -- Mailing list: https://la
[Kernel-packages] [Bug 1880445] Re: Hercules Classic Link does not work in recent Ubuntu versions (but does in 14.04 and 16.04)
Situation update: web camera works with guvcview, but not with Cheese, Skype or browser -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880445 Title: Hercules Classic Link does not work in recent Ubuntu versions (but does in 14.04 and 16.04) Status in linux package in Ubuntu: Confirmed Bug description: I've got a bug similar to this one here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872634 There's a detailed description here https://askubuntu.com/questions/1241552/making-hercules-classic-link- web-camera-work-with-ubuntu-19-10 The strange thing is, it does not work in 19.10 and live-usb 20.04, but it does work in 14.04 and 16.04. The last one I tried from Virtualbox by adding a USB device in the settings - and it works just fine. When I do `lsmod | grep gspca` in 16.04, I get the following output: gspca_pac7302 20480 0 gspca_main 36864 1 gspca_pac7302 v4l2_common16384 2 gspca_main videodev 188416 3 gspca_main, gspca_pac7302, v4l2_common Whereas on my machine with 19.10 it's like this: gspca_pac7302 20480 0 gspca_main 24576 1 gspca_pac7302 videobuf2_vmalloc 20480 1 gspca_main videobuf2_v4l2 24576 1 gspca_main videobuf2_common 53248 2 gspca_main,videobuf2_v4l2 videodev 208896 5 gspca_main,gspca_pac7302,v4l2_common,videobuf2_v4l2,videobuf2_common I already tried modprobe -r for all videobuf2_* and gspca_* modules and adding v4l2, but it just restored the previous module config. Could you please advice how could I solve this? I'm not sure which way to follow from here. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mao3074 F pulseaudio /dev/snd/controlC0: mao3074 F pulseaudio /dev/snd/controlC1: mao3074 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=b4d0333b-5cb2-4e38-9b7d-5c6e156875b6 resume_offset=66347008 InstallationDate: Installed on 2020-02-09 (105 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=b4d0333b-5cb2-4e38-9b7d-5c6e156875b6 ro resume=UUID=b4d0333b-5cb2-4e38-9b7d-5c6e156875b6 resume_offset=66347008 quiet splash ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-53-generic N/A linux-backports-modules-5.3.0-53-generic N/A linux-firmware1.183.5 RfKill: Tags: eoan Uname: Linux 5.3.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd netdev plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 09/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/04/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881134] Re: amdgpu crashes in mode_support_and_system_configuration
It's at https://gitlab.freedesktop.org/drm/amd/issues -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881134 Title: amdgpu crashes in mode_support_and_system_configuration Status in linux package in Ubuntu: Confirmed Bug description: When switching window from gnome-terminal to firefox, the amdgpu kernel driver suddenly crashed. This caused screen to freeze completely, but ssh to the machine still worked ok. There is a similar bug filed in https://bugzilla.kernel.org/show_bug.cgi?id=206987 but not much activity. I'm not sure if there is an amdgpu specific bugtracker somewhere. Below is a decoded call trace and I've attached the full dmesg output. [455834.384976] simd exception: [#1] SMP NOPTI [455834.384980] CPU: 1 PID: 2411 Comm: Xorg Tainted: GW OE 5.4.0-31-generic #35-Ubuntu ... [455834.385061] Call Trace: [455834.385120] mode_support_and_system_configuration (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calc_auto.c:176) amdgpu [455834.385174] ? calculate_inits_and_adj_vp (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:950 (discriminator 12)) amdgpu [455834.385230] dcn_validate_bandwidth (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.c:1034) amdgpu [455834.385283] dc_validate_global_state (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:2093) amdgpu [455834.385338] amdgpu_dm_atomic_check (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:7413) amdgpu [455834.385351] drm_atomic_check_only (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_atomic.c:1179) drm [455834.385361] drm_atomic_commit (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_atomic.c:1220) drm [455834.385370] drm_mode_obj_set_property_ioctl (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_mode_object.c:496 /build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_mode_object.c:533) drm [455834.385379] ? drm_mode_obj_find_prop_id (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_mode_object.c:512) drm [455834.385386] drm_ioctl_kernel (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_ioctl.c:793) drm [455834.385394] drm_ioctl (/build/linux-FFoizL/linux-5.4.0/include/linux/thread_info.h:119 /build/linux-FFoizL/linux-5.4.0/include/linux/thread_info.h:152 /build/linux-FFoizL/linux-5.4.0/include/linux/uaccess.h:151 /build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_ioctl.c:888) drm [455834.385402] ? drm_mode_obj_find_prop_id (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/drm_mode_object.c:512) drm [455834.385406] ? recalc_sigpending (/build/linux-FFoizL/linux-5.4.0/kernel/signal.c:184) [455834.385440] amdgpu_drm_ioctl (/build/linux-FFoizL/linux-5.4.0/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c:1293) amdgpu [455834.385443] do_vfs_ioctl (/build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:47 /build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:510 /build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:697) [455834.385444] ? recalc_sigpending (/build/linux-FFoizL/linux-5.4.0/kernel/signal.c:184) [455834.385446] ? _copy_from_user (/build/linux-FFoizL/linux-5.4.0/arch/x86/include/asm/uaccess_64.h:46 /build/linux-FFoizL/linux-5.4.0/arch/x86/include/asm/uaccess_64.h:71 /build/linux-FFoizL/linux-5.4.0/lib/usercopy.c:14) [455834.385448] ksys_ioctl (/build/linux-FFoizL/linux-5.4.0/include/linux/file.h:43 /build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:715) [455834.385449] __x64_sys_ioctl (/build/linux-FFoizL/linux-5.4.0/fs/ioctl.c:719) [455834.385451] do_syscall_64 (/build/linux-FFoizL/linux-5.4.0/arch/x86/entry/common.c:290) [455834.385455] entry_SYSCALL_64_after_hwframe (/build/linux-FFoizL/linux-5.4.0/arch/x86/entry/entry_64.S:184) [455834.385456] RIP: 0033:0x7faf3181837b ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: petteri1198 F pulseaudio /dev/snd/controlC0: petteri1198 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ICEWM Date: Thu May 28 17:09:28 2020 InstallationDate: Installed on 2020-05-20 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-31-generic root=UUID=81e6e5d0-6a69-412b-8f6c-d6d765ae32de ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A l
[Kernel-packages] [Bug 1834322] Re: Losing port aggregate with 802.3ad port-channel/bonding aggregation on reboot
Could anyone hitting this bug confirm it is a DUP of LP Bug 1852077 and that latest releases fix this issue? The handling of the state changes/updates borked here due to not just marking it as a DUP and closing this one. I will close this next week otherwise. ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834322 Title: Losing port aggregate with 802.3ad port-channel/bonding aggregation on reboot Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: We are losing port channel aggregation on reboot. After the reboot, /var/log/syslog contains the entries: [ 250.790758] bond2: An illegal loopback occurred on adapter (enp24s0f1np1) Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports [ 282.029426] bond2: An illegal loopback occurred on adapter (enp24s0f1np1) Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports Aggregator IDs of the slave interfaces are different: ubuntu@node-6:~$ cat /proc/net/bonding/bond2 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer3+4 (1) MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 802.3ad info LACP rate: fast Min links: 0 Aggregator selection policy (ad_select): stable Slave Interface: enp24s0f1np1 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: b0:26:28:48:9f:51 Slave queue ID: 0 Aggregator ID: 1 Actor Churn State: none Partner Churn State: none Actor Churned Count: 0 Partner Churned Count: 0 Slave Interface: enp24s0f0np0 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: b0:26:28:48:9f:50 Slave queue ID: 0 Aggregator ID: 2 Actor Churn State: churned Partner Churn State: churned Actor Churned Count: 1 Partner Churned Count: 1 The mismatch in "Aggregator ID" on the port is a symptom of the issue. If we do 'ip link set dev bond2 down' and 'ip link set dev bond2 up', the port with the mismatched ID appears to renegotiate with the port- channel and becomes aggregated. The other way to workaround this issue is to put bond ports down and bring up port enp24s0f0np0 first and port enp24s0f1np1 second. When I change the order of bringing the ports up (first enp24s0f1np1, and second enp24s0f0np0), the issue is still there. When the issue occurs, a port on the switch, corresponding to interface enp24s0f0np0 is in Suspended state. After applying the workaround the port is no longer in Suspended state and Aggregator IDs in /proc/net/bonding/bond2 are equal. I installed 5.0.0 kernel, the issue is still there. Operating System: Ubuntu 18.04.2 LTS (GNU/Linux 4.15.0-52-generic x86_64) ubuntu@node-6:~$ uname -a Linux node-6 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ubuntu@node-6:~$ sudo lspci -vnvn https://pastebin.ubuntu.com/p/Dy2CKDbySC/ Hardware: Dell PowerEdge R740xd BIOS version: 2.1.7 sosreport: https://drive.google.com/open?id=1-eN7cZJIeu- AQBEU7Gw8a_AJTuq0AOZO ubuntu@node-6:~$ lspci | grep Ethernet | grep 10G https://pastebin.ubuntu.com/p/sqCx79vZWM/ ubuntu@node-6:~$ lspci -n | grep 18:00 18:00.0 0200: 14e4:16d8 (rev 01) 18:00.1 0200: 14e4:16d8 (rev 01) ubuntu@node-6:~$ modinfo bnx2x https://pastebin.ubuntu.com/p/pkmzsFjK8M/ ubuntu@node-6:~$ ip -o l https://pastebin.ubuntu.com/p/QpW7TjnT2v/ ubuntu@node-6:~$ ip -o a https://pastebin.ubuntu.com/p/MczKtrnmDR/ ubuntu@node-6:~$ cat /etc/netplan/98-juju.yaml https://pastebin.ubuntu.com/p/9cZpPc7C6P/ ubuntu@node-6:~$ sudo lshw -c network https://pastebin.ubuntu.com/p/gmfgZptzDT/ --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 26 10:21 seq crw-rw 1 root audio 116, 33 Jun 26 10:21 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/
[Kernel-packages] [Bug 1881124] Re: I2C bus on Dell Edge Gateway stops working after upgrading to Ubuntu-4.4.0-180.210
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881124 Title: I2C bus on Dell Edge Gateway stops working after upgrading to Ubuntu-4.4.0-180.210 Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: I2C stops working after kernel upgrade: [ 13.812210] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x [ 13.855837] i2c_designware 80860F41:01: timeout in enabling adapter [ 14.856276] i2c_designware 80860F41:01: controller timed out [ 14.856288] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x This is caused by the commit commit 5568c3f29fbd0ec0d9bb0f805bacc5755180c5cb Author: Andy Shevchenko Date: Fri Dec 4 23:49:18 2015 +0200 Revert "ACPI / LPSS: allow to use specific PM domain during ->probe()" BugLink: https://bugs.launchpad.net/bugs/1878232 commit b5f88dd1d6efc472e35ca1b21a44e662c5422088 upstream. The specific power domain can't be used in a way provided by the commit 01ac170ba29a, i.e. pointer to platform device is a subject to change during unbound / bind cycle. This reverts commit 01ac170ba29a9903ee590e1ef2d8e6b27b49a16c. Fixes: 3df2da968744 (Revert "ACPI / LPSS: introduce a 'proxy' device to power on LPSS for DMA") Signed-off-by: Andy Shevchenko Signed-off-by: Rafael J. Wysocki Signed-off-by: Greg Kroah-Hartman Signed-off-by: Ian May Signed-off-by: Kleber Sacilotto de Souza To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1881124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1881107] Re: zfs: backport AES-GCM performance accelleration
There is another AES-GCM performance acceleration commit for systems without MOVBE. -- Richard -- 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/1881107 Title: zfs: backport AES-GCM performance accelleration Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: In Progress Status in zfs-linux source package in Groovy: Fix Released Bug description: == SRU Justification == Upstream commit 31b160f0a6c673c8f926233af2ed6d5354808393 contains AES- GCM acceleration changes that significantly improve encrypted performance. Tests on a memory backed pool show performance improvements of ~15-22% for AES-CCM writes, ~17-20% AES-CCM reads, 34-36% AES-GCM writes and ~79-80% AES-GCM reads on a Sandybridge x86-64 CPU, so this looks like a promising optimization that will benefit a lot of users. == The fix == Backport of upstream 31b160f0a6c673c8f926233af2ed6d5354808393 - this is already backported in Groovy ZFS 0.8.3-1ubuntu13 == Test case == Run ZFS performance tests from ubuntu_performance_zfs_encryption ubuntu kernel team autotests. With the fix the encryption runs significantly faster, as noted earlier in the SRU justification. Also test with the 4 types of ZFS ubuntu autotests, should not fail any of these. == Regression Potential == This fix alters the crypto engine and adds in new optimizations for CPUs that have capable instruction sets. There is a risk that this new crypto code is erroneous. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834322] Re: Losing port aggregate with 802.3ad port-channel/bonding aggregation on reboot
Note that fix for all the above series are already released. i.e, from Ubuntu-4.15.0-73.82. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834322 Title: Losing port aggregate with 802.3ad port-channel/bonding aggregation on reboot Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: We are losing port channel aggregation on reboot. After the reboot, /var/log/syslog contains the entries: [ 250.790758] bond2: An illegal loopback occurred on adapter (enp24s0f1np1) Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports [ 282.029426] bond2: An illegal loopback occurred on adapter (enp24s0f1np1) Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports Aggregator IDs of the slave interfaces are different: ubuntu@node-6:~$ cat /proc/net/bonding/bond2 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer3+4 (1) MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 802.3ad info LACP rate: fast Min links: 0 Aggregator selection policy (ad_select): stable Slave Interface: enp24s0f1np1 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: b0:26:28:48:9f:51 Slave queue ID: 0 Aggregator ID: 1 Actor Churn State: none Partner Churn State: none Actor Churned Count: 0 Partner Churned Count: 0 Slave Interface: enp24s0f0np0 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: b0:26:28:48:9f:50 Slave queue ID: 0 Aggregator ID: 2 Actor Churn State: churned Partner Churn State: churned Actor Churned Count: 1 Partner Churned Count: 1 The mismatch in "Aggregator ID" on the port is a symptom of the issue. If we do 'ip link set dev bond2 down' and 'ip link set dev bond2 up', the port with the mismatched ID appears to renegotiate with the port- channel and becomes aggregated. The other way to workaround this issue is to put bond ports down and bring up port enp24s0f0np0 first and port enp24s0f1np1 second. When I change the order of bringing the ports up (first enp24s0f1np1, and second enp24s0f0np0), the issue is still there. When the issue occurs, a port on the switch, corresponding to interface enp24s0f0np0 is in Suspended state. After applying the workaround the port is no longer in Suspended state and Aggregator IDs in /proc/net/bonding/bond2 are equal. I installed 5.0.0 kernel, the issue is still there. Operating System: Ubuntu 18.04.2 LTS (GNU/Linux 4.15.0-52-generic x86_64) ubuntu@node-6:~$ uname -a Linux node-6 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ubuntu@node-6:~$ sudo lspci -vnvn https://pastebin.ubuntu.com/p/Dy2CKDbySC/ Hardware: Dell PowerEdge R740xd BIOS version: 2.1.7 sosreport: https://drive.google.com/open?id=1-eN7cZJIeu- AQBEU7Gw8a_AJTuq0AOZO ubuntu@node-6:~$ lspci | grep Ethernet | grep 10G https://pastebin.ubuntu.com/p/sqCx79vZWM/ ubuntu@node-6:~$ lspci -n | grep 18:00 18:00.0 0200: 14e4:16d8 (rev 01) 18:00.1 0200: 14e4:16d8 (rev 01) ubuntu@node-6:~$ modinfo bnx2x https://pastebin.ubuntu.com/p/pkmzsFjK8M/ ubuntu@node-6:~$ ip -o l https://pastebin.ubuntu.com/p/QpW7TjnT2v/ ubuntu@node-6:~$ ip -o a https://pastebin.ubuntu.com/p/MczKtrnmDR/ ubuntu@node-6:~$ cat /etc/netplan/98-juju.yaml https://pastebin.ubuntu.com/p/9cZpPc7C6P/ ubuntu@node-6:~$ sudo lshw -c network https://pastebin.ubuntu.com/p/gmfgZptzDT/ --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 26 10:21 seq crw-rw 1 root audio 116, 33 Jun 26 10:21 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 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 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1604:10c0 Tascam Bus 001 Device 003: ID 1604:10c0 Tascam Bus 001 Device 002: ID 1604:10c0 Tascam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R740xd Package: linux (not installed) PciM
