[Kernel-packages] [Bug 1875099] Re: RTL8822BE Wifi [10ec:b822] subsystem [17aa:b023] crashes on 20.04 on Lenovo Legion Y530
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc7/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875099 Title: RTL8822BE Wifi [10ec:b822] subsystem [17aa:b023] crashes on 20.04 on Lenovo Legion Y530 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Incomplete Bug description: After upgrading Ubuntu Mate to 20.04 , my wifi crashed on Lenovo legion Y530. The strange thing is that it connects to the network, i have internet for some time (usually between 1 and 10 minutes) and then it disconnects. After that, the applet shows me something like device not ready and i can only restart the computer to connect. Then it crashes again... I also tried a fresh install with the same results. I used 19.04 and 19.10 on the same laptop as my primary operating system and wifi worked flawlessly. Since I do my work on this laptop i was forced to downgrade back to 19.10 for now. This is my lshw -C network (from 19.10 If I remember correctly it was RTL8822BE also in 20.04) *-network description: Wireless interface product: RTL8822BE 802.11a/b/g/n/ac WiFi adapter vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:07:00.0 logical name: wlp7s0 version: 00 serial: dc:a2:66:80:7d:7d width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=rtw_pci driverversion=5.3.0-46-generic firmware=N/A ip=192.168.0.146 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:141 ioport:4000(size=256) memory:a430-a430 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:08:00.0 logical name: enp8s0 version: 15 serial: 8c:16:45:e9:e9:a8 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:17 ioport:3000(size=256) memory:a4204000-a4204fff memory:a420-a4203fff and my lspci -nnk | grep -A2 0280 07:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822] Subsystem: Lenovo RTL8822BE 802.11a/b/g/n/ac WiFi adapter [17aa:b023] Kernel driver in use: rtw_pci If you think it is necessary, I can try to install 20.04 on an external hard drive and give you some more info from there. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: campus 1207 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-09 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81FV NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=2ba3f662-50a5-4db8-a5e1-ddaf5e09d5a9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-29-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: 07/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8JCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion Y530-15ICH dmi.modalias: dmi:bvnLENOVO:bvr8JCN43WW:bd07/18/2018:svnLENOVO:pn81FV:pvrLenovoLegionY530-15ICH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH: dmi.product.family: Legion Y530-15ICH dmi.product.name: 81FV dmi.product.sku: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH dmi.product.version: Lenovo Legion Y530-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1881062] Re: Mouse pointer disappeared after upgrade
Please attach your /var/log/apt/history.log so we can see what changed on the 28th of May. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (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/1881062 Title: Mouse pointer disappeared after upgrade Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Mouse vendor: Elecom Mouse name: Deft M-DT20R S/N 99011158 S/N 9700261B I have two sets of this model and both are not working any more. Wireless USB mouse stopped working after 'sudo apt upgrade' on 0:00 UTC 28th May 2020. I also upgraded BIOS of ThinkStation P500 from A4KT89US to A4KTA7US just an hour before the upgrade. However I plugged in an old wired Elecom USB mouse and this is working. And also I tried another wireless USB mouse Logicool M570, this model is working except the left-click or right-click (means unstable). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41 Uname: Linux 5.4.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Thu May 28 13:14:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107GL [Quadro K2200] [10de:1097] InstallationDate: Installed on 2020-05-25 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 30A6S45A16 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=822191be-6b70-4841-97dc-e4c008d418b2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: A4KTA7AUS dmi.board.name: 102F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN 3425060692537 dmi.chassis.type: 7 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrA4KTA7AUS:bd04/13/2020:svnLENOVO:pn30A6S45A16:pvrThinkStationP500:rvnLENOVO:rn102F:rvrSDK0J40705WIN3425060692537:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.: dmi.product.family: ThinkStation P500 dmi.product.name: 30A6S45A16 dmi.product.sku: LENOVO_MT_30A6_BU_Think_FM_ThinkStation P500 dmi.product.version: ThinkStation P500 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: [focal] disk I/O performance regression
Note that I didn't add any kernel parameter, so my first guess would be "iommu=pt" doesn't get passthrough right. ** 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/1880943 Title: [focal] disk I/O performance regression Status in linux package in Ubuntu: Incomplete 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:
[Kernel-packages] [Bug 1875200] Re: [amdgpu] Entire computer freezes shortly after bootup
Can you please remove "nomodeset" kernel parameter? ** 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/1875200 Title: [amdgpu] Entire computer freezes shortly after bootup Status in linux package in Ubuntu: Incomplete Bug description: I'm not sure if this bug was filed completely; I used the "ubuntu-bug" command which gathered a lot of information and files, but then the bugs.launchpad.net site timeouted and I'm not sure if the information I entered before and the files that were gathered have actually been submitted. Summary: after an upgrade to Ubuntu 20.04 my entire computer freezes some seconds after bootup. It does not even reply to pings anymore and remote logins stop working as well. When booting it in recovery mode and then immediately using the menu option to continue booting, it appears to work reliably, but it only detects one monitor and there is no 3d acceleration. I've seen freezes happening at the following points: a) at the stage of a black screnen saying "lenovo" in the middle and "ubuntu" at the bottom (of both monitors) b) when asking for username and password to login c) after login When I was using the same computer with Ubuntu 19.10, there was no such problem. The computer is a Lenovo ThinkCentre M920x, the graphics card used is 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] (rev ef) with two monitors (3840x2160) connected via MiniDisplayPort ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 14:29:19 2020 DistUpgraded: 2020-04-25 14:33:16,904 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Subsystem: Lenovo UHD Graphics 630 (Desktop 9 Series) [17aa:3135] Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] [1002:67ff] (rev ef) (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Baffin [Radeon RX 550 640SP / RX 560/560X] [1642:1725] InstallationDate: Installed on 2020-03-29 (28 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 10S1002NMZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ff61fce1-cc83-4bbe-bc88-09cdd2ac7471 ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) XorgLogOld: dmi.bios.date: 02/17/2020 dmi.bios.vendor: LENOVO dmi.bios.version: M1UKT50A dmi.board.name: 3135 dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN 3305220985042 dmi.chassis.type: 35 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM1UKT50A:bd02/17/2020:svnLENOVO:pn10S1002NMZ:pvrThinkCentreM920x:rvnLENOVO:rn3135:rvrSDK0T08861WIN3305220985042:cvnLENOVO:ct35:cvrNone: dmi.product.family: ThinkCentre M920x dmi.product.name: 10S1002NMZ dmi.product.sku: LENOVO_MT_10S1_BU_Think_FM_ThinkCentre M920x dmi.product.version: ThinkCentre M920x dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: [focal] disk I/O performance regression
Tried 4.15.0-102, 5.4.0-33 and mailing kernel all three show similar performance (~2100MB/s). Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc7/ And decide what's the next step based on the performance of mainline kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880943 Title: [focal] disk I/O performance regression Status in linux package in Ubuntu: Incomplete 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
[Kernel-packages] [Bug 1880666] Re: Power management: does not suspend
I don't think it's a kernel issue. Some userspace process blocked the suspend. Can you please test whether suspend works under Ubuntu live USB? ** 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/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 1878166] Re: Kernel crash in nouveau with Wayland
Please test latest drm-tip kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ If the kernel still have the issue, please file an upstream bug at https://bugs.freedesktop.org/ Product: xorg Component: DRM/nouveau ** 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/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Incomplete Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877670] Re: [Acer Aspire R3-131T] Touchpad freezes and frequently mouse cursor disappears.
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc7/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877670 Title: [Acer Aspire R3-131T] Touchpad freezes and frequently mouse cursor disappears. Status in linux package in Ubuntu: Incomplete Bug description: Display Freezes and frequently mouse cursor disappears. After restart mouse cursor comes back again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 02:25:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1025:1022] InstallationDate: Installed on 2020-04-23 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 2386:0401 Raydium Corporation Raydium Touch System Bus 001 Device 002: ID 04f2:b520 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire R3-131T ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=5b613349-680c-466c-b069-960c9c12c462 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire R3-131T dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireR3-131T:pvrV1.17:rvnAcer:rnAspireR3-131T:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.family: BSW dmi.product.name: Aspire R3-131T dmi.product.sku: Aspire R3-131T_1022_1.17 dmi.product.version: V1.17 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872401] Re: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / X-KVM / B-KVM
This is still failing with the kvm-unit-tests from upstream. Note that with the upstream repo, you will have to split the vmx_nm_tests like below: https://kernel.ubuntu.com/git/ubuntu/kvm-unit-tests/commit/?h=disco=4671e4baaec6c968e626e9fc3557aa4581504586 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1872401 Title: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / X-KVM / B-KVM Status in ubuntu-kernel-tests: New Status in linux-signed-oracle package in Ubuntu: New Bug description: This issue was first spotted on Mar.16 [1] The ubuntu_kvm_unit_tests will be interrupted on X-oracle-4.15 on both VM.Standard2.1 and VM.Standard2.16, this is not a regression since it can be reproduced with 4.15.0-1031-oracle #34~16.04.1: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_nm_test' BUILD_HEAD=4671e4ba timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.da3iFrsCzC -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.h2DFw8L0AF enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_nm_test client_loop: send disconnect: Broken pipe (node disconnected here) Before the test started, this can be found in syslog: Apr 13 06:26:25 selfprovisioned-phlin-kvm-unit kernel: [ 1073.529005] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. After that, noting was printed and node disconnected. If you try to run this case manually, it will stop at: # ./vmx_nm_test BUILD_HEAD=4671e4ba ready!!! timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.ZcGrnXu6se -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.ADjEOAcRKM enabling ap (stopped here, even the "enabling apic" string was not printed) It looks like this is a new test case added since the cycle of 4.15.0-1037.41~16.04.1-oracle [1] https://bugs.launchpad.net/ubuntu-kernel- tests/+bug/1867623/comments/2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-1031-oracle 4.15.0-1031.34~16.04.1 ProcVersionSignature: User Name 4.15.0-1031.34~16.04.1-oracle 4.15.18 Uname: Linux 4.15.0-1031-oracle x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Mon Apr 13 05:18:03 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1872401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879612] Re: Ralink RT5390 [1814:539f] Subsystem [103c:1774] Wifi looses connection more often after the upgrade
@ Bankapur, can find any deauthenticating/disconnecting signature from the log. Please attach one after the symptom reappears. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879612 Title: Ralink RT5390 [1814:539f] Subsystem [103c:1774] Wifi looses connection more often after the upgrade Status in linux package in Ubuntu: Incomplete Bug description: I upgraded my ubuntu to 20.04 LTS. After the upgrade I keep seeing the wifi issues. More often it keeps getting disconnected and I will have to go on Airplane mode to re enable the connectivity. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raghavendra 2046 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-02 (230 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=c6751bdb-dd90-489c-9932-b52487fb6eea ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/03/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd06/03/2014:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr07921020561610100:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: B3H81PA#ACJ dmi.product.version: 07921020561610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872401] Re: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / X-KVM / B-KVM
BTW the power status on MAAS will be "OFF" And since this KVM will be in "paused" state, it needs to be destroyed before re-deploying, it seems this is why we constantly seeing deploying failures on KVM nodes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1872401 Title: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / X-KVM / B-KVM Status in ubuntu-kernel-tests: New Status in linux-signed-oracle package in Ubuntu: New Bug description: This issue was first spotted on Mar.16 [1] The ubuntu_kvm_unit_tests will be interrupted on X-oracle-4.15 on both VM.Standard2.1 and VM.Standard2.16, this is not a regression since it can be reproduced with 4.15.0-1031-oracle #34~16.04.1: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_nm_test' BUILD_HEAD=4671e4ba timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.da3iFrsCzC -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.h2DFw8L0AF enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_nm_test client_loop: send disconnect: Broken pipe (node disconnected here) Before the test started, this can be found in syslog: Apr 13 06:26:25 selfprovisioned-phlin-kvm-unit kernel: [ 1073.529005] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. After that, noting was printed and node disconnected. If you try to run this case manually, it will stop at: # ./vmx_nm_test BUILD_HEAD=4671e4ba ready!!! timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.ZcGrnXu6se -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.ADjEOAcRKM enabling ap (stopped here, even the "enabling apic" string was not printed) It looks like this is a new test case added since the cycle of 4.15.0-1037.41~16.04.1-oracle [1] https://bugs.launchpad.net/ubuntu-kernel- tests/+bug/1867623/comments/2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-1031-oracle 4.15.0-1031.34~16.04.1 ProcVersionSignature: User Name 4.15.0-1031.34~16.04.1-oracle 4.15.18 Uname: Linux 4.15.0-1031-oracle x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Mon Apr 13 05:18:03 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1872401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872401] Re: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15
This issue can be reproduced with KVM nodes on our BareMetal MAAS Step to reproduce: 1. Deploy a KVM node with Xenial / Bionic 2. sudo apt install gcc build-essential cpu-checker qemu-kvm git 3. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/kvm-unit-tests/ -b disco 4. cd kvm-unit-tests 5. ./configure 6. make standalone 7. cd tests 8. sudo ./vmx_nm_test BUILD_HEAD=4671e4ba timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.wHvN1CDAeZ -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.J5VNtXChPd enabling ap (Test interrupted here) When this happens, the node will stop responding, nothing special can be found in syslog. The virsh on the host will show it's been paused: $ virsh list IdName State 533 curly paused ** Summary changed: - vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 + vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / X-KVM / B-KVM ** Tags added: 4.4 bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1872401 Title: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / X-KVM / B-KVM Status in ubuntu-kernel-tests: New Status in linux-signed-oracle package in Ubuntu: New Bug description: This issue was first spotted on Mar.16 [1] The ubuntu_kvm_unit_tests will be interrupted on X-oracle-4.15 on both VM.Standard2.1 and VM.Standard2.16, this is not a regression since it can be reproduced with 4.15.0-1031-oracle #34~16.04.1: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_nm_test' BUILD_HEAD=4671e4ba timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.da3iFrsCzC -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.h2DFw8L0AF enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_nm_test client_loop: send disconnect: Broken pipe (node disconnected here) Before the test started, this can be found in syslog: Apr 13 06:26:25 selfprovisioned-phlin-kvm-unit kernel: [ 1073.529005] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. After that, noting was printed and node disconnected. If you try to run this case manually, it will stop at: # ./vmx_nm_test BUILD_HEAD=4671e4ba ready!!! timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.ZcGrnXu6se -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.ADjEOAcRKM enabling ap (stopped here, even the "enabling apic" string was not printed) It looks like this is a new test case added since the cycle of 4.15.0-1037.41~16.04.1-oracle [1] https://bugs.launchpad.net/ubuntu-kernel- tests/+bug/1867623/comments/2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-1031-oracle 4.15.0-1031.34~16.04.1 ProcVersionSignature: User Name 4.15.0-1031.34~16.04.1-oracle 4.15.18 Uname: Linux 4.15.0-1031-oracle x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Mon Apr 13 05:18:03 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1872401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 271254] Re: [ffe] drbd doesn't start: "No response from the DRBD driver! Is the module loaded?" but module is loaded
Difficulty to boot when processing "block device major 147" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/271254 Title: [ffe] drbd doesn't start: "No response from the DRBD driver! Is the module loaded?" but module is loaded Status in drbd8 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in drbd8 source package in Intrepid: Fix Released Status in linux source package in Intrepid: Invalid Bug description: If I try to start drbd I get the following error: root@intrepid:~# /etc/init.d/drbd restart * Restarting all DRBD resources No response from the DRBD driver! Is the module loaded? Command '/sbin/drbdsetup /dev/drbd0 down' terminated with exit code 20 drbdsetup exited with code 20 No response from the DRBD driver! Is the module loaded? Command '/sbin/drbdsetup /dev/drbd0 disk /dev/mapper/vol_grp1-ldap1 /dev/mapper/vol_grp1-ldap1 internal --set-defaults --create-device --on-io-error=detach' terminated with exit code 20 dmesg|tail says: [ 2124.572783] drbd: module cleanup done. [ 2124.594175] drbd: initialised. Version: 8.2.6 (api:88/proto:86-88) [ 2124.594188] drbd: GIT-hash: 3e69822d3bb4920a8c1bfdf7d647169eba7d2eb4 build by phil@fat-tyre, 2008-05-30 12:59:17 [ 2124.594190] drbd: registered as block device major 147 [ 2124.594192] drbd: minor_table @ 0x880c23cac700 and lsmod|grep drbd drbd 243624 0 cn 17068 2 drbd,uvesafb on manual drbdadm attach ressource-name: No response from the DRBD driver! Is the module loaded? Command 'drbdsetup /dev/drbd0 disk /dev/mapper/vol_grp1-ldap1 /dev/mapper/vol_grp1-ldap1 internal --set-defaults --create-device --on-io-error=detach' terminated with exit code 20 I think there is somewhere a bug in the drbd driver? On hardy there was no problem to start drbd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/271254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865293] Re: ryzen 5 3600x soft lockups
So another soft lockup. It was followed by a hard lockup on the next reboot. ** Attachment added: "journal_log05272020.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865293/+attachment/5377634/+files/journal_log05272020.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865293 Title: ryzen 5 3600x soft lockups Status in linux package in Ubuntu: Confirmed Bug description: I am using ubuntu 19.10 with a ryzen 5 3600x cpu and am getting soft lockups with the machine unresponsive almost on a daily basis. The only fix is a hard reset. I have the latest amd64-microcode installed - 3.20191021.1+really3.20181128.1ubuntu2, but still continues to happen. Description: Ubuntu 19.10 Release: 19.10 using kernel: 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: martin 2483 F pulseaudio /dev/snd/controlC0: martin 2483 F pulseaudio /dev/snd/controlC2: martin 2483 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-08 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: enp4s0no wireless extensions. lono wireless extensions. 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-40-generic root=UUID=05d2cb45-6b9c-47b3-8102-e6c6a13de26b ro acpi_enforce_resources=lax quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.183.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: eoan Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 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.:bvrF11:bd12/06/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/1865293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301
@Balint Please try the below command: 1. $ acpi_listen => press power button output: button/power PBTN 0080 It is for getting the power button string which is PBTN 2. $ sudo acpidbg -b "notify _SB.PBTN 0x80"; sudo acpidbg -b "notify _SB.PBTN 0x80" To simulate two consecutive power button event It will shutdown directly on focal. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878351 Title: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301 Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: kchsieh@kchsieh-laptop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS (fossa-bulbasaur X23) Release: 20.04 kchsieh@kchsieh-laptop:~$ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expect: When press the button, the endSeesionDialog should show up. Actual: The system shutdown directly. When the issue happend: endSessionDialog is not triggered immediately after the first power button event, but triggered after the second power button event. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-10 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: systemd 245.4-4ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301
@Balint Please try the below command: 1. $ acpi_listen => press power button output: button/power PBTN 0080 It is for getting the power button string which is PBTN 2. $ sudo acpidbg -b "notify _SB.PBTN 0x80"; sudo acpidbg -b "notify _SB.PBTN 0x80" To simulate to consecutive power button event It will shutdown directly on focal. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878351 Title: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301 Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: kchsieh@kchsieh-laptop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS (fossa-bulbasaur X23) Release: 20.04 kchsieh@kchsieh-laptop:~$ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expect: When press the button, the endSeesionDialog should show up. Actual: The system shutdown directly. When the issue happend: endSessionDialog is not triggered immediately after the first power button event, but triggered after the second power button event. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-10 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: systemd 245.4-4ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881015] Re: Fn Lock light does not come on to indicate when Fn Lock is enabled
This led status is controlled by BIOS, not OS. -- You 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 1874359] Re: alsa/sof: kernel oops on the machine without Intel hdmi audio codec (a regression in the asoc machine driver)
** Tags removed: verification-needed-eoan verification-needed-focal ** Tags added: verification-done-eoan verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874359 Title: alsa/sof: kernel oops on the machine without Intel hdmi audio codec (a regression in the asoc machine driver) Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: Please apply the fix for #1872569 first, then apply this patch. [Impact] The fix for #1872569 introduces a regression, the driver access a NULL pointer on the machiens without Intel hdmi audio codec. [Fix] pick a fixing patch from alsa/asoc repo, the patch doesn't assume the first rtd is for hda codec, it will look for that rtd through strstr() [Test Case] Boot the kenrel on those 2 Dell and 2 Lenovo machines which uses this driver, the audio could work. disable the intel hdmi audio codec through bios, the analogue audio still works [Regression Risk] Low, I have tested this patch Lenovo / Dell machines, they all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881046] Re: ASoC/amd: add audio driver for amd renoir
** Description changed: - this bug is for tracking purpose. + This patchset is for mainline kernel-5.8, after backporting to 5.6, + there is no need to change anything, but after backporting to 5.4 + kernel, because of API differences, need to do some change to adapt + to 5.4 kernel's API. So there is one more patch for focal than for + oem-5.6. + + [Impact] + We have a couple of LENOVO machines which has amd renoir audio on + them, our kernel doesn't have the driver for it yet. + + [Fix] + amd just upstreamed the driver, it is for kernel-5.8, we backport + them to ubunt kernel. + + [Test Case] + boot the kernel with those patches, we could see a sound card named + "acp" and the dmic on it could record sound via arecord. + + [Regression Risk] + Low, just adding a new driver, no change to existing drivers. ** Also affects: linux (Ubuntu Groovy) Importance: High Assignee: Hui Wang (hui.wang) Status: Incomplete ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oem-5.6 (Ubuntu Groovy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881046 Title: ASoC/amd: add audio driver for amd renoir Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.6 source package in Focal: New Status in linux source package in Groovy: Incomplete Bug description: This patchset is for mainline kernel-5.8, after backporting to 5.6, there is no need to change anything, but after backporting to 5.4 kernel, because of API differences, need to do some change to adapt to 5.4 kernel's API. So there is one more patch for focal than for oem-5.6. [Impact] We have a couple of LENOVO machines which has amd renoir audio on them, our kernel doesn't have the driver for it yet. [Fix] amd just upstreamed the driver, it is for kernel-5.8, we backport them to ubunt kernel. [Test Case] boot the kernel with those patches, we could see a sound card named "acp" and the dmic on it could record sound via arecord. [Regression Risk] Low, just adding a new driver, no change to existing drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1881046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861284] Re: Build and ship a signed wireguard.ko
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861284 Title: Build and ship a signed wireguard.ko Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Committed Bug description: .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874685] Re: Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found due to firmware crash
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874685 Title: Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found due to firmware crash Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Fix Released 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: Fix Released Status in linux source package in Eoan: Fix Committed 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: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Fix Released Status in linux-oem-osp1 source package in Groovy: Invalid Bug description: [9.924130] iwlwifi :00:14.3: enabling device ( -> 0002) [ 10.031456] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 58.3.35.22 [ 10.031480] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM [ 10.031489] iwlwifi :00:14.3: Found debug configuration: 0 [ 10.033948] iwlwifi :00:14.3: loaded firmware version 50.3e391d3e.0 op_mode iwlmvm [ 10.218293] iwlwifi :00:14.3: Detected Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [ 10.232843] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 10.235398] iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. [ 11.241180] iwlwifi :00:14.3: Collecting data: trigger 15 fired. [ 11.489274] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 11.489293] iwlwifi :00:14.3: Status: 0x, count: -673266569 [ 11.489303] iwlwifi :00:14.3: Loaded firmware version: 50.3e391d3e.0 [ 11.489315] iwlwifi :00:14.3: 0x90F1F96A | ADVANCED_SYSASSERT [ 11.489323] iwlwifi :00:14.3: 0x7A7986FC | trm_hw_status0 [ 11.489331] iwlwifi :00:14.3: 0x09E990EC | trm_hw_status1 [ 11.489338] iwlwifi :00:14.3: 0x3073F272 | branchlink2 [ 11.489345] iwlwifi :00:14.3: 0xD569005D | interruptlink1 [ 11.489352] iwlwifi :00:14.3: 0xFEA17D01 | interruptlink2 [ 11.489359] iwlwifi :00:14.3: 0x4BBD0C7B | data1 [ 11.489367] iwlwifi :00:14.3: 0xB33DAF15 | data2 [ 11.489375] iwlwifi :00:14.3: 0xC8E4188F | data3 [ 11.489382] iwlwifi :00:14.3: 0xDEC3F4B3 | beacon time [ 11.489389] iwlwifi :00:14.3: 0xD5B7AAC7 | tsf low [ 11.489395] iwlwifi :00:14.3: 0x00073EAF | tsf hi [ 11.489402] iwlwifi :00:14.3: 0xB943A8DA | time gp1 [ 11.489409] iwlwifi :00:14.3: 0x6CCF8627 | time gp2 [ 11.489417] iwlwifi :00:14.3: 0x7944BDC6 | uCode revision type [ 11.489424] iwlwifi :00:14.3: 0x3C9DCF39 | uCode version major [ 11.489431] iwlwifi :00:14.3: 0xAF537547 | uCode version minor [ 11.489439] iwlwifi :00:14.3: 0xBC11442E | hw version [ 11.489447] iwlwifi :00:14.3: 0x160C9445 | board version [ 11.489453] iwlwifi :00:14.3: 0x276F21F6 | hcmd [ 11.489460] iwlwifi :00:14.3: 0x022688AB | isr0 [ 11.489466] iwlwifi :00:14.3: 0xEBF64685 | isr1 [ 11.489473] iwlwifi :00:14.3: 0x9D16A85F | isr2 [ 11.489480] iwlwifi :00:14.3: 0x606C870F | isr3 [ 11.489488] iwlwifi :00:14.3: 0x1B3967BF | isr4 [ 11.489495] iwlwifi :00:14.3: 0xFFBCEAB8 | last cmd Id [ 11.489503] iwlwifi :00:14.3: 0xAEB80995 | wait_event [ 11.489512] iwlwifi :00:14.3: 0x95AD6DCD | l2p_control [ 11.489518] iwlwifi :00:14.3: 0x06D3D9B3 | l2p_duration [ 11.489526] iwlwifi :00:14.3: 0x51B4EEA2 | l2p_mhvalid [ 11.489533] iwlwifi :00:14.3: 0x51B8C323 | l2p_addr_match [ 11.489540] iwlwifi :00:14.3: 0x81E0114B | lmpm_pmg_sel [ 11.489548] iwlwifi :00:14.3: 0xF4D75F29 | timestamp [ 11.489555]
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Confirmed Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874359] Re: alsa/sof: kernel oops on the machine without Intel hdmi audio codec (a regression in the asoc machine driver)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874359 Title: alsa/sof: kernel oops on the machine without Intel hdmi audio codec (a regression in the asoc machine driver) Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: Please apply the fix for #1872569 first, then apply this patch. [Impact] The fix for #1872569 introduces a regression, the driver access a NULL pointer on the machiens without Intel hdmi audio codec. [Fix] pick a fixing patch from alsa/asoc repo, the patch doesn't assume the first rtd is for hda codec, it will look for that rtd through strstr() [Test Case] Boot the kenrel on those 2 Dell and 2 Lenovo machines which uses this driver, the audio could work. disable the intel hdmi audio codec through bios, the analogue audio still works [Regression Risk] Low, I have tested this patch Lenovo / Dell machines, they all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877958] Re: Do not treat unresolved test case in ftrace from ubuntu_kernel_selftests as failure
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877958 Title: Do not treat unresolved test case in ftrace from ubuntu_kernel_selftests as failure Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: == SRU Justification == There are some test cases in ftrace from ubuntu_kernel_selftests that would need some kernel configs to be enabled or have some special HW requirements: * https://pad.lv/1869347 - missing CONFIG_SAMPLE_TRACE_PRINTK=m * https://pad.lv/1869349 - missing CONFIG_SAMPLE_TRACE_PRINTK=m * https://pad.lv/1874198 - nproc > 1 If the requirement was not met, these test will fail with "unresolved" and return 1. So even these is no failed test case, the ftrace test will still be marked as "failed" with the presence of unresolved test: # # of passed: 28 # # of failed: 0 # # of unresolved: 1 # # of untested: 0 # # of unsupported: 58 # # of xfailed: 0 # # of undefined(test bug): 0 not ok 1 selftests: ftrace: ftracetest # exit=1 == Fix == * b730d668138c ("ftrace/selftest: make unresolved cases cause failure if --fail-unresolved set") This patch will only make unresolved test case return 1 if we ask it to fail with unresolved test case. It can be cherry-picked to kernels starting from Disco. For Bionic and Xenial it needs to be backported with some context adjustment as they're missing some other patches to the testing tool. == Test == With the patch applied, the ftrace test will not be marked as failed with the presence of unresolved test case: # # of passed: 28 # # of failed: 0 # # of unresolved: 1 # # of untested: 0 # # of unsupported: 58 # # of xfailed: 0 # # of undefined(test bug): 0 ok 1 selftests: ftrace: ftracetest == Regression Potential == Low, changes limited to testing tools, no actual impacts to our kernels. The worst case is to cause false negative in test reports, but in that case it's probably a test case issue since a failed case should be treated as a failed one, instead of unresolved. == Original Bug Report == There are some test cases in ftrace from ubuntu_kernel_selftests that would need some kernel configs to be enabled. bug 1869347 bug 1869349 We should not treat unresolved test case as a failure, as it's expected to fail with no correlated configs enabeled. https://github.com/torvalds/linux/commit/b730d668138cb3dd9ce78f8003986d1adae5523a #diff-33d74da785cbc5da20f71eb1af106d68 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1877958/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878897] Re: debian/scripts/file-downloader does not handle positive failures correctly
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878897 Title: debian/scripts/file-downloader does not handle positive failures correctly Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: Somehow we are not really correctly handling positive failures, 404 for example. Sigh. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881046] 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 1881046 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/1881046 Title: ASoC/amd: add audio driver for amd renoir Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: this bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1881046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881046] [NEW] ASoC/amd: add audio driver for amd renoir
Public bug reported: this bug is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: Incomplete ** Tags: originate-from-1874593 sutton ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: originate-from-1874593 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881046 Title: ASoC/amd: add audio driver for amd renoir Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: this bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1881046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 upload 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 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 More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876990] Re: zfs modules in Focal kernel taint kernel
@Jeff, not sure how we progress on this. Any comments? ** Changed in: linux (Ubuntu) Status: In Progress => 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/1876990 Title: zfs modules in Focal kernel taint kernel Status in linux package in Ubuntu: Incomplete Bug description: the ZFS modules in the shipping focal kernel do not contain the intree flag, and because of that I believe they are the cause of kernel tainting discovered during 20.04 certification testing. The output from a recent certification test run for 20.04: Kernel taint value is 4097 Taint bit value: 0 (proprietary module was loaded) Taint bit value: 12 (externally-built ('out-of-tree') module was loaded) Looking into modinfo for everything loaded at the time, it appears that the ZFS modules are loaded (even though we did not configure any ZFS filesystems), and that seems to be the root cause of the test failure. To test this, I checked /proc/sys/kernel/tainted and verified it was tainted. I then blacklisted all the ZFS related modules and rebooted, and then checked /proc/sys/kernel/tainted again and the kernel no longer shows as being tainted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879949] Re: Can not log in
Where can I mark that? What is the possible root cause? Sorry, I'm pretty inexperienced. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879949 Title: Can not log in Status in linux package in Ubuntu: Incomplete Bug description: I'm on Ubuntu 20.04. After upgrading from linux 5.4.0-26-generic to 5.4.0-31-generic I could not log in anymore. I was stuck in the display manager. Then I rebooted into the old kernel and sent these reports. I'm not sure if this is related but I can't put my display onto the correct resolution anymore. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jesko 3203 F pulseaudio /dev/snd/controlC1: jesko 3203 F pulseaudio /dev/snd/controlC2: jesko 3203 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 15:07:25 2020 InstallationDate: Installed on 2020-05-20 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B79 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=9f451f12-4a89-4dcc-9eca-97df16101efc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PLUS (MS-7B79) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.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: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.50:bd11/16/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B79:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPLUS(MS-7B79):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B79 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.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/1879949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879690] Re: Docker registry doesn't stay up and keeps restarting
This bug was fixed in the package linux - 5.4.0-33.37 --- linux (5.4.0-33.37) focal; urgency=medium * focal/linux: 5.4.0-33.37 -proposed tracker (LP: #1879926) * Docker registry doesn't stay up and keeps restarting (LP: #1879690) - Revert "UBUNTU: SAUCE: overlayfs: fix shitfs special-casing" - Revert "UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay" -- Kleber Sacilotto de Souza Thu, 21 May 2020 14:34:26 +0200 ** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] The change applied for bug 1857257 and its followup fix bug 1876645, which were released on focal and eoan -updates, introduced a regression on overlayfs, breaking docker snap. [Test case] See original bug report. [Fix] While we don't have a final fix the solution for now is to revert the following commits: UBUNTU: SAUCE: overlayfs: fix shitfs special-casing UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay [Regression potential] Low. Reverting these two commits will introduce back the issue reported on bug 1857257, but will fix the other use cases which was broken by the latest release. Original bug report. --- Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881015] 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/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 1877889] Re: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595
My e595 is my main develop machine, qt dev, lots of ssh connections, virtualbox + many firefox tabs with sometime youtube vids and many thunderbird imap accounts. And with the freeze is not even sysreq+"reisub" possible. The e595 not have a rs232 so i cannot console to second machine, what i would do to see what happen :-( And i think non of the kernel can use ttyusb for kernel console because ttyusb is always "m" not "y" compiled. But i didn't try yet. Maybe next days i will try ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877889 Title: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595 Status in linux package in Ubuntu: Confirmed Bug description: Hello, I see occasional hangs on boot. The hangs occur after entering the LUKS decryption password for the root filesystem, and before the login screen is displayed. The "/boot" filesystem is not encrypted, so the initramfs is loading fine etc. The hangs are intermittent. Sometimes I don't see a hang for 10+ boots in a row, and sometimes I'll get a hang 5 times in a row. When the hang occurs the boot splash screen is visible (not the login screen). The system is still responsive to SysRq keys, so I can somewhat safely issue S+U+S+B sequence to try booting again without corrupting much. I have tried removing the "quiet splash" kernel parameters that are enabled by default on Ubuntu desktop to see if any interesting messages occur that way. So far however I have not experienced a hang with "quiet splash" removed. This system is a Lenovo E595 (Ryzen 3500U) with the latest BIOS from Lenovo installed (v1.16), running Ubuntu 20.04 desktop. I am submitting this bug using `ubuntu-bug linux-image-generic`, but I don't know for sure if this is a kernel issue or something else. I suspect my bug might be the same as this one already reported ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873594 ), but I'm filing my own anyway as a means to capture more details of my system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.29.34 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/controlC1: paul 2507 F pulseaudio /dev/snd/controlC0: paul 2507 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 20:09:53 2020 MachineType: LENOVO 20NFCTO1WW ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=f466d4ea-c251-4721-b071-bd70c82f00e1 ro rootflags=subvol=@ splash quiet 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-04-24 (15 days ago) 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/1877889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874444] Re: Bionic ubuntu ethtool doesn't check ring parameters boundaries
I was able to verify it on AWS using the test procedure on description, in the following linux-aws proposed kernels: 4.4.0-1108-aws (Xenial / 16.04) 4.15.0-1068-aws (Bionic / 18.04) Also, I've done a code inspection in generic proposed kernels (4.4.0-180/Xenial and 4.15.0-102/Bionic) and the patch is there, hence marking it as verified for both kernels. Cheers, Guilherme ** Tags removed: verification-needed-bionic verification-needed-xenial ** Tags added: verification-done-bionic verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/187 Title: Bionic ubuntu ethtool doesn't check ring parameters boundaries Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] * There's a bad behavior in the ena driver ringparam setting on kernels 4.4 and 4.15, if an invalid ringparam is provided to ethtool. * Upstream Linux kernel implemented ring parameter boundaries check in commit: 37e2d99b59c4 ("ethtool: Ensure new ring parameters are within bounds during SRINGPARAM") [ git.kernel.org/linus/37e2d99b59c4 ]. Due to this commit, the community doesn't usually allow ring parameter boundary checks in driver code. * Xenial/Bionic kernels don't include this patch, and some network drivers (like ena) rely on this patch for boundary checking of ring params. So, we are hereby requesting the commit inclusion in these kernel versions. [Test case] 1. In AWS, create a new c5.4xlarge instance with the Ubuntu 18.04 official ami (uses the ENA network driver) and update to latest kernel/reboot. 2. Run ethtool -g ens5 output: Ring parameters for ens5: Pre-set maximums: RX: 16384 RX Mini: 0 RX Jumbo: 0 TX: 1024 Current hardware settings: RX: 1024 RX Mini: 0 RX Jumbo: 0 TX: 1024 3. Change the TX/RX ring size to a legal number within boundaries - works! 4. Change the TX/RX ring size to an illegal number (such as 2048 for TX) with the command - "sudo ethtool -G ens5 tx 2048". Expected behavior - "Cannot set device ring parameters: Invalid argument" Actual behavior - causes a driver hang since boundaries are not checked by ethtool, effectively hanging the instance (given that AWS has no console to allow system manipulation). [Regression Potential] Since that the commit is present in kernels v4.16+ (including Ubuntu) and is quite small and self-contained, the regression risk is very reduced. One potential "regression" would be if some driver has bugs and provide bad values on get_ringparams, then the validation would be broken (allowing illegal values or refusing legal ones), but this wouldn't be a regression in the hereby proposed patch itself, it'd be only exposed by the patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881015] Re: Fn Lock light does not come on to indicate when Fn Lock is enabled
( I also posted this to Ask Ubuntu: https://askubuntu.com/questions/1243284/how-do-i-get-the-lenovo-fn-lock- light-to-work-under-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/1881015 Title: Fn Lock light does not come on to indicate when Fn Lock is enabled Status in linux package in Ubuntu: New 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 1881015] [NEW] Fn Lock light does not come on to indicate when Fn Lock is enabled
Public bug reported: 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881015 Title: Fn Lock light does not come on to indicate when Fn Lock is enabled Status in linux package in Ubuntu: New 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 )
[Kernel-packages] [Bug 1880666] Re: Power management: does not suspend
** Description changed: 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: at least sometimes; used to work at least sometimes with - this release. + 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 + 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. + 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 + 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. -- You 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: Confirmed 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 1880834] Re: qeth: utilize virtual MAC for Layer2 OSD devices
Thanks for sharing the two backports, they apply nicely on bionic master-next. Unblocking ticket ... ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: ubuntu-z-systems Status: Incomplete => Triaged ** Changed in: ubuntu-z-systems Importance: Undecided => High -- You 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 1093795] Re: Backlight does not work on sony vaio sve1112
** Description changed: Using the default ati open source driver hotkeys are not working, echo commands are not working but files exist in sys/class/backlight. I used acpi_backlight=vendor , legacy and also the video.use_bios_initial_backlight=0 with no effect. Reverse mainline kernel version bisecting revealed the fix landed in the transition from 3.6.11 raring to 3.7-rc1 quantal. - ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-21-generic 3.5.0-21.32 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: micdhack 1643 F pulseaudio - /dev/snd/controlC0: micdhack 1643 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: mt 1643 F pulseaudio + /dev/snd/controlC0: mt 1643 F pulseaudio Date: Wed Dec 26 13:40:51 2012 HibernationDevice: RESUME=UUID=b9ded35c-c251-435b-898e-e2827835b63a InstallationDate: Installed on 2012-12-25 (0 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Sony Corporation SVE1112M1EW MarkForUpload: True ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic.efi.signed root=UUID=ff2bb0f9-b45a-4e72-871e-9463d0ab0c66 ro quiet splash acpi_osi=Linux acpi_backlight=legacy vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.5.0-21-generic N/A - linux-backports-modules-3.5.0-21-generic N/A - linux-firmware1.95 + linux-restricted-modules-3.5.0-21-generic N/A + linux-backports-modules-3.5.0-21-generic N/A + linux-firmware1.95 SourcePackage: linux StagingDrivers: rts_pstor UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0120D8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0120D8:bd08/22/2012:svnSonyCorporation:pnSVE1112M1EW:pvrC60B8NZ6:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVE1112M1EW dmi.product.version: C60B8NZ6 dmi.sys.vendor: Sony Corporation -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1093795 Title: Backlight does not work on sony vaio sve1112 Status in linux package in Ubuntu: Fix Released Bug description: Using the default ati open source driver hotkeys are not working, echo commands are not working but files exist in sys/class/backlight. I used acpi_backlight=vendor , legacy and also the video.use_bios_initial_backlight=0 with no effect. Reverse mainline kernel version bisecting revealed the fix landed in the transition from 3.6.11 raring to 3.7-rc1 quantal. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-21-generic 3.5.0-21.32 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mt 1643 F pulseaudio /dev/snd/controlC0: mt 1643 F pulseaudio Date: Wed Dec 26 13:40:51 2012 HibernationDevice: RESUME=UUID=b9ded35c-c251-435b-898e-e2827835b63a InstallationDate: Installed on 2012-12-25 (0 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Sony Corporation SVE1112M1EW MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic.efi.signed root=UUID=ff2bb0f9-b45a-4e72-871e-9463d0ab0c66 ro quiet splash acpi_osi=Linux acpi_backlight=legacy vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-21-generic N/A linux-backports-modules-3.5.0-21-generic N/A linux-firmware1.95 SourcePackage: linux StagingDrivers: rts_pstor UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0120D8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony
[Kernel-packages] [Bug 1877889] Re: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595
@viperomega It's interesting that you mention freezes at times other than bootup. I've never experienced that problem on this laptop. Only the hang on boot issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877889 Title: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595 Status in linux package in Ubuntu: Confirmed Bug description: Hello, I see occasional hangs on boot. The hangs occur after entering the LUKS decryption password for the root filesystem, and before the login screen is displayed. The "/boot" filesystem is not encrypted, so the initramfs is loading fine etc. The hangs are intermittent. Sometimes I don't see a hang for 10+ boots in a row, and sometimes I'll get a hang 5 times in a row. When the hang occurs the boot splash screen is visible (not the login screen). The system is still responsive to SysRq keys, so I can somewhat safely issue S+U+S+B sequence to try booting again without corrupting much. I have tried removing the "quiet splash" kernel parameters that are enabled by default on Ubuntu desktop to see if any interesting messages occur that way. So far however I have not experienced a hang with "quiet splash" removed. This system is a Lenovo E595 (Ryzen 3500U) with the latest BIOS from Lenovo installed (v1.16), running Ubuntu 20.04 desktop. I am submitting this bug using `ubuntu-bug linux-image-generic`, but I don't know for sure if this is a kernel issue or something else. I suspect my bug might be the same as this one already reported ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873594 ), but I'm filing my own anyway as a means to capture more details of my system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.29.34 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/controlC1: paul 2507 F pulseaudio /dev/snd/controlC0: paul 2507 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 20:09:53 2020 MachineType: LENOVO 20NFCTO1WW ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=f466d4ea-c251-4721-b071-bd70c82f00e1 ro rootflags=subvol=@ splash quiet 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-04-24 (15 days ago) 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/1877889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
Note: My comment (#34) above is in VirtualBox 6.1.8 and without the Serial port redirection mentioned in comment #7. With the serial port redirection everything seems to work properly for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Using `ubuntu/focal64` version `20200423.0.0`, the boot process is extremely slow and the box always reboots once before completing a successful boot. With default settings, this causes a timeout in Vagrant waiting for SSH to be available. Setting a long enough timeout it does eventually boot successfully. For comparison, `ubuntu/bionic64` boots successfully in roughly 10 seconds on my machine. This appears to be the big hang-up: Apr 23 14:00:12 ubuntu-focal kernel: [0.219784] printk: console [tty1] enabled Apr 23 14:00:12 ubuntu-focal kernel: [ 76.448371] printk: console [ttyS0] enabled I have a hard time telling where exactly it reboots because my /var/log/syslog only ends up with the second boot. I can watch it in Virtualbox though and it suddenly reboots, then the second boot process runs to completion. The long delay shown above happens both times making the total time to a successful boot very long. Here is the head of my /var/log/syslog: Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Remount Root and Kernel File Systems. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Uncomplicated firewall. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting FUSE Control File System... Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting Kernel Configuration File System... Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Flush Journal to Persistent Storage... Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Load/Save Random Seed... Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Apply Kernel Variables... Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create System Users... Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished udev Coldplug all Devices. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted FUSE Control File System. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted Kernel Configuration File System. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Flush Journal to Persistent Storage. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Load/Save Random Seed. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Apply Kernel Variables. Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating group systemd-coredump with gid 999. Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating user systemd-coredump (systemd Core Dumper) with uid 999 and gid 999. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Wait for Complete Device Initialization... Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create System Users. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create Static Device Nodes in /dev... Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create Static Device Nodes in /dev. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Kernel Device Manager... Apr 23 14:00:12 ubuntu-focal systemd[1]: Started udev Kernel Device Manager. Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Linux version 5.4.0-26-generic (buildd@lcy01-amd64-029) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 ( Ubuntu 5.4.0-26.30-generic 5.4.30) Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=PARTUUID=fac6339f-01 ro console=tty1 console=ttyS0 Subsequent boots are also slow but don't seem to have the extra reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 7 16:02 seq crw-rw 1 root audio 116, 33 May 7 16:02 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: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or
[Kernel-packages] [Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
Interestingly, using the VirtualBox GUI to boot a VM created from the 20200522.0.0 vagrant box causes the entire VirtualBox GUI to hang. The only way out of it is to force quit the VM processes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Using `ubuntu/focal64` version `20200423.0.0`, the boot process is extremely slow and the box always reboots once before completing a successful boot. With default settings, this causes a timeout in Vagrant waiting for SSH to be available. Setting a long enough timeout it does eventually boot successfully. For comparison, `ubuntu/bionic64` boots successfully in roughly 10 seconds on my machine. This appears to be the big hang-up: Apr 23 14:00:12 ubuntu-focal kernel: [0.219784] printk: console [tty1] enabled Apr 23 14:00:12 ubuntu-focal kernel: [ 76.448371] printk: console [ttyS0] enabled I have a hard time telling where exactly it reboots because my /var/log/syslog only ends up with the second boot. I can watch it in Virtualbox though and it suddenly reboots, then the second boot process runs to completion. The long delay shown above happens both times making the total time to a successful boot very long. Here is the head of my /var/log/syslog: Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Remount Root and Kernel File Systems. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Uncomplicated firewall. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting FUSE Control File System... Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting Kernel Configuration File System... Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Flush Journal to Persistent Storage... Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Load/Save Random Seed... Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Apply Kernel Variables... Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create System Users... Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished udev Coldplug all Devices. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted FUSE Control File System. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted Kernel Configuration File System. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Flush Journal to Persistent Storage. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Load/Save Random Seed. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Apply Kernel Variables. Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating group systemd-coredump with gid 999. Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating user systemd-coredump (systemd Core Dumper) with uid 999 and gid 999. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Wait for Complete Device Initialization... Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create System Users. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create Static Device Nodes in /dev... Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create Static Device Nodes in /dev. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Kernel Device Manager... Apr 23 14:00:12 ubuntu-focal systemd[1]: Started udev Kernel Device Manager. Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Linux version 5.4.0-26-generic (buildd@lcy01-amd64-029) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 ( Ubuntu 5.4.0-26.30-generic 5.4.30) Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=PARTUUID=fac6339f-01 ro console=tty1 console=ttyS0 Subsequent boots are also slow but don't seem to have the extra reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 7 16:02 seq crw-rw 1 root audio 116, 33 May 7 16:02 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: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or
[Kernel-packages] [Bug 1877425] Re: linux-azure: Enable FSGSBASE instructions to support SGX
** Changed in: linux-azure (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1877425 Title: linux-azure: Enable FSGSBASE instructions to support SGX Status in linux-azure package in Ubuntu: In Progress Status in linux-azure-4.15 package in Ubuntu: In Progress Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: In Progress Status in linux-azure source package in Eoan: Fix Committed Status in linux-azure-4.15 source package in Eoan: Invalid Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-4.15 source package in Focal: Invalid Bug description: X86 has instructions (RDFSBASE, RDGSBASE, WRFSBASE, and WRGSBASE) to support read/write of the FS/GS bases. Linux doesn't allow user mode code to execute these instructions by default. These instructions can be enabled for user mode by setting the 16th control bit of the CR4 register. Since only protected mode can modify the control registers, application programs and operating-system procedures (running at privilege levels 1, 2, or 3) are prevented from reading or loading the control registers. The kernel patch sets this CR4 register and handles the context switching to account for the fact that user mode can now modify the FS/GS base. A recent news article that talks about the performance benefits: https://phoronix.com/scan.php?page=news_item=Intel-FSGSBASE- Linux-2020. Another news article covers the performance information in a lot more detail by running a number of performance tests: https://www.phoronix.com/scan.php?page=article=linux-wip- fsgsbase=1 Patch set: https://lkml.org/lkml/2019/10/4/725 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1877425/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880835] Re: pulse audio hangs in kernel call
Now The system seems working just fine. I have to run a long test to see if the problem occurs again ** Attachment added: "Alsa Output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880835/+attachment/5377480/+files/alsa-info.txt.WzjGHXBkFd -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880835 Title: pulse audio hangs in kernel call Status in linux package in Ubuntu: Incomplete Bug description: there is no audio device accessible any more and pulse-audio process can not be terminated in kernel log there is such a output: This makes the complete audio unstable in the laptop. I think it is started to happen when I installed Nvidia driver and there is an external monitor attached with DP audio device. [ 364.150644] INFO: task pulseaudio:2183 blocked for more than 120 seconds. [ 364.150646] Tainted: P OE 5.4.0-31-generic #35-Ubuntu [ 364.150647] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 364.150647] pulseaudio D0 2183 2175 0x4120 [ 364.150649] Call Trace: [ 364.150653] __schedule+0x2e3/0x740 [ 364.150655] ? dma_pte_clear_level+0x142/0x190 [ 364.150655] schedule+0x42/0xb0 [ 364.150656] schedule_timeout+0x203/0x2f0 [ 364.150657] wait_for_completion+0xb1/0x120 [ 364.150659] ? wake_up_q+0x70/0x70 [ 364.150663] fw_run_transaction+0xdc/0x110 [firewire_core] [ 364.150665] ? fw_core_handle_bus_reset+0x440/0x440 [firewire_core] [ 364.150666] ? free_iova_fast+0x18/0x30 [ 364.150667] ? close_transaction+0x110/0x110 [firewire_core] [ 364.150668] ? intel_unmap+0xd9/0x1c0 [ 364.150670] ? transmit_phy_packet_callback+0x20/0x20 [firewire_core] [ 364.150671] snd_fw_transaction+0xbc/0x110 [snd_firewire_lib] [ 364.150673] ? avc_general_get_plug_info+0x100/0x100 [snd_firewire_lib] [ 364.150674] pcr_modify+0x65/0x100 [snd_firewire_lib] [ 364.150675] cmp_connection_break+0x37/0x50 [snd_firewire_lib] [ 364.150677] snd_oxfw_stream_start_duplex+0x1ee/0x2e0 [snd_oxfw] [ 364.150678] ? wait_woken+0x80/0x80 [ 364.150679] pcm_capture_prepare+0x26/0x50 [snd_oxfw] [ 364.150682] snd_pcm_do_prepare+0x1e/0x30 [snd_pcm] [ 364.150684] snd_pcm_action_single+0x3c/0x80 [snd_pcm] [ 364.150686] snd_pcm_action_nonatomic+0x6e/0x80 [snd_pcm] [ 364.150687] snd_pcm_prepare+0x6a/0x90 [snd_pcm] [ 364.150689] snd_pcm_common_ioctl+0x28c/0xc00 [snd_pcm] [ 364.150691] snd_pcm_ioctl+0x27/0x40 [snd_pcm] [ 364.150692] do_vfs_ioctl+0x407/0x670 [ 364.150694] ? __secure_computing+0x42/0xe0 [ 364.150694] ksys_ioctl+0x67/0x90 [ 364.150695] __x64_sys_ioctl+0x1a/0x20 [ 364.150697] do_syscall_64+0x57/0x190 [ 364.150698] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 364.150699] RIP: 0033:0x7f0bbfa1a37b [ 364.150701] Code: Bad RIP value. [ 364.150701] RSP: 002b:7ffed915d308 EFLAGS: 0202 ORIG_RAX: 0010 [ 364.150702] RAX: ffda RBX: 5607c7b63de0 RCX: 7f0bbfa1a37b [ 364.150703] RDX: RSI: 4140 RDI: 006e [ 364.150703] RBP: 5607c7b63bb0 R08: R09: 1000 [ 364.150703] R10: 0004 R11: 0202 R12: 5607c7b63de0 [ 364.150704] R13: 7ffed915d6f0 R14: R15: 7ffed915d480 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_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 27 10:07:13 2020 InstallationDate: Installed on 2020-02-22 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) MachineType: Dell Inc. Precision 7540 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=7a5890f6-2724-480a-8fa7-778d07cd929d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. 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/12/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0T2FXT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd03/12/2020:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0T2FXT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540
[Kernel-packages] [Bug 1880835] Re: pulse audio hangs in kernel call
OK I have started to test it now. My cernel is now: $ uname -a Linux DEM-RSZABO-U20 5.7.0-050700rc7-generic #202005242331 SMP Sun May 24 23:33:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux with self compiled and patched nvida driver (the latest driver kernel module with the mainline kernel does not compile without a patch see (https://gitlab.com/snippets/1965550) ): So Now I run Nvidia driver and external monitor over the thunderbolt 3 where also the FireWire interface is running. Nvidia $ nvidia-smi -a ==NVSMI LOG== Timestamp : Wed May 27 19:57:17 2020 Driver Version : 440.82 CUDA Version: 10.2 Attached GPUs : 1 GPU :01:00.0 Product Name: Quadro T2000 Product Brand : Quadro Display Mode: Enabled Display Active : Enabled Persistence Mode: Disabled Accounting Mode : Disabled Accounting Mode Buffer Size : 4000 Driver Model Current : N/A Pending : N/A Serial Number : N/A GPU UUID: GPU-e970a3f0-ccb4-aca2-c0bb-c63d35d10fdc Minor Number: 0 VBIOS Version : 90.17.1A.00.A3 MultiGPU Board : No Board ID: 0x100 GPU Part Number : N/A Inforom Version Image Version : G001..02.04 OEM Object : 1.1 ECC Object : N/A Power Management Object : N/A GPU Operation Mode Current : N/A Pending : N/A GPU Virtualization Mode Virtualization Mode : None Host VGPU Mode : N/A IBMNPU Relaxed Ordering Mode : N/A PCI Bus : 0x01 Device : 0x00 Domain : 0x Device Id : 0x1FB810DE Bus Id : :01:00.0 Sub System Id : 0x09261028 GPU Link Info PCIe Generation Max : 3 Current : 1 Link Width Max : 16x Current : 16x Bridge Chip Type: N/A Firmware: N/A Replays Since Reset : 0 Replay Number Rollovers : 0 Tx Throughput : 1000 KB/s Rx Throughput : 6000 KB/s Fan Speed : N/A Performance State : P8 Clocks Throttle Reasons Idle: Active Applications Clocks Setting : Not Active SW Power Cap: Not Active HW Slowdown : Not Active HW Thermal Slowdown : Not Active HW Power Brake Slowdown : Not Active Sync Boost : Not Active SW Thermal Slowdown : Not Active Display Clock Setting : Not Active FB Memory Usage Total : 3911 MiB Used: 976 MiB Free: 2935 MiB BAR1 Memory Usage Total : 256 MiB Used: 7 MiB Free: 249 MiB Compute Mode: Default Utilization Gpu : 2 % Memory : 12 % Encoder : 0 % Decoder : 0 % Encoder Stats Active Sessions : 0 Average FPS : 0 Average Latency : 0 FBC Stats Active Sessions : 0 Average FPS : 0 Average Latency : 0 Ecc Mode Current : N/A Pending : N/A ECC Errors Volatile SRAM Correctable: N/A SRAM Uncorrectable : N/A DRAM Correctable: N/A DRAM Uncorrectable : N/A Aggregate SRAM Correctable: N/A SRAM Uncorrectable : N/A DRAM Correctable: N/A DRAM Uncorrectable : N/A Retired Pages Single Bit ECC : N/A Double Bit ECC : N/A Pending Page Blacklist : N/A Temperature GPU Current Temp: 48 C GPU Shutdown Temp : 98 C GPU Slowdown Temp : 93 C GPU Max Operating Temp : 87 C
[Kernel-packages] [Bug 1880834] Backport of "s390/qeth: improve fallback to random MAC address"
--- Comment (attachment only) From julian.wiedm...@de.ibm.com 2020-05-27 12:51 EDT--- ** Attachment added: "Backport of "s390/qeth: improve fallback to random MAC address"" https://bugs.launchpad.net/bugs/1880834/+attachment/5377433/+files/0001-s390-qeth-improve-fallback-to-random-MAC-address.patch -- You 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: Incomplete Status in linux package in Ubuntu: Incomplete 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 1880834] Backport of "s390/qeth: utilize virtual MAC for Layer2 OSD devices"
--- Comment (attachment only) From julian.wiedm...@de.ibm.com 2020-05-27 12:52 EDT--- ** Attachment added: "Backport of "s390/qeth: utilize virtual MAC for Layer2 OSD devices"" https://bugs.launchpad.net/bugs/1880834/+attachment/5377434/+files/0002-s390-qeth-utilize-virtual-MAC-for-Layer2-OSD-devices.patch -- You 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: Incomplete Status in linux package in Ubuntu: Incomplete 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 1865988] Re: Performing function level reset of AMD onboard USB and audio devices causes system lockup
Per offline discuss, we will help SRU this patch so that it won't miss current release cycle. -- You 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
[Kernel-packages] [Bug 1880639] Re: O wi-fi desconecta automaticamente
** Tags added: hwe-networking-wifi ** Summary changed: - O wi-fi desconecta automaticamente + Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] O wi-fi desconecta automaticamente -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880639 Title: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] O wi-fi desconecta automaticamente Status in linux package in Ubuntu: Confirmed Bug description: Atualizei para a versão 20.04 e desde então meu notebook vem apresentando erro, desconectando automaticamente minhas conexões wi- fi. 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/controlC0: josimar1912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 01:17:39 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-20180608-47+loki-n3-v3-kbl+X28 InstallationDate: Installed on 2020-01-17 (129 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3584 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=127ffefc-873d-410c-8d99-aaf1637e14dc ro mem_sleep_default=deep 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: Upgraded to focal on 2020-05-11 (15 days ago) dmi.bios.date: 07/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05RCHV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd07/10/2019:svnDellInc.:pnInspiron3584:pvr:rvnDellInc.:rn05RCHV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3584 dmi.product.sku: 08D1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
Re #28 I have both problems using the 20200522.0.0 image on a Windows host. Host specs: Lenovo Thinkpad P50, Intel Core i7-6700HQ, Windows 10 v1909, tried with both VirtualBox 6.0.4 and 6.1.8. Full details at https://askubuntu.com/questions/1243582/unable-to-boot- official-vagrant-boxes-for-20-04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874453 Title: ubuntu/focal64 very slow to boot and reboots once Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Using `ubuntu/focal64` version `20200423.0.0`, the boot process is extremely slow and the box always reboots once before completing a successful boot. With default settings, this causes a timeout in Vagrant waiting for SSH to be available. Setting a long enough timeout it does eventually boot successfully. For comparison, `ubuntu/bionic64` boots successfully in roughly 10 seconds on my machine. This appears to be the big hang-up: Apr 23 14:00:12 ubuntu-focal kernel: [0.219784] printk: console [tty1] enabled Apr 23 14:00:12 ubuntu-focal kernel: [ 76.448371] printk: console [ttyS0] enabled I have a hard time telling where exactly it reboots because my /var/log/syslog only ends up with the second boot. I can watch it in Virtualbox though and it suddenly reboots, then the second boot process runs to completion. The long delay shown above happens both times making the total time to a successful boot very long. Here is the head of my /var/log/syslog: Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Remount Root and Kernel File Systems. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Uncomplicated firewall. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting FUSE Control File System... Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting Kernel Configuration File System... Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Flush Journal to Persistent Storage... Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Load/Save Random Seed... Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Apply Kernel Variables... Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create System Users... Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished udev Coldplug all Devices. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted FUSE Control File System. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted Kernel Configuration File System. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Flush Journal to Persistent Storage. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Load/Save Random Seed. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Apply Kernel Variables. Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating group systemd-coredump with gid 999. Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating user systemd-coredump (systemd Core Dumper) with uid 999 and gid 999. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Wait for Complete Device Initialization... Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create System Users. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create Static Device Nodes in /dev... Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create Static Device Nodes in /dev. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Kernel Device Manager... Apr 23 14:00:12 ubuntu-focal systemd[1]: Started udev Kernel Device Manager. Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Linux version 5.4.0-26-generic (buildd@lcy01-amd64-029) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 ( Ubuntu 5.4.0-26.30-generic 5.4.30) Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=PARTUUID=fac6339f-01 ro console=tty1 console=ttyS0 Subsequent boots are also slow but don't seem to have the extra reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 7 16:02 seq crw-rw 1 root audio 116, 33 May 7 16:02 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: CRDA: N/A
[Kernel-packages] [Bug 1879949] Re: Can not log in
Sorry, just mark the possible root cause first for further analysis for myself and for anyone who's interested. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879949 Title: Can not log in Status in linux package in Ubuntu: Incomplete Bug description: I'm on Ubuntu 20.04. After upgrading from linux 5.4.0-26-generic to 5.4.0-31-generic I could not log in anymore. I was stuck in the display manager. Then I rebooted into the old kernel and sent these reports. I'm not sure if this is related but I can't put my display onto the correct resolution anymore. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jesko 3203 F pulseaudio /dev/snd/controlC1: jesko 3203 F pulseaudio /dev/snd/controlC2: jesko 3203 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 15:07:25 2020 InstallationDate: Installed on 2020-05-20 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B79 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=9f451f12-4a89-4dcc-9eca-97df16101efc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PLUS (MS-7B79) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.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: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.50:bd11/16/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B79:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPLUS(MS-7B79):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B79 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.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/1879949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Problem continues in 5.4.0-31 kernel version -- You 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 More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880975] [NEW] Request to include two NUMA related commits in Azure kernels
Public bug reported: Microsoft would like to request the following two commits in all releases supported on Azure: 999dd956d838 ("PCI: hv: Add support for protocol 1.3 and support PCI_BUS_RELATIONS2") f9ad0f361cf3 ("PCI: hv: Decouple the func definition in hv_dr_state from VSP message") These two commits will add support for PCI protocol version 1.3. This will allow the host to pass NUMA node information for devices on the bus. Currently it is assumed the NUMA node is 0, which these patches will correct. This functionality will provide an increase in performance, especially for HPC and AI workloads. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1880975 Title: Request to include two NUMA related commits in Azure kernels Status in linux-azure package in Ubuntu: New Bug description: Microsoft would like to request the following two commits in all releases supported on Azure: 999dd956d838 ("PCI: hv: Add support for protocol 1.3 and support PCI_BUS_RELATIONS2") f9ad0f361cf3 ("PCI: hv: Decouple the func definition in hv_dr_state from VSP message") These two commits will add support for PCI protocol version 1.3. This will allow the host to pass NUMA node information for devices on the bus. Currently it is assumed the NUMA node is 0, which these patches will correct. This functionality will provide an increase in performance, especially for HPC and AI workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Hi Ryan, Sorry, I couldn't look at this earlier, but can put some cycles this week. I'm looking at the stack trace, crashdump, and the offending patch. Thanks again for your work on this. cheers, Mauricio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: [focal] disk I/O performance regression
Note that to rule out any hardware configuration/malfunction issue between the two hosts I have re-run the tests on the exact same machine used for the non-performant Focal tests with good performance for Bionic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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
[Kernel-packages] [Bug 1880835] Re: pulse audio hangs in kernel call
Thanks I try it out and come back with the result. Thanks for the prompt response -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880835 Title: pulse audio hangs in kernel call Status in linux package in Ubuntu: Incomplete Bug description: there is no audio device accessible any more and pulse-audio process can not be terminated in kernel log there is such a output: This makes the complete audio unstable in the laptop. I think it is started to happen when I installed Nvidia driver and there is an external monitor attached with DP audio device. [ 364.150644] INFO: task pulseaudio:2183 blocked for more than 120 seconds. [ 364.150646] Tainted: P OE 5.4.0-31-generic #35-Ubuntu [ 364.150647] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 364.150647] pulseaudio D0 2183 2175 0x4120 [ 364.150649] Call Trace: [ 364.150653] __schedule+0x2e3/0x740 [ 364.150655] ? dma_pte_clear_level+0x142/0x190 [ 364.150655] schedule+0x42/0xb0 [ 364.150656] schedule_timeout+0x203/0x2f0 [ 364.150657] wait_for_completion+0xb1/0x120 [ 364.150659] ? wake_up_q+0x70/0x70 [ 364.150663] fw_run_transaction+0xdc/0x110 [firewire_core] [ 364.150665] ? fw_core_handle_bus_reset+0x440/0x440 [firewire_core] [ 364.150666] ? free_iova_fast+0x18/0x30 [ 364.150667] ? close_transaction+0x110/0x110 [firewire_core] [ 364.150668] ? intel_unmap+0xd9/0x1c0 [ 364.150670] ? transmit_phy_packet_callback+0x20/0x20 [firewire_core] [ 364.150671] snd_fw_transaction+0xbc/0x110 [snd_firewire_lib] [ 364.150673] ? avc_general_get_plug_info+0x100/0x100 [snd_firewire_lib] [ 364.150674] pcr_modify+0x65/0x100 [snd_firewire_lib] [ 364.150675] cmp_connection_break+0x37/0x50 [snd_firewire_lib] [ 364.150677] snd_oxfw_stream_start_duplex+0x1ee/0x2e0 [snd_oxfw] [ 364.150678] ? wait_woken+0x80/0x80 [ 364.150679] pcm_capture_prepare+0x26/0x50 [snd_oxfw] [ 364.150682] snd_pcm_do_prepare+0x1e/0x30 [snd_pcm] [ 364.150684] snd_pcm_action_single+0x3c/0x80 [snd_pcm] [ 364.150686] snd_pcm_action_nonatomic+0x6e/0x80 [snd_pcm] [ 364.150687] snd_pcm_prepare+0x6a/0x90 [snd_pcm] [ 364.150689] snd_pcm_common_ioctl+0x28c/0xc00 [snd_pcm] [ 364.150691] snd_pcm_ioctl+0x27/0x40 [snd_pcm] [ 364.150692] do_vfs_ioctl+0x407/0x670 [ 364.150694] ? __secure_computing+0x42/0xe0 [ 364.150694] ksys_ioctl+0x67/0x90 [ 364.150695] __x64_sys_ioctl+0x1a/0x20 [ 364.150697] do_syscall_64+0x57/0x190 [ 364.150698] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 364.150699] RIP: 0033:0x7f0bbfa1a37b [ 364.150701] Code: Bad RIP value. [ 364.150701] RSP: 002b:7ffed915d308 EFLAGS: 0202 ORIG_RAX: 0010 [ 364.150702] RAX: ffda RBX: 5607c7b63de0 RCX: 7f0bbfa1a37b [ 364.150703] RDX: RSI: 4140 RDI: 006e [ 364.150703] RBP: 5607c7b63bb0 R08: R09: 1000 [ 364.150703] R10: 0004 R11: 0202 R12: 5607c7b63de0 [ 364.150704] R13: 7ffed915d6f0 R14: R15: 7ffed915d480 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_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 27 10:07:13 2020 InstallationDate: Installed on 2020-02-22 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) MachineType: Dell Inc. Precision 7540 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=7a5890f6-2724-480a-8fa7-778d07cd929d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. 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/12/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0T2FXT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd03/12/2020:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0T2FXT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880835/+subscriptions --
[Kernel-packages] [Bug 1853044] Re: 5.3.0-23-generic causes fans to spin when idle
There are nearly 600 commits between the working and non-working kernel. Rather than work on ~8-9 bisects steps, I've built 5 test kernels that just the relevant i915 driver commits reverted between the working and broken kernel. I've put the .debs at the following location: https://kernel.ubuntu.com/~cking/lp-1853044/ Please can you test the kernels in https://kernel.ubuntu.com/~cking/lp-1853044/revert1/ first. Install the kernel, reboot into it, and check it is the correct one using: uname -r Please work through the kernels in revert1 through to revert5 one by one (install, reboot, test for a while) and let me know which ones work fine and which ones cause the fan to kick in because of overheating. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853044 Title: 5.3.0-23-generic causes fans to spin when idle Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: "drm/i915/gen8+: Add RC6 CTX corruption WA" makes it effectively impossible to enter RC6 for some Intel GPUs when a display server is running. This results in increased energy usage and temperature. Fix: Upstream has changed too much to make the fixes there applicable, but Chris Wilson has provided a patch for 5.3, here: https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 Test Case: See test results below. On an affected machine powertop will show increased RC6 usage on an idle desktop after the patch, and other symptoms of excessive power use should also subside. Regression Potential: The 5.3 patch is pretty straightforward, and only adds running of an existing delayed worker to retire GPU requests. No regressions have been reported in testing so far. --- After upgrading to 5.3.0-23-generic the fans in my machine don't stop running. They always sound like something is utilizing CPU - even with no applications running after boot. If I boot back to 5.3.0-19-generic it's fine. My microcode version is reported as 0xd4 and iucode-tool reports: iucode-tool: system has processor(s) with signature 0x000506e3 Let me know if you need anything else. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 2898 F pulseaudio /dev/snd/pcmC2D0p: dean 2898 F...m pulseaudio /dev/snd/controlC0: dean 2898 F pulseaudio /dev/snd/controlC1: dean 2898 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 18 13:03:34 2019 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (482 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-07-19 (121 days ago) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880623] Re: linux-firmware: generate the symbollink of sof-hda-generic-2ch/4ch.tplg for bionic
** Summary changed: - linux-firmware: generate the symbollink of sof-hda-generic-2ch/4ch.tplg for bionic and eoan + linux-firmware: generate the symbollink of sof-hda-generic-2ch/4ch.tplg for bionic ** No longer affects: linux-firmware (Ubuntu Eoan) ** Description changed: [Impact] - Users install the focal kernel on the bionic or eoan, the sof driver + Users install the focal kernel on the bionic, the sof driver in focal kernel will fail to load the tplg files. [Fix] generate the symbollinks according to the requirement of sof driver in the focal kernel. [Test Case] - booting the focal kernel on bionic or eoan, the sof driver could + booting the focal kernel on bionic, the sof driver could load the tplg successfully, and the audio works well. [Regression Risk] - Low, the bionic and eoan kernel will still load sof-hda-generic.tplg, - there is no any impact on the original bionic/eoan kernel + linux-firmware. + Low, the bionic kernel will still load sof-hda-generic.tplg, + there is no any impact on the original bionic kernel + linux-firmware. -- 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/1880623 Title: linux-firmware: generate the symbollink of sof-hda-generic- 2ch/4ch.tplg for bionic Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: New Bug description: [Impact] Users install the focal kernel on the bionic, the sof driver in focal kernel will fail to load the tplg files. [Fix] generate the symbollinks according to the requirement of sof driver in the focal kernel. [Test Case] booting the focal kernel on bionic, the sof driver could load the tplg successfully, and the audio works well. [Regression Risk] Low, the bionic kernel will still load sof-hda-generic.tplg, there is no any impact on the original bionic kernel + linux-firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1880623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: [focal] disk I/O performance regression
** Tags added: uosci -- You 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, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub,
[Kernel-packages] [Bug 1880623] Re: linux-firmware: generate the symbollink of sof-hda-generic-2ch/4ch.tplg for bionic and eoan
** Changed in: linux-firmware (Ubuntu Eoan) Status: New => Invalid -- 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/1880623 Title: linux-firmware: generate the symbollink of sof-hda-generic- 2ch/4ch.tplg for bionic Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: New Bug description: [Impact] Users install the focal kernel on the bionic, the sof driver in focal kernel will fail to load the tplg files. [Fix] generate the symbollinks according to the requirement of sof driver in the focal kernel. [Test Case] booting the focal kernel on bionic, the sof driver could load the tplg successfully, and the audio works well. [Regression Risk] Low, the bionic kernel will still load sof-hda-generic.tplg, there is no any impact on the original bionic kernel + linux-firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1880623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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
[Kernel-packages] [Bug 1877425] Re: linux-azure: Enable FSGSBASE instructions to support SGX
** Changed in: linux-azure (Ubuntu Eoan) Status: In Progress => Fix Committed -- 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/1877425 Title: linux-azure: Enable FSGSBASE instructions to support SGX Status in linux-azure package in Ubuntu: In Progress Status in linux-azure-4.15 package in Ubuntu: In Progress Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: In Progress Status in linux-azure source package in Eoan: Fix Committed Status in linux-azure-4.15 source package in Eoan: Invalid Status in linux-azure source package in Focal: In Progress Status in linux-azure-4.15 source package in Focal: Invalid Bug description: X86 has instructions (RDFSBASE, RDGSBASE, WRFSBASE, and WRGSBASE) to support read/write of the FS/GS bases. Linux doesn't allow user mode code to execute these instructions by default. These instructions can be enabled for user mode by setting the 16th control bit of the CR4 register. Since only protected mode can modify the control registers, application programs and operating-system procedures (running at privilege levels 1, 2, or 3) are prevented from reading or loading the control registers. The kernel patch sets this CR4 register and handles the context switching to account for the fact that user mode can now modify the FS/GS base. A recent news article that talks about the performance benefits: https://phoronix.com/scan.php?page=news_item=Intel-FSGSBASE- Linux-2020. Another news article covers the performance information in a lot more detail by running a number of performance tests: https://www.phoronix.com/scan.php?page=article=linux-wip- fsgsbase=1 Patch set: https://lkml.org/lkml/2019/10/4/725 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1877425/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880639] Re: O wi-fi desconecta automaticamente
Oi Josimar, Por favor, pode coletar um sosreport depois que o problema acontecer algumas vezes (por exemplo, 24 horas com o notebook ligado), e anexar nesse bug? $ sudo sosreport --batch --case-id lp1880639 O arquivo será algo como /tmp/sosreport-*-lp1880639-2020-*.tar.xz Seu kernel log mostra 2 mensagens interessantes do driver de wi-fi; gostaria de ver se elas sao consistentes entre os eventos de desconexão. [ 342.159298] wlp2s0: authenticate with 14:cc:20:a1:f9:b8 [ 342.191224] wlp2s0: send auth to 14:cc:20:a1:f9:b8 (try 1/3) [ 342.193302] wlp2s0: authenticated [ 342.201849] wlp2s0: associate with 14:cc:20:a1:f9:b8 (try 1/3) [ 342.206364] wlp2s0: RX AssocResp from 14:cc:20:a1:f9:b8 (capab=0x431 status=0 aid=1) [ 342.209383] wlp2s0: associated [ 342.311375] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready *** [ 346.586943] wlp2s0: deauthenticating from 14:cc:20:a1:f9:b8 by local choice (Reason: 3=DEAUTH_LEAVING) [ 547.084759] ath10k_pci :02:00.0: unsupported HTC service id: 1536 *** [ 552.200067] wlp2s0: authenticate with 14:cc:20:a1:f9:b8 [ 552.231888] wlp2s0: send auth to 14:cc:20:a1:f9:b8 (try 1/3) [ 552.234122] wlp2s0: authenticated [ 552.237649] wlp2s0: associate with 14:cc:20:a1:f9:b8 (try 1/3) [ 552.241979] wlp2s0: RX AssocResp from 14:cc:20:a1:f9:b8 (capab=0x431 status=0 aid=1) [ 552.244682] wlp2s0: associated [ 552.254458] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880639 Title: O wi-fi desconecta automaticamente Status in linux package in Ubuntu: Confirmed Bug description: Atualizei para a versão 20.04 e desde então meu notebook vem apresentando erro, desconectando automaticamente minhas conexões wi- fi. 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/controlC0: josimar1912 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 01:17:39 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-20180608-47+loki-n3-v3-kbl+X28 InstallationDate: Installed on 2020-01-17 (129 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3584 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=127ffefc-873d-410c-8d99-aaf1637e14dc ro mem_sleep_default=deep 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: Upgraded to focal on 2020-05-11 (15 days ago) dmi.bios.date: 07/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05RCHV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd07/10/2019:svnDellInc.:pnInspiron3584:pvr:rvnDellInc.:rn05RCHV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3584 dmi.product.sku: 08D1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] [NEW] [focal] disk I/O performance regression
Public bug reported: 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, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/6p, 480M MachineType: Dell Inc. PowerEdge R630 PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=8dd6086f-e616-466d-a424-e5556fd75045 ro intel_iommu=on iommu=pt probe_vf=0 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A
[Kernel-packages] [Bug 1880835] Re: pulse audio hangs in kernel call
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc7/ There are several fixes for oxfw which is the driver for FireWire One. ** 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/1880835 Title: pulse audio hangs in kernel call Status in linux package in Ubuntu: Incomplete Bug description: there is no audio device accessible any more and pulse-audio process can not be terminated in kernel log there is such a output: This makes the complete audio unstable in the laptop. I think it is started to happen when I installed Nvidia driver and there is an external monitor attached with DP audio device. [ 364.150644] INFO: task pulseaudio:2183 blocked for more than 120 seconds. [ 364.150646] Tainted: P OE 5.4.0-31-generic #35-Ubuntu [ 364.150647] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 364.150647] pulseaudio D0 2183 2175 0x4120 [ 364.150649] Call Trace: [ 364.150653] __schedule+0x2e3/0x740 [ 364.150655] ? dma_pte_clear_level+0x142/0x190 [ 364.150655] schedule+0x42/0xb0 [ 364.150656] schedule_timeout+0x203/0x2f0 [ 364.150657] wait_for_completion+0xb1/0x120 [ 364.150659] ? wake_up_q+0x70/0x70 [ 364.150663] fw_run_transaction+0xdc/0x110 [firewire_core] [ 364.150665] ? fw_core_handle_bus_reset+0x440/0x440 [firewire_core] [ 364.150666] ? free_iova_fast+0x18/0x30 [ 364.150667] ? close_transaction+0x110/0x110 [firewire_core] [ 364.150668] ? intel_unmap+0xd9/0x1c0 [ 364.150670] ? transmit_phy_packet_callback+0x20/0x20 [firewire_core] [ 364.150671] snd_fw_transaction+0xbc/0x110 [snd_firewire_lib] [ 364.150673] ? avc_general_get_plug_info+0x100/0x100 [snd_firewire_lib] [ 364.150674] pcr_modify+0x65/0x100 [snd_firewire_lib] [ 364.150675] cmp_connection_break+0x37/0x50 [snd_firewire_lib] [ 364.150677] snd_oxfw_stream_start_duplex+0x1ee/0x2e0 [snd_oxfw] [ 364.150678] ? wait_woken+0x80/0x80 [ 364.150679] pcm_capture_prepare+0x26/0x50 [snd_oxfw] [ 364.150682] snd_pcm_do_prepare+0x1e/0x30 [snd_pcm] [ 364.150684] snd_pcm_action_single+0x3c/0x80 [snd_pcm] [ 364.150686] snd_pcm_action_nonatomic+0x6e/0x80 [snd_pcm] [ 364.150687] snd_pcm_prepare+0x6a/0x90 [snd_pcm] [ 364.150689] snd_pcm_common_ioctl+0x28c/0xc00 [snd_pcm] [ 364.150691] snd_pcm_ioctl+0x27/0x40 [snd_pcm] [ 364.150692] do_vfs_ioctl+0x407/0x670 [ 364.150694] ? __secure_computing+0x42/0xe0 [ 364.150694] ksys_ioctl+0x67/0x90 [ 364.150695] __x64_sys_ioctl+0x1a/0x20 [ 364.150697] do_syscall_64+0x57/0x190 [ 364.150698] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 364.150699] RIP: 0033:0x7f0bbfa1a37b [ 364.150701] Code: Bad RIP value. [ 364.150701] RSP: 002b:7ffed915d308 EFLAGS: 0202 ORIG_RAX: 0010 [ 364.150702] RAX: ffda RBX: 5607c7b63de0 RCX: 7f0bbfa1a37b [ 364.150703] RDX: RSI: 4140 RDI: 006e [ 364.150703] RBP: 5607c7b63bb0 R08: R09: 1000 [ 364.150703] R10: 0004 R11: 0202 R12: 5607c7b63de0 [ 364.150704] R13: 7ffed915d6f0 R14: R15: 7ffed915d480 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_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 27 10:07:13 2020 InstallationDate: Installed on 2020-02-22 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) MachineType: Dell Inc. Precision 7540 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=7a5890f6-2724-480a-8fa7-778d07cd929d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. 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/12/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0T2FXT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd03/12/2020:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0T2FXT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926
[Kernel-packages] [Bug 1878166] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377350/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878166] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377359/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878166] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377351/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878166] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377348/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878166] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377349/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878166] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377346/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878166] Re: Kernel crash in nouveau with Wayland
apport information ** Tags added: apport-collected ** Description changed: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: mavi 2227 F pulseaudio + /dev/snd/controlC0: mavi 2227 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap + InstallationDate: Installed on 2016-09-05 (1360 days ago) + InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + MachineType: LENOVO 20EN0005MS + Package: linux (not installed) + ProcFB: 0 nouveaudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-31-generic N/A + linux-backports-modules-5.4.0-31-generic N/A + linux-firmware1.187 + Tags: wayland-session focal + Uname: Linux 5.4.0-31-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) + UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video + _MarkForUpload: True + dmi.bios.date: 12/06/2019 + dmi.bios.vendor: LENOVO + dmi.bios.version: N1EET87W (1.60 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20EN0005MS + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40705 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad P50 + dmi.product.name: 20EN0005MS + dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 + dmi.product.version: ThinkPad P50 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377343/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs.
[Kernel-packages] [Bug 1878166] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377356/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878166] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377358/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878166] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377354/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878166] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377347/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878166] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377344/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878166] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377360/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878166] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377355/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878166] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377352/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878166] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377357/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878166] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377345/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878166] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1878166/+attachment/5377353/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Confirmed Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2227 F pulseaudio /dev/snd/controlC0: mavi 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1360 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: wayland-session focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago) UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET87W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869672] Re: Kdump broken since 4.15.0-65 on secureboot - purgatory cannot load
Great news yamato, thanks for testing. I'll mark it as verified. Thanks once more for the great bug report and all the help provided on testing! Cheers, Guilherme ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869672 Title: Kdump broken since 4.15.0-65 on secureboot - purgatory cannot load Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] * Kdump kernel can't be loaded using Linux kernel 4.15.0-65 and newer on Bionic; kexec fails to load using the "new" kexec_file_load() syscall, showing the following messages in dmesg: kexec: Undefined symbol: __stack_chk_fail kexec-bzImage64: Loading purgatory failed * Reason for this was that backport from upstream commit b059f801a937 ("x86/purgatory: Use CFLAGS_REMOVE rather than reset KBUILD_CFLAGS") makes use of a config option guard that wasn't backported to Ubuntu 4.15.x series. * Also, we found another related issue, an undefined memcpy() symbol, that was related to the above patch too. We propose here a specific fix for Bionic, in the form of the patch attached in comment #18. [Test case] * Basically the test consists in booting a signed kernel in a secure boot environment (this is required given Ubuntu kernel is built with CONFIG_KEXEC_VERIFY_SIG so to use kexec_file_load() we must be in a proper signed/secure booted system). It works until 4.15.0-64, and starts to fail after this release, until the current proposed version 4.15.0-97. We can also check kdump-tools service in the failing case, which shows: systemctl status kdump-tools [...] kdump-tools[895]: Starting kdump-tools: * Creating symlink /var/lib/kdump/vmlinuz kdump-tools[895]: * Creating symlink /var/lib/kdump/initrd.img kdump-tools[895]: kexec_file_load failed: Exec format error kdump-tools[895]: * failed to load kdump kernel [...] * With the patch attached in the LP, it works normally again and I was able to collect a kdump. [Regression potential] * Given the patch is quite simple and fixes the build of purgatory, I think the regression potential is low. One potential regression in future would be on backports to purgatory Makefile, making them more difficult/prone to errors; given purgatory is a pretty untouchable code, I consider the regression potential here to be really low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876741] Re: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed
Hi Raoul, yes, your probably right it is not exactly the same. I overlooked in your initial post that the problem happened before grub and the title sounds so much like my problem. I think I assumed from here > if something is attached to thunderbolt, no way to see even grub, if nothing is attached (and LID is closed) then I see grub loading on the external monitor but I don't get GDM. that you also had a problem after grub that is not associated with the thunderbolt issue. Thanks for your suggestions, I quickly tried both of them. Uninstalling xserver-xorg-video-intel did not solve it, but if I boot without "quiet splash" I can get to the login screen and login normally even though the HDMI cable is attached. I first see some log lines from the booting process on the screen, as expected, but the page with the Lenovo logo and Spinner does not come up and I just get to the login screen. Sorry if I am posting to the wrong thread here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876741 Title: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed Status in linux package in Ubuntu: Confirmed Bug description: Hey everyone, just upgraded to 20.04 in my Lenovo X1 Carbon laptop and found myself in really big troubles. I always started my laptop pressing the power button and then closing the laptop lid, because I'm using an external HDMI display. This worked always well with Ubuntu 19.10. With 20.04 the system crash. These are the actions that reproduce the problem: 1 - Boot the system, pressing the power button and closing the laptop lid with an external HDMI display attached to the laptop; 2 - See on the external HDMI display the boot progress: BIOS loading and then grub not appearing; 3 - Listen to the fans that are about to make the laptop lift; 4 - Press the power button to force off the laptop; At this point the only way to have everything back is: 1 - Detach any external device; 2 - Detach the power cable; 3 - Wait 3 seconds or more; 4 - Open the laptop lid; 5 - Attach the power cable; 6 - Press the power button; Without doing exactly as I written the laptop will not boot up, even if I force power off, after starting it again, after the BIOS display, the screen goes blank and the fans lift. NOTE 1: I already disabled secure boot in the BIOS, and also selected discrete graphics for the display (otherwise I'm not able to even start X); NOTE 2: the scenario is exactly the same with nvidia-driver-435 and nvidia-driver-440; NOTE 3: if I leave the laptop lid open, everything is just fine; ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-28-generic 5.4.0-28.32 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rasca 2750 F pulseaudio /dev/snd/controlC1: rasca 2750 F pulseaudio /dev/snd/controlC0: rasca 2750 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 4 16:24:47 2020 InstallationDate: Installed on 2019-12-10 (146 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=c61df9cc-bd36-4ed2-8f52-de114bbf3fc3 ro rd.driver.blacklist=nouveau RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-28 (6 days ago) dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET43W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET43W(1.30):bd03/24/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876741/+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 1880835] Re: pulse audio hangs in kernel call
After debugging a bit. I narrowed down the problem. It is related to the FireWire800 auido adapter (Tascam FireOne) the device goes in to a non working state. It seems that the the control part of the communication works. But The SoundCard is in a dead lock. And it hangs the kernel diver communication. The the problem solved by power cycle the Tascan FireOne device and reboot the ubuntu laptop. After the boot then the audio works again and pulseaudio does not hang any more. So it seems the the problem caused by the device communication misbehavior on the filerwire port. I think the kernel driver shall be examined to able to cope with the errors from the device side. Since this breaks done the complete audio subsystem and the machine can not even rebooted. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880835 Title: pulse audio hangs in kernel call Status in linux package in Ubuntu: Confirmed Bug description: there is no audio device accessible any more and pulse-audio process can not be terminated in kernel log there is such a output: This makes the complete audio unstable in the laptop. I think it is started to happen when I installed Nvidia driver and there is an external monitor attached with DP audio device. [ 364.150644] INFO: task pulseaudio:2183 blocked for more than 120 seconds. [ 364.150646] Tainted: P OE 5.4.0-31-generic #35-Ubuntu [ 364.150647] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 364.150647] pulseaudio D0 2183 2175 0x4120 [ 364.150649] Call Trace: [ 364.150653] __schedule+0x2e3/0x740 [ 364.150655] ? dma_pte_clear_level+0x142/0x190 [ 364.150655] schedule+0x42/0xb0 [ 364.150656] schedule_timeout+0x203/0x2f0 [ 364.150657] wait_for_completion+0xb1/0x120 [ 364.150659] ? wake_up_q+0x70/0x70 [ 364.150663] fw_run_transaction+0xdc/0x110 [firewire_core] [ 364.150665] ? fw_core_handle_bus_reset+0x440/0x440 [firewire_core] [ 364.150666] ? free_iova_fast+0x18/0x30 [ 364.150667] ? close_transaction+0x110/0x110 [firewire_core] [ 364.150668] ? intel_unmap+0xd9/0x1c0 [ 364.150670] ? transmit_phy_packet_callback+0x20/0x20 [firewire_core] [ 364.150671] snd_fw_transaction+0xbc/0x110 [snd_firewire_lib] [ 364.150673] ? avc_general_get_plug_info+0x100/0x100 [snd_firewire_lib] [ 364.150674] pcr_modify+0x65/0x100 [snd_firewire_lib] [ 364.150675] cmp_connection_break+0x37/0x50 [snd_firewire_lib] [ 364.150677] snd_oxfw_stream_start_duplex+0x1ee/0x2e0 [snd_oxfw] [ 364.150678] ? wait_woken+0x80/0x80 [ 364.150679] pcm_capture_prepare+0x26/0x50 [snd_oxfw] [ 364.150682] snd_pcm_do_prepare+0x1e/0x30 [snd_pcm] [ 364.150684] snd_pcm_action_single+0x3c/0x80 [snd_pcm] [ 364.150686] snd_pcm_action_nonatomic+0x6e/0x80 [snd_pcm] [ 364.150687] snd_pcm_prepare+0x6a/0x90 [snd_pcm] [ 364.150689] snd_pcm_common_ioctl+0x28c/0xc00 [snd_pcm] [ 364.150691] snd_pcm_ioctl+0x27/0x40 [snd_pcm] [ 364.150692] do_vfs_ioctl+0x407/0x670 [ 364.150694] ? __secure_computing+0x42/0xe0 [ 364.150694] ksys_ioctl+0x67/0x90 [ 364.150695] __x64_sys_ioctl+0x1a/0x20 [ 364.150697] do_syscall_64+0x57/0x190 [ 364.150698] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 364.150699] RIP: 0033:0x7f0bbfa1a37b [ 364.150701] Code: Bad RIP value. [ 364.150701] RSP: 002b:7ffed915d308 EFLAGS: 0202 ORIG_RAX: 0010 [ 364.150702] RAX: ffda RBX: 5607c7b63de0 RCX: 7f0bbfa1a37b [ 364.150703] RDX: RSI: 4140 RDI: 006e [ 364.150703] RBP: 5607c7b63bb0 R08: R09: 1000 [ 364.150703] R10: 0004 R11: 0202 R12: 5607c7b63de0 [ 364.150704] R13: 7ffed915d6f0 R14: R15: 7ffed915d480 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_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 27 10:07:13 2020 InstallationDate: Installed on 2020-02-22 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) MachineType: Dell Inc. Precision 7540 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=7a5890f6-2724-480a-8fa7-778d07cd929d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187
Re: [Kernel-packages] [Bug 1877670] Re: [Acer Aspire R3-131T] Touchpad freezes and frequently mouse cursor disappears.
No. It happens at all times. On Wed, May 27, 2020 at 9:40 AM Kai-Heng Feng <1877...@bugs.launchpad.net> wrote: > Does this issue only happen after system suspend? > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1877670 > > Title: > [Acer Aspire R3-131T] Touchpad freezes and frequently mouse cursor > disappears. > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Display Freezes and frequently mouse cursor disappears. After restart > mouse cursor comes back again. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > 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 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sat May 9 02:25:55 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx > Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA > controller]) > Subsystem: Acer Incorporated [ALI] Atom/Celeron/Pentium Processor > x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1025:1022] > InstallationDate: Installed on 2020-04-23 (14 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 8087:0a2a Intel Corp. >Bus 001 Device 003: ID 2386:0401 Raydium Corporation Raydium Touch > System >Bus 001 Device 002: ID 04f2:b520 Chicony Electronics Co., Ltd HD WebCam >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: Acer Aspire R3-131T > ProcEnviron: >LANGUAGE=en_IN:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_IN >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic > root=UUID=5b613349-680c-466c-b069-960c9c12c462 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/30/2016 > dmi.bios.vendor: Insyde Corp. > dmi.bios.version: V1.17 > dmi.board.name: Aspire R3-131T > dmi.board.vendor: Acer > dmi.board.version: V1.17 > dmi.chassis.type: 10 > dmi.chassis.vendor: Acer > dmi.chassis.version: V1.17 > dmi.modalias: > dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireR3-131T:pvrV1.17:rvnAcer:rnAspireR3-131T:rvrV1.17:cvnAcer:ct10:cvrV1.17: > dmi.product.family: BSW > dmi.product.name: Aspire R3-131T > dmi.product.sku: Aspire R3-131T_1022_1.17 > dmi.product.version: V1.17 > dmi.sys.vendor: Acer > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877670/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877670 Title: [Acer Aspire R3-131T] Touchpad freezes and frequently mouse cursor disappears. Status in linux package in Ubuntu: Incomplete Bug description: Display Freezes and frequently mouse cursor disappears. After restart mouse cursor comes back again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 02:25:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom/Celeron/Pentium Processor
[Kernel-packages] [Bug 1878166] 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 1878166 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/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: Incomplete Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland
Thanks, that worked: https://errors.ubuntu.com/oops/93823806-9ff7-11ea-9bb3-fa163e102db1 but I can't see any interesting functions blocking in any of the threads. Let's skip that and just make this about the nouveau kernel crash. ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Summary changed: - gnome-shell freezes randomly on nouveau and wayland + Kernel crash in nouveau with Wayland -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland Status in linux package in Ubuntu: New Bug description: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876741] Re: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed
Hi Maria, I don't think your issue is the same I got. Note that my problem happened with or without the dock, and I wasn't even reaching grub. That's the big difference here. If you lose the video after grub, than your problem is elsewhere, and my suggestion is to boot without "quiet splash" on the grup command line, so that you can see where the boot is stuck. If it reaches the end of the boot process and it is just unable to start X (so GDM, LightDM or whatever), then your problem might be related to the drivers, maybe not blacklisting nouveau or things like these. Maybe as suggested elsewhere [1], you just need to uninstall the buggy xserver-xorg-video-intel package. What is more important here is that my problem got solved by setting the "Set Optimized" option in the BIOS to true. This solved a huge amount of problems, the last one I'm waiting to solve before closing this bug is to understand how to boot without a customized /etc/X11/xorg.conf. Hope this helps. [1] https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1879484 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876741 Title: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed Status in linux package in Ubuntu: Confirmed Bug description: Hey everyone, just upgraded to 20.04 in my Lenovo X1 Carbon laptop and found myself in really big troubles. I always started my laptop pressing the power button and then closing the laptop lid, because I'm using an external HDMI display. This worked always well with Ubuntu 19.10. With 20.04 the system crash. These are the actions that reproduce the problem: 1 - Boot the system, pressing the power button and closing the laptop lid with an external HDMI display attached to the laptop; 2 - See on the external HDMI display the boot progress: BIOS loading and then grub not appearing; 3 - Listen to the fans that are about to make the laptop lift; 4 - Press the power button to force off the laptop; At this point the only way to have everything back is: 1 - Detach any external device; 2 - Detach the power cable; 3 - Wait 3 seconds or more; 4 - Open the laptop lid; 5 - Attach the power cable; 6 - Press the power button; Without doing exactly as I written the laptop will not boot up, even if I force power off, after starting it again, after the BIOS display, the screen goes blank and the fans lift. NOTE 1: I already disabled secure boot in the BIOS, and also selected discrete graphics for the display (otherwise I'm not able to even start X); NOTE 2: the scenario is exactly the same with nvidia-driver-435 and nvidia-driver-440; NOTE 3: if I leave the laptop lid open, everything is just fine; ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-28-generic 5.4.0-28.32 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rasca 2750 F pulseaudio /dev/snd/controlC1: rasca 2750 F pulseaudio /dev/snd/controlC0: rasca 2750 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 4 16:24:47 2020 InstallationDate: Installed on 2019-12-10 (146 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=c61df9cc-bd36-4ed2-8f52-de114bbf3fc3 ro rd.driver.blacklist=nouveau RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-28 (6 days ago) dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET43W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET43W(1.30):bd03/24/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1878166] [NEW] gnome-shell freezes randomly on nouveau and wayland
You have been subscribed to a public bug: The freeze causes the mouse cursor to stop moving and keyboard to stop responding and nothing moves on screen, not even the clock. Curiously the music continues to play (and e.g. sound from youtube video continues to be played even though the video itself freezes and no longer animates on-screen). It appears that the freeze happens quite randomly; I am not able to figure out what it's caused by. Sometimes it's caused by launching the Snap Chromium, or perhaps by a notification shown, but I do not know for sure. I also tried to hunt system logs and/or systemd gnome-shell logs, but I failed to discover some kind of crash dump. Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to believe that it's some kind of kernel+nouveau crash, but I can't seem to discover any kernel panic in the system logs. After the gnome-shell freezes, the numlock light still responds to numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm only able to reboot via Alt+Sysrq+s u b. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 11:20:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-05 (1344 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal wayland-session -- gnome-shell freezes randomly on nouveau and wayland https://bugs.launchpad.net/bugs/1878166 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 1877889] Re: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595
I've switched back to the 5.4 kernel and have enabled the 'nomodeset' parameter. The laptop has booted fine. I'll keep using it like this and let you know if I see another hang on boot. I've noticed that Wayland is no longer an option on the login screen. I presume this is an expected consequence of disabling modesetting. $ cat /proc/version Linux version 5.4.0-31-generic (buildd@lgw01-amd64-059) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 $ cat /proc/version_signature Ubuntu 5.4.0-31.35-generic 5.4.34 $ cat /etc/default/grub | grep GRUB_CMDLINE GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" GRUB_CMDLINE_LINUX="" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877889 Title: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595 Status in linux package in Ubuntu: Confirmed Bug description: Hello, I see occasional hangs on boot. The hangs occur after entering the LUKS decryption password for the root filesystem, and before the login screen is displayed. The "/boot" filesystem is not encrypted, so the initramfs is loading fine etc. The hangs are intermittent. Sometimes I don't see a hang for 10+ boots in a row, and sometimes I'll get a hang 5 times in a row. When the hang occurs the boot splash screen is visible (not the login screen). The system is still responsive to SysRq keys, so I can somewhat safely issue S+U+S+B sequence to try booting again without corrupting much. I have tried removing the "quiet splash" kernel parameters that are enabled by default on Ubuntu desktop to see if any interesting messages occur that way. So far however I have not experienced a hang with "quiet splash" removed. This system is a Lenovo E595 (Ryzen 3500U) with the latest BIOS from Lenovo installed (v1.16), running Ubuntu 20.04 desktop. I am submitting this bug using `ubuntu-bug linux-image-generic`, but I don't know for sure if this is a kernel issue or something else. I suspect my bug might be the same as this one already reported ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873594 ), but I'm filing my own anyway as a means to capture more details of my system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.29.34 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/controlC1: paul 2507 F pulseaudio /dev/snd/controlC0: paul 2507 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 20:09:53 2020 MachineType: LENOVO 20NFCTO1WW ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=f466d4ea-c251-4721-b071-bd70c82f00e1 ro rootflags=subvol=@ splash quiet 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-04-24 (15 days ago) 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/1877889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879704] Re: [UBUNTU 20.04] s390x/pci: implement linking between PF and VF for multifunction devices
Thx for the update - yepp, found them in linux-next. So should be possible to address them with the upcoming kernel SRU ... ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: ubuntu-z-systems Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879704 Title: [UBUNTU 20.04] s390x/pci: implement linking between PF and VF for multifunction devices Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: As with other architectures, we must be able on s390x to verify the following relationships between PFs and VFs for proper management (including by libvirt) of network interfaces: 1. Determine if a device is a virtual function: for other architectures this is currently available in the file `physfn` which is a link to the parent PF's device. 2. Determine virtual functions of a physical function: for other architectures this is currently available as `virtfn{index}` links under the PF device's directory. 3. Determine the physical function of a virtual function: on x86 this is currently available in the file `physfn` which is a link to the parent PF More details for the already existing parameters mentioned above can be found here: https://www.kernel.org/doc/Documentation/ABI/testing /sysfs-bus-pci Moreover creating not just the sysfs but also the in-kernel link (struct pci_dev->physfn) also allows us to use the common code path for disabling/shutdown of PFs. This code path is currently fenced off by the struct pci_dev->no_vf_scan flag of which s390 is currently the only user. This in turn allows for a graceful and orderly shutdown of VFs associated with a VF as triggered by: echo 0 > /sys/bus/pci/devices//sriov_numvfs Previously this could leave the card in an unresponsive error state. The patches for this have been discussed and Acked-by the responsible upstream maintainer here: [RFC 0/2] Enable PF-VF linking with pdev->no_vf_scan (s390) https://lore.kernel.org/linux-pci/20200506154139.90609-1-schne...@linux.ibm.com/ [RFC 1/2] PCI/IOV: Introduce pci_iov_sysfs_link() function https://lore.kernel.org/linux-pci/20200506154139.90609-2-schne...@linux.ibm.com/ [RFC 2/2] s390/pci: create links between PFs and VFs https://lore.kernel.org/linux-pci/20200506154139.90609-2-schne...@linux.ibm.com/ They are currently queued to be posted to the public s390 Kernel repository and linux-next / 5.8. These depend on the previous multi-function/enumeration rework. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1879704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
@Hui Here is alsa-info.sh output with snd_hda_intel.dmic_detect=0 http://alsa-project.org/db/?f=a0666f31d648566f09d98d4ca79746a197403e28 With dmic_detect=0 internal speakers works but internal mic does not. External headset works fine both headphones and mic. -- You 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 1850904] Re: 36-sim-ipc_syscalls, 37-sim-ipc_syscalls_be from ubuntu_seccomp failed with X/B/D s390x / PPC
Didn't see this on X/B PPC. * 4.4.0-180.210 * 4.15.0-102.103 Looks like this has been fixed, closing this bug. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Disco) Status: Incomplete => Invalid ** Changed in: ubuntu-kernel-tests Status: Triaged => 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/1850904 Title: 36-sim-ipc_syscalls, 37-sim-ipc_syscalls_be from ubuntu_seccomp failed with X/B/D s390x / PPC Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Invalid Bug description: This issue was found on Disco, after re-enable the ubuntu-seccomp (bug 1850743) test for newer releases. So this is not a regression. The test has passed with amd64, i386, but failed with s390x / PowerPC 36 test errored. batch name: 36-sim-ipc_syscalls test mode: c test type: bpf-sim Test 36-sim-ipc_syscalls%%001-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%002-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%003-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%004-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%005-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%006-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%007-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%008-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%009-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%010-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%011-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%012-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%013-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%014-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%015-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%016-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%017-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%018-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%019-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%020-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%021-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%022-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%023-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%024-1 result: ERROR 36-sim-ipc_syscalls rc=14 test mode: c test type: bpf-valgrind Test 36-sim-ipc_syscalls%%025-1 result: SKIPPED (valgrind not installed) batch name: 37-sim-ipc_syscalls_be test mode: c test type: bpf-sim test arch: s390 Test 37-sim-ipc_syscalls_be%%001-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%002-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%003-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%004-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%005-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%006-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%007-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%008-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%009-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%010-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%011-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%012-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test mode: c test type: bpf-valgrind ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34 ProcVersionSignature: User Name 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic s390x AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or
[Kernel-packages] [Bug 1880834] Re: qeth: utilize virtual MAC for Layer2 OSD devices
** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Status: New => Incomplete ** 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/1880834 Title: qeth: utilize virtual MAC for Layer2 OSD devices Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete 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 1850904] Re: 36-sim-ipc_syscalls, 37-sim-ipc_syscalls_be from ubuntu_seccomp failed with X/B/D s390x / PPC
For comment #5, nor seeing this on s390x. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850904 Title: 36-sim-ipc_syscalls, 37-sim-ipc_syscalls_be from ubuntu_seccomp failed with X/B/D s390x / PPC Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Invalid Bug description: This issue was found on Disco, after re-enable the ubuntu-seccomp (bug 1850743) test for newer releases. So this is not a regression. The test has passed with amd64, i386, but failed with s390x / PowerPC 36 test errored. batch name: 36-sim-ipc_syscalls test mode: c test type: bpf-sim Test 36-sim-ipc_syscalls%%001-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%002-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%003-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%004-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%005-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%006-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%007-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%008-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%009-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%010-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%011-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%012-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%013-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%014-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%015-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%016-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%017-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%018-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%019-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%020-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%021-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%022-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%023-1 result: ERROR 36-sim-ipc_syscalls rc=14 Test 36-sim-ipc_syscalls%%024-1 result: ERROR 36-sim-ipc_syscalls rc=14 test mode: c test type: bpf-valgrind Test 36-sim-ipc_syscalls%%025-1 result: SKIPPED (valgrind not installed) batch name: 37-sim-ipc_syscalls_be test mode: c test type: bpf-sim test arch: s390 Test 37-sim-ipc_syscalls_be%%001-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%002-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%003-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%004-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%005-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%006-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%007-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%008-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%009-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%010-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%011-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test arch: s390 Test 37-sim-ipc_syscalls_be%%012-1 result: ERROR 37-sim-ipc_syscalls_be rc=14 test mode: c test type: bpf-valgrind ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34 ProcVersionSignature: User Name 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic s390x AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.2 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit
[Kernel-packages] [Bug 1880835] 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/1880835 Title: pulse audio hangs in kernel call Status in linux package in Ubuntu: Confirmed Bug description: there is no audio device accessible any more and pulse-audio process can not be terminated in kernel log there is such a output: This makes the complete audio unstable in the laptop. I think it is started to happen when I installed Nvidia driver and there is an external monitor attached with DP audio device. [ 364.150644] INFO: task pulseaudio:2183 blocked for more than 120 seconds. [ 364.150646] Tainted: P OE 5.4.0-31-generic #35-Ubuntu [ 364.150647] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 364.150647] pulseaudio D0 2183 2175 0x4120 [ 364.150649] Call Trace: [ 364.150653] __schedule+0x2e3/0x740 [ 364.150655] ? dma_pte_clear_level+0x142/0x190 [ 364.150655] schedule+0x42/0xb0 [ 364.150656] schedule_timeout+0x203/0x2f0 [ 364.150657] wait_for_completion+0xb1/0x120 [ 364.150659] ? wake_up_q+0x70/0x70 [ 364.150663] fw_run_transaction+0xdc/0x110 [firewire_core] [ 364.150665] ? fw_core_handle_bus_reset+0x440/0x440 [firewire_core] [ 364.150666] ? free_iova_fast+0x18/0x30 [ 364.150667] ? close_transaction+0x110/0x110 [firewire_core] [ 364.150668] ? intel_unmap+0xd9/0x1c0 [ 364.150670] ? transmit_phy_packet_callback+0x20/0x20 [firewire_core] [ 364.150671] snd_fw_transaction+0xbc/0x110 [snd_firewire_lib] [ 364.150673] ? avc_general_get_plug_info+0x100/0x100 [snd_firewire_lib] [ 364.150674] pcr_modify+0x65/0x100 [snd_firewire_lib] [ 364.150675] cmp_connection_break+0x37/0x50 [snd_firewire_lib] [ 364.150677] snd_oxfw_stream_start_duplex+0x1ee/0x2e0 [snd_oxfw] [ 364.150678] ? wait_woken+0x80/0x80 [ 364.150679] pcm_capture_prepare+0x26/0x50 [snd_oxfw] [ 364.150682] snd_pcm_do_prepare+0x1e/0x30 [snd_pcm] [ 364.150684] snd_pcm_action_single+0x3c/0x80 [snd_pcm] [ 364.150686] snd_pcm_action_nonatomic+0x6e/0x80 [snd_pcm] [ 364.150687] snd_pcm_prepare+0x6a/0x90 [snd_pcm] [ 364.150689] snd_pcm_common_ioctl+0x28c/0xc00 [snd_pcm] [ 364.150691] snd_pcm_ioctl+0x27/0x40 [snd_pcm] [ 364.150692] do_vfs_ioctl+0x407/0x670 [ 364.150694] ? __secure_computing+0x42/0xe0 [ 364.150694] ksys_ioctl+0x67/0x90 [ 364.150695] __x64_sys_ioctl+0x1a/0x20 [ 364.150697] do_syscall_64+0x57/0x190 [ 364.150698] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 364.150699] RIP: 0033:0x7f0bbfa1a37b [ 364.150701] Code: Bad RIP value. [ 364.150701] RSP: 002b:7ffed915d308 EFLAGS: 0202 ORIG_RAX: 0010 [ 364.150702] RAX: ffda RBX: 5607c7b63de0 RCX: 7f0bbfa1a37b [ 364.150703] RDX: RSI: 4140 RDI: 006e [ 364.150703] RBP: 5607c7b63bb0 R08: R09: 1000 [ 364.150703] R10: 0004 R11: 0202 R12: 5607c7b63de0 [ 364.150704] R13: 7ffed915d6f0 R14: R15: 7ffed915d480 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_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 27 10:07:13 2020 InstallationDate: Installed on 2020-02-22 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) MachineType: Dell Inc. Precision 7540 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=7a5890f6-2724-480a-8fa7-778d07cd929d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. 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/12/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0T2FXT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd03/12/2020:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0T2FXT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1866041] Re: 53-sim-binary_tree from ubuntu_seccomp failed with FAILURE bpf_sim resulted in ALLOW on 4.4 / 4.15 non-amd64
Didn't see this on Xenial AMD64 / i386 / P8 / s390x (ARM64 blacklisted) 4.4.0-180.210 ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866041 Title: 53-sim-binary_tree from ubuntu_seccomp failed with FAILURE bpf_sim resulted in ALLOW on 4.4 / 4.15 non-amd64 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Invalid Bug description: The following failures: Test 53-sim-binary_tree%%034-1 result: FAILURE bpf_sim resulted in ALLOW Test 53-sim-binary_tree%%035-1 result: FAILURE bpf_sim resulted in ALLOW Test 53-sim-binary_tree%%036-1 result: FAILURE bpf_sim resulted in ALLOW Can be found on: 4.15.0-92.93 - PoewrPC / s390x / i386 4.4.0-177 - PoewrPC / s390x / i386 Please find the complete test log with 4.4.0-177 in the attachment of comment 5. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-148-generic 4.4.0-148.174~14.04.1 ProcVersionSignature: User Name 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 Date: Wed Mar 4 10:32:46 2020 SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866041] Re: 53-sim-binary_tree from ubuntu_seccomp failed with FAILURE bpf_sim resulted in ALLOW on 4.4 / 4.15 non-amd64
Didn't see this on Bionic AMD64 / i386 / P8, P9 / s390x (ARM64 blacklisted) 4.15.0-102.103 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866041 Title: 53-sim-binary_tree from ubuntu_seccomp failed with FAILURE bpf_sim resulted in ALLOW on 4.4 / 4.15 non-amd64 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Invalid Bug description: The following failures: Test 53-sim-binary_tree%%034-1 result: FAILURE bpf_sim resulted in ALLOW Test 53-sim-binary_tree%%035-1 result: FAILURE bpf_sim resulted in ALLOW Test 53-sim-binary_tree%%036-1 result: FAILURE bpf_sim resulted in ALLOW Can be found on: 4.15.0-92.93 - PoewrPC / s390x / i386 4.4.0-177 - PoewrPC / s390x / i386 Please find the complete test log with 4.4.0-177 in the attachment of comment 5. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-148-generic 4.4.0-148.174~14.04.1 ProcVersionSignature: User Name 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 Date: Wed Mar 4 10:32:46 2020 SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp