[Kernel-packages] [Bug 1907262] Re: raid10: discard leads to corrupted file system
Hi Thimo, Thanks for writing back, great timing! So, the new revision of the patches that we have been testing since February have just been merged into mainline. The md/raid10 patches got merged on Friday, and the dm/raid patches got merged on Saturday, and will be tagged into 5.13-rc1. There's been a few of us testing them, and we haven't seen any regressions that cause data loss or disk corruption. Things are looking okay. If you are interested, you can see a list of the new commits on bug 1896578. We are still planning to SRU the new revision into the Ubuntu kernels, and I have spent the day backporting the official mainline commits to the Ubuntu 5.11, 5.8, 5.4 and 4.15 kernels. I'm currently building re-spins of the test kernels, based on more recently released Ubuntu kernels, with these official mainline patches, instead of the patches I got from the development mailing list I used in my previous set of test kernels. I'm expecting these kernels to finish building overnight, and I will make sure to write back tomorrow morning with instructions on how to install these test kernels. It would be great if you could give them a test before they get built into the next Ubuntu kernel update. Even when they are built into the next kernel update, I'll let you know how you can test them when they are in -proposed, before they are officially released to -updates. I'll write back tomorrow morning with instructions on how to install the fresh test kernels. Thanks, Matthew -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907262 Title: raid10: discard leads to corrupted file system Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: Seems to be closely related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578 After updating the Ubuntu 18.04 kernel from 4.15.0-124 to 4.15.0-126 the fstrim command triggered by fstrim.timer causes a severe number of mismatches between two RAID10 component devices. This bug affects several machines in our company with different HW configurations (All using ECC RAM). Both, NVMe and SATA SSDs are affected. How to reproduce: - Create a RAID10 LVM and filesystem on two SSDs mdadm -C -v -l10 -n2 -N "lv-raid" -R /dev/md0 /dev/nvme0n1p2 /dev/nvme1n1p2 pvcreate -ff -y /dev/md0 vgcreate -f -y VolGroup /dev/md0 lvcreate -n root-L 100G -ay -y VolGroup mkfs.ext4 /dev/VolGroup/root mount /dev/VolGroup/root /mnt - Write some data, sync and delete it dd if=/dev/zero of=/mnt/data.raw bs=4K count=1M sync rm /mnt/data.raw - Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (should be 0): cat /sys/block/md0/md/mismatch_cnt - Trigger the bug fstrim /mnt - Re-Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (probably in the range of N*1): cat /sys/block/md0/md/mismatch_cnt After investigating this issue on several machines it *seems* that the first drive does the trim correctly while the second one goes wild. At least the number and severity of errors found by a USB stick live session fsck.ext4 suggests this. To perform the single drive evaluation the RAID10 was started using a single drive at once: mdadm --assemble /dev/md127 /dev/nvme0n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root vgchange -a n /dev/VolGroup mdadm --stop /dev/md127 mdadm --assemble /dev/md127 /dev/nvme1n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root When starting these fscks without -n, on the first device it seems the directory structure is OK while on the second device there is only the lost+found folder left. Side-note: Another machine using HWE kernel 5.4.0-56 (after using -53 before) seems to have a quite similar issue. Unfortunately the risk/regression assessment in the aforementioned bug is not complete: the workaround only mitigates the issues during FS creation. This bug on the other hand is triggered by a weekly service (fstrim) causing severe file system corruption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927019] Re: Xorg freeze
Thanks for the bug report. Next time the problem happens please reboot and then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. Although I notice the attached logs already show your SSD is experiencing hardware errors. You might need to replace the SSD: [ 1633.238345] pcieport 1:e0:06.0: AER: Corrected error received: 1:e1:00.0 [ 1633.238381] nvme 1:e1:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 1633.238384] nvme 1:e1:00.0: device [15b7:5006] error status/mask=0001/e000 [ 1633.238387] nvme 1:e1:00.0:[ 0] RxErr (First) ** Summary changed: - Xorg freeze + System freeze ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927019 Title: System freeze Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 21.04 Freeze sometime ( using wayland ) . A black screen appear from top to bottom and ubuntu doesn't react to any keyboard shortcut. It's appears, maybe after 2 hours of work. I didn't see this bug with my previous ubuntu 20.10. My computer is a new DELL XPS 13 - intel core i7. I disabled the 4K screen and I am using a resolution 1920x1080. I enabled the night mode. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 4 00:10:39 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Xe Graphics [1028:0a5c] InstallationDate: Installed on 2021-04-30 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9305 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=37473b6f-8714-4a48-91c1-f6964b09347d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: 0PPYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd01/13/2021:br1.0:svnDellInc.:pnXPS139305:pvr:rvnDellInc.:rn0PPYW4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9305 dmi.product.sku: 0A5C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926062] Re: [hirsute] Can't turn bluetooth on again after turning it off
I was facing the same problem. My toggle was not at all working, neither from the top bar dropdown menu nor from the settings window. Switching on the toggle did not have any effect. I had also reported this bug. Someone in the comments had suggested a workaround to type this command in the terminal: systemctl restart Bluetooth This command kind of hard restarts the Bluetooth service and works for me for the time being until the bug is fixed. It might also help someone else. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute] Can't turn bluetooth on again after turning it off Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 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 ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927019] [NEW] System freeze
You have been subscribed to a public bug: Ubuntu 21.04 Freeze sometime ( using wayland ) . A black screen appear from top to bottom and ubuntu doesn't react to any keyboard shortcut. It's appears, maybe after 2 hours of work. I didn't see this bug with my previous ubuntu 20.10. My computer is a new DELL XPS 13 - intel core i7. I disabled the 4K screen and I am using a resolution 1920x1080. I enabled the night mode. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 4 00:10:39 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Xe Graphics [1028:0a5c] InstallationDate: Installed on 2021-04-30 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9305 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=37473b6f-8714-4a48-91c1-f6964b09347d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: 0PPYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd01/13/2021:br1.0:svnDellInc.:pnXPS139305:pvr:rvnDellInc.:rn0PPYW4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9305 dmi.product.sku: 0A5C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug freeze hirsute ubuntu -- System freeze https://bugs.launchpad.net/bugs/1927019 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 1926783] Re: [MSI MS-7B98] Sound is faster, high-pitched and distorted
Since you say the current kernel for Ubuntu 20.04 does not have the problem then it is considered Fix Released. If there is a newer kernel that does still have the bug then you should report it upstream, not here. ** Summary changed: - [USB-Audio - Saffire 6 USB, playback] Sound is faster, high-pitched and distorted + [MSI MS-7B98] Sound is faster, high-pitched and distorted ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => 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/1926783 Title: [MSI MS-7B98] Sound is faster, high-pitched and distorted Status in linux package in Ubuntu: Fix Released Bug description: It works normally when playing youtube videos, only audio files on PC are a problem. Also, kernel 5.8.0-50-generic does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.11.0-7614.15~1618626693~20.04~ecb25cd-generic 5.11.13 Uname: Linux 5.11.0-7614-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michal 1518 F pulseaudio /dev/snd/controlC2: michal 1518 F pulseaudio /dev/snd/controlC1: michal 1518 F pulseaudio /dev/snd/pcmC1D0p: michal 1518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Apr 30 17:05:38 2021 InstallationDate: Installed on 2021-01-31 (89 days ago) InstallationMedia: SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: TU104 HD Audio Controller - HDA NVidia Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - Saffire 6 USB, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd12/25/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926783] [NEW] [MSI MS-7B98] Sound is faster, high-pitched and distorted
You have been subscribed to a public bug: It works normally when playing youtube videos, only audio files on PC are a problem. Also, kernel 5.8.0-50-generic does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.11.0-7614.15~1618626693~20.04~ecb25cd-generic 5.11.13 Uname: Linux 5.11.0-7614-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michal 1518 F pulseaudio /dev/snd/controlC2: michal 1518 F pulseaudio /dev/snd/controlC1: michal 1518 F pulseaudio /dev/snd/pcmC1D0p: michal 1518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Apr 30 17:05:38 2021 InstallationDate: Installed on 2021-01-31 (89 days ago) InstallationMedia: SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: TU104 HD Audio Controller - HDA NVidia Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - Saffire 6 USB, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd12/25/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Tags: amd64 apport-bug focal third-party-packages -- [MSI MS-7B98] Sound is faster, high-pitched and distorted https://bugs.launchpad.net/bugs/1926783 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 1926062] Re: [RTL8821A][ideapad_bluetooth] I am unable to open/close/connect/scan bluetooth
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1926095, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - [RTL8821A][ideapad_bluetooth] I am unable to open/close/connect/scan bluetooth + [hirsute] Can't turn bluetooth on again after turning it off ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (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/1926062 Title: [hirsute] Can't turn bluetooth on again after turning it off Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 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 ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926095] Re: The bluetooth toggle is not working properly. Switching it on does not turn on the bluetooth. It remains off permanently.
*** This bug is a duplicate of bug 1926062 *** https://bugs.launchpad.net/bugs/1926062 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1926062, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1926062 [hirsute] Can't turn bluetooth on again after turning it off -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926095 Title: The bluetooth toggle is not working properly. Switching it on does not turn on the bluetooth. It remains off permanently. Status in bluez package in Ubuntu: Confirmed Bug description: I have described the issue here with screenshots https://askubuntu.com/q/1333848/1022606. Please have a look at the screenshots. Turning on the Bluetooth toggle has no effect. The system doesn't turn on the Bluetooth and does no scan for devices. Turning it on just moves the toggle, even the system doesn't acknowledge by showing that Bluetooth is on. The status remains off. It happened only after the upgrade I did yesterday. It was working fine before that. Please look into it. I cannot connect my Bluetooth earphones to my PC. This poses a lot of problems since my classes and courses are all online. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 00:09:35 2021 InstallationDate: Installed on 2019-12-05 (507 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to hirsute on 2021-04-24 (1 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927050] Re: Enable BLK_DEV_NVME =y to support "shielded VM minimal images"
** Description changed: This is requested by CPC -- see the title. + + [Impact] + nvme.ko exists outside the kernel currently + + [Fix] + Enable BLK_DEV_NVME=y + + [Test] + Tested by CPC crew / Google: + + > The test images have passed testing and we would like this enabled so we + > can have minimal images boot with NVME boot disk and so we can enable + > GCE confidential VMs with minimal images. + + + [Regression Potential] + Not aware of any. ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Changed in: linux-gcp (Ubuntu) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927050 Title: Enable BLK_DEV_NVME =y to support "shielded VM minimal images" Status in linux-gcp package in Ubuntu: In Progress Bug description: This is requested by CPC -- see the title. [Impact] nvme.ko exists outside the kernel currently [Fix] Enable BLK_DEV_NVME=y [Test] Tested by CPC crew / Google: > The test images have passed testing and we would like this enabled so we > can have minimal images boot with NVME boot disk and so we can enable > GCE confidential VMs with minimal images. [Regression Potential] Not aware of any. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1927050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926770] Re: Bluetooth switches back on each reboot
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1926770 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926770 Title: Bluetooth switches back on each reboot Status in bluez package in Ubuntu: Incomplete Bug description: Dear, When switching off Bluetooth in the settings menu, after each reboot and login into GNOME, the Bluetooth radio stack seems to be switched on again. Could this setting made by persistent over reboots? Thanks, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927050] [NEW] Enable BLK_DEV_NVME =y to support "shielded VM minimal images"
Public bug reported: This is requested by CPC -- see the title. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927050 Title: Enable BLK_DEV_NVME =y to support "shielded VM minimal images" Status in linux package in Ubuntu: New Bug description: This is requested by CPC -- see the title. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926032] Re: [i915] Screen "disconnects" when updating screen buffer
There certainly are invisible differences between Linux and Windows kernels internally how they implement HDMI signalling. So it is possible Linux is more fragile than Windows in this respect. As such, avoiding the receiver or changing cables might be a workaround. A proper fix in that case would go in the kernel so reassigning there... ** No longer affects: xorg-server (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/1926032 Title: [i915] Screen "disconnects" when updating screen buffer Status in linux package in Ubuntu: Incomplete Bug description: I have a problem in which the screen will behave as if I pulled the HDMI or turned the computer off (no source) for a few seconds until the screen comes back on again. This happens a lot when I open a new window, moves the mouse after it has been still for a while or I open a new window or move the current window. I can watch a whole movie without this problem but as soon as I pause or touch the controls of VLC or move the mouse the problem reocurr. It seems to be after a certain idle period most of the time, but not always. Sometimes it happens many times in a row. The setup is my home built media PC with intel integrated graphics (i5-9400) connected to a philips 55" TV (55POS901F) through a Pioneer AV receiver. I have tried probably every possible resolution and screen update frequency and the problem is still there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 24 21:57:54 2021 DistUpgraded: 2020-12-01 07:11:08,428 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation UHD Graphics 630 (Desktop 9 Series) [1849:3e98] InstallationDate: Installed on 2020-12-01 (144 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-12-01 (144 days ago) dmi.bios.date: 05/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.10 dmi.board.name: H310CM-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.10:bd05/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH310CM-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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/1926032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926032] Re: [i915] Screen "disconnects" when updating screen buffer
Most certainly not a problem with hdmi connection. I have had windows installed on the same machine without issues. The behavior is such that it is very clear that as soon as you move the mouse after a period of idle, the problem occurs. Also if the computer receives a notification after a period of idle it occurs. There is a definite link to activity which renders new information on the screen buffer. It can play a movie without a problem on vlc but when I pause, it disconnects the screen (presumably because the "pause" bars appear on the screen). If I right click to add subtitles or change something else in the video it also appears at the exact same time I click. This problem is very repeatable. I can do a phone quality video if that would be of interest. If it was a problem with hdmi it would be more random in behavior and it would be a problem on windows as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926032 Title: [i915] Screen "disconnects" when updating screen buffer Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a problem in which the screen will behave as if I pulled the HDMI or turned the computer off (no source) for a few seconds until the screen comes back on again. This happens a lot when I open a new window, moves the mouse after it has been still for a while or I open a new window or move the current window. I can watch a whole movie without this problem but as soon as I pause or touch the controls of VLC or move the mouse the problem reocurr. It seems to be after a certain idle period most of the time, but not always. Sometimes it happens many times in a row. The setup is my home built media PC with intel integrated graphics (i5-9400) connected to a philips 55" TV (55POS901F) through a Pioneer AV receiver. I have tried probably every possible resolution and screen update frequency and the problem is still there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 24 21:57:54 2021 DistUpgraded: 2020-12-01 07:11:08,428 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation UHD Graphics 630 (Desktop 9 Series) [1849:3e98] InstallationDate: Installed on 2020-12-01 (144 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-12-01 (144 days ago) dmi.bios.date: 05/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.10 dmi.board.name: H310CM-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.10:bd05/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH310CM-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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.l
[Kernel-packages] [Bug 1922738] Re: 5.4 kernel: when iommu is on crashdump fails
Hi Ioanna, may you please verify the focal kernel in -proposed resolves this bug? 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/1922738 Title: 5.4 kernel: when iommu is on crashdump fails Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [IMPACT] When iommu is enabled crashdump fails to be collected because crash-kernel crashes with following trace [1]. Commits that address it : 1ddb32da4a62 iommu/vt-d: Simplify check in identity_mapping() 96d170f3b1a6 iommu/vt-d: Remove deferred_attach_domain() a11bfde9c77d iommu/vt-d: Do deferred attachment in iommu_need_mapping() 034d98cc0cdc iommu/vt-d: Move deferred device attachment into helper function 1d4615978f52 iommu/vt-d: Add attach_deferred() helper 1ee0186b9a12 iommu/vt-d: Refactor find_domain() helper [TEST CASE] Install a 5.4 kernel, add intel_iommu=on and iommu=pt to grub cmdline and trigger a crash. The crash kernel that boots will crash with trace [1]. [REGRESSION POTENTIAL] 1) 1ee0186b9a12 iommu/vt-d: Refactor find_domain() helper Refactors find_domain() into two helpers: 1) find_domain() only returns the domain in use; 2) deferred_attach_domain() does the deferred domain attachment if required and return the domain in use. 2) 1d4615978f52 iommu/vt-d: Add attach_deferred() helper Add helper function to check if a device's attach process is deffered. Before this commit, this check was done with "dev->archdata.iommu == DEFER_DEVICE_DOMAIN_INFO". This commit wraps it into a function. Fixes (1). 3) 034d98cc0cdc iommu/vt-d: Move deferred device attachment into helper function Takes the code that does the deffered attachment from deferred_attach_domain() function and places it in new do_deferred_attach() function. Fixes (1). 4) a11bfde9c77d iommu/vt-d: Do deferred attachment in iommu_need_mapping() This one actually fixes the bug. Attachement of devive needs to happen before checking if device is identity mapped. Fixes (1). 5) 96d170f3b1a6 iommu/vt-d: Remove deferred_attach_domain() Code cleanup, removes deferred_attach_domain() which now is just a wrapper around find_domain and calls directly find_domain from caller sites. Fixes (1). 6) 1ddb32da4a62 iommu/vt-d: Simplify check in identity_mapping() Code cleanup. Fixes (1). Commits 2,3,5, and 6 are code movements/cleanups so little regression potential. Commit 1 is the intial code refactroring ( the rest of commits fix it) and commit 3 fixes the bug. So far testing has not revealed any regression. Any possible regression will regard device deffered attachment. [OTHER] Kernel affected 5.4. [1] https://pastebin.ubuntu.com/p/FNxTxjg3DV/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856010] Re: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail if running the whole suite
** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856010 Title: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail if running the whole suite Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: New Status in linux source package in Impish: In Progress Bug description: These 3 tests will fail with timeout when running the whole "net" test in ubuntu_kernel_selftests: * not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT * not ok 16 selftests: net: pmtu.sh # TIMEOUT * not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT However they will pass if you run them manually: So there must be some test in net that will cause this. From the test result it looks like the test was executed in the following sequence: ok 1 selftests: net: reuseport_bpf ok 2 selftests: net: reuseport_bpf_cpu ok 3 selftests: net: reuseport_bpf_numa ok 4 selftests: net: reuseport_dualstack # Successok 5 selftests: net: reuseaddr_conflict ok 6 selftests: net: tls ok 7 selftests: net: run_netsocktests ok 8 selftests: net: run_afpackettests ok 9 selftests: net: test_bpf.sh ok 10 selftests: net: netdevice.sh ok 11 selftests: net: rtnetlink.sh not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT not ok 13 selftests: net: test_blackhole_dev.sh # exit=1 ok 14 selftests: net: fib_tests.sh ok 15 selftests: net: fib-onlink-tests.sh not ok 16 selftests: net: pmtu.sh # TIMEOUT ok 17 selftests: net: udpgso.sh not ok 18 selftests: net: ip_defrag.sh # exit=255 not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT ok 20 selftests: net: fib_rule_tests.sh not ok 21 selftests: net: msg_zerocopy.sh # exit=1 ok 22 selftests: net: psock_snd.sh ok 23 selftests: net: udpgro_bench.sh ok 24 selftests: net: udpgro.sh ok 25 selftests: net: test_vxlan_under_vrf.sh ok 26 selftests: net: reuseport_addr_any.sh ok 27 selftests: net: test_vxlan_fdb_changelink.sh ok 28 selftests: net: so_txtime.sh ok 29 selftests: net: ipv6_flowlabel.sh ok 30 selftests: net: tcp_fastopen_backup_key.sh ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1009-aws 5.3.0-1009.10 ProcVersionSignature: User Name 5.3.0-1009.10-aws 5.3.13 Uname: Linux 5.3.0-1009-aws aarch64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: arm64 Date: Wed Dec 11 06:42:39 2019 Ec2AMI: ami-047cec24582f6ae0d Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2c Ec2InstanceType: a1.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1856010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915322] Re: [nvidia] System freezes on resume from sleep
[Expired for nvidia-graphics-drivers-460 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915322 Title: [nvidia] System freezes on resume from sleep Status in linux-hwe-5.8 package in Ubuntu: Expired Status in nvidia-graphics-drivers-460 package in Ubuntu: Expired Bug description: Hey guys! First up, I've been using ubuntu on and off since I was about twelve, and I love this os.Thank you guys for the hard work! Second, I've been having an unfortunate bug on my laptop for quite some time now. I'm using an acer aspire e5-575g-55nw and every time my laptop goes into suspend, I can't get back to any kind of GUI after waking it up, instead going to a black screen with a single blinking white - symbol in the top left corner. i've tried just about every fix I could find on the internet, without being able to find any way back to my login screen or desktop. Note that this does not happen when my laptop goes to sleep on it's own after a set ammount of time, only when i put it into suspend or close the lid. I hope I included enough information, please let me know if you need any other information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 15:15:18 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] Acer Aspire E5-575G [1025:1094] InstallationDate: Installed on 2021-02-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57f2 Realtek Semiconductor Corp. HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=f1010786-e2a1-44b4-a3b8-6a48523960df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.release: 1.47 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.47 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.47 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.50 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:br1.47:efr2.50:svnAcer:pnAspireE5-575G:pvrV1.47:rvnAcer:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.47 dmi.product.version: V1.47 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 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.9-2ubunt
[Kernel-packages] [Bug 1915322] Re: [nvidia] System freezes on resume from sleep
[Expired for linux-hwe-5.8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-hwe-5.8 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915322 Title: [nvidia] System freezes on resume from sleep Status in linux-hwe-5.8 package in Ubuntu: Expired Status in nvidia-graphics-drivers-460 package in Ubuntu: Expired Bug description: Hey guys! First up, I've been using ubuntu on and off since I was about twelve, and I love this os.Thank you guys for the hard work! Second, I've been having an unfortunate bug on my laptop for quite some time now. I'm using an acer aspire e5-575g-55nw and every time my laptop goes into suspend, I can't get back to any kind of GUI after waking it up, instead going to a black screen with a single blinking white - symbol in the top left corner. i've tried just about every fix I could find on the internet, without being able to find any way back to my login screen or desktop. Note that this does not happen when my laptop goes to sleep on it's own after a set ammount of time, only when i put it into suspend or close the lid. I hope I included enough information, please let me know if you need any other information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 15:15:18 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] Acer Aspire E5-575G [1025:1094] InstallationDate: Installed on 2021-02-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57f2 Realtek Semiconductor Corp. HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=f1010786-e2a1-44b4-a3b8-6a48523960df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.release: 1.47 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.47 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.47 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.50 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:br1.47:efr2.50:svnAcer:pnAspireE5-575G:pvrV1.47:rvnAcer:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.47 dmi.product.version: V1.47 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 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.9-2ubuntu1.2~20.04.1 version.xserv
[Kernel-packages] [Bug 1926062] Re: [ideapad_bluetooth] I am unable to open/close/connect/scan bluetooth
** Summary changed: - I am unable to open/close/connect/scan bluetooth + [ideapad_bluetooth] I am unable to open/close/connect/scan bluetooth ** Summary changed: - [ideapad_bluetooth] I am unable to open/close/connect/scan bluetooth + [RTL8821A][ideapad_bluetooth] I am unable to open/close/connect/scan bluetooth -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [RTL8821A][ideapad_bluetooth] I am unable to open/close/connect/scan bluetooth Status in linux package in Ubuntu: Confirmed Bug description: When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 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 ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856010] Re: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail if running the whole suite
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Assignee: Po-Hsu Lin (cypressyew) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856010 Title: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail if running the whole suite Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: New Status in linux source package in Impish: In Progress Bug description: These 3 tests will fail with timeout when running the whole "net" test in ubuntu_kernel_selftests: * not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT * not ok 16 selftests: net: pmtu.sh # TIMEOUT * not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT However they will pass if you run them manually: So there must be some test in net that will cause this. From the test result it looks like the test was executed in the following sequence: ok 1 selftests: net: reuseport_bpf ok 2 selftests: net: reuseport_bpf_cpu ok 3 selftests: net: reuseport_bpf_numa ok 4 selftests: net: reuseport_dualstack # Successok 5 selftests: net: reuseaddr_conflict ok 6 selftests: net: tls ok 7 selftests: net: run_netsocktests ok 8 selftests: net: run_afpackettests ok 9 selftests: net: test_bpf.sh ok 10 selftests: net: netdevice.sh ok 11 selftests: net: rtnetlink.sh not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT not ok 13 selftests: net: test_blackhole_dev.sh # exit=1 ok 14 selftests: net: fib_tests.sh ok 15 selftests: net: fib-onlink-tests.sh not ok 16 selftests: net: pmtu.sh # TIMEOUT ok 17 selftests: net: udpgso.sh not ok 18 selftests: net: ip_defrag.sh # exit=255 not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT ok 20 selftests: net: fib_rule_tests.sh not ok 21 selftests: net: msg_zerocopy.sh # exit=1 ok 22 selftests: net: psock_snd.sh ok 23 selftests: net: udpgro_bench.sh ok 24 selftests: net: udpgro.sh ok 25 selftests: net: test_vxlan_under_vrf.sh ok 26 selftests: net: reuseport_addr_any.sh ok 27 selftests: net: test_vxlan_fdb_changelink.sh ok 28 selftests: net: so_txtime.sh ok 29 selftests: net: ipv6_flowlabel.sh ok 30 selftests: net: tcp_fastopen_backup_key.sh ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1009-aws 5.3.0-1009.10 ProcVersionSignature: User Name 5.3.0-1009.10-aws 5.3.13 Uname: Linux 5.3.0-1009-aws aarch64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: arm64 Date: Wed Dec 11 06:42:39 2019 Ec2AMI: ami-047cec24582f6ae0d Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2c Ec2InstanceType: a1.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1856010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926084] Re: Bluetooth speakers reconnect randomly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926084 Title: [hirsute] Bluetooth speakers reconnect randomly Status in bluez package in Ubuntu: Confirmed Bug description: Bluetooth speakers reconnect randomly. The onlt workaround that seems to work is to remove speakers from paired devies, restart buetooth service and connect them once again. Once these stepss are performed connection become stable until reboot or hibernation. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Apr 25 17:22:11 2021 InstallationDate: Installed on 2021-04-13 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-18 (6 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 44:AF:28:F7:A9:6C ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:2239397 acl:225 sco:0 events:318945 errors:0 TX bytes:207283666 acl:315238 sco:0 commands:3564 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926084] Re: [hirsute] Bluetooth speakers reconnect randomly
** Summary changed: - Bluetooth speakers reconnect randomly + [hirsute] Bluetooth speakers reconnect randomly -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926084 Title: [hirsute] Bluetooth speakers reconnect randomly Status in bluez package in Ubuntu: Confirmed Bug description: Bluetooth speakers reconnect randomly. The onlt workaround that seems to work is to remove speakers from paired devies, restart buetooth service and connect them once again. Once these stepss are performed connection become stable until reboot or hibernation. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Apr 25 17:22:11 2021 InstallationDate: Installed on 2021-04-13 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-18 (6 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 44:AF:28:F7:A9:6C ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:2239397 acl:225 sco:0 events:318945 errors:0 TX bytes:207283666 acl:315238 sco:0 commands:3564 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926145] Re: bluetooth disconnects and reconnects on 21.04
*** This bug is a duplicate of bug 1926084 *** https://bugs.launchpad.net/bugs/1926084 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1926084, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1926084 Bluetooth speakers reconnect randomly -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926145 Title: bluetooth disconnects and reconnects on 21.04 Status in bluez package in Ubuntu: New Bug description: Bluetooth speaker disconnects randomly and reconnects again. Problem occurred after upgrade to Ubuntu 21.04 ( -d ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926145/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910323] Re: Fix implicit declaration warnings for kselftests/memfd test on newer releases
** Changed in: linux-oem-5.6 (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-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1910323
Title:
Fix implicit declaration warnings for kselftests/memfd test on newer
releases
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.6 package in Ubuntu:
New
Status in linux source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix Released
Bug description:
[Impact]
While debugging bug 1910277, I found that the test compilation will
print some warnings:
memfd_test.c:64:7: warning: implicit declaration of function ‘open’;
memfd_test.c:90:6: warning: implicit declaration of function ‘fcntl’
memfd_test.c:397:6: warning: implicit declaration of function ‘fallocate’;
fuse_test.c:67:6: warning: implicit declaration of function ‘fcntl’
fuse_test.c:261:7: warning: implicit declaration of function ‘open’;
It's harmless but fixing this we can make the test report easier to
read.
[Fix]
* 1c49e3783f8899 ("selftests/memfd: Fix implicit declaration warnings")
This fix can be cherry-picked into F/F-oem-5.6/G and compiled without
any problem. Older kernel does not have this issue since they're
missing some other commits.
[Test Case]
Build the memfd test in tools/testing/selftests/ with:
sudo make TARGETS=memfd
With this fix, these warnings will be gone.
[Where problems could occur]
This fix is just for fixing the test case compilation, so it's not
affecting real kernel functionality.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910323/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922759] Re: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10
** Also affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux-oem-5.6 (Ubuntu Groovy) ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1922759 Title: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10 Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Bug description: The Clevo NH55RZQ and Intel NUC10 need SND_PCI_QUIRKs to fix wrong pin setup and enable microphones to work correctly when using via the audio jacks. Patches that are fixing these problems have already been accepted to current Linux stable releases: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=48698c973e6b4dde94d87cd1ded56d9436e9c97d https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=73e7161eab5dee98114987239ec9c87fe8034ddb Commit-hash: 48698c973e6b4dde94d87cd1ded56d9436e9c97d 73e7161eab5dee98114987239ec9c87fe8034ddb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862559] Re: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min
** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862559 Title: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min Status in gdm3 package in Ubuntu: Won't Fix Bug description: UBUNTU 19.10 installed on ThunderX2 saber ARM64 machine. If the system left idle for ~22min it becomes unresponsive. The system will not take any inputs like from UART, ping ..etc. The system will completely freeze and we need to hard reset the system. It could be possible the system goes to hibernate state and could not able to come out of the state. Dmesg log when system halts/no response on Saber boards (TX2) Ubuntu 19.10 ubuntu ttyAMA0 ubuntu login: ubuntu Password: Last login: Wed Jan 29 20:08:22 PST 2020 on ttyAMA0 Welcome to Ubuntu 19.10 (GNU/Linux 5.3.0-26-generic aarch64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage ubuntu@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan [ +0.732512] audit: type=1400 audit(1580358920.412:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=3087 comm="apparmor_parser" [ +0.64] audit: type=1400 audit(1580358920.412:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ippusbxd" pid=3091 comm="apparmor_parser" [ +0.000168] audit: type=1400 audit(1580358920.412:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=3086 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=3086 comm="apparmor_parser" [ +0.000546] audit: type=1400 audit(1580358920.412:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=3085 comm="apparmor_parser" [ +0.06] audit: type=1400 audit(1580358920.412:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=3085 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=3085 comm="apparmor_parser" [ +0.000854] audit: type=1400 audit(1580358920.412:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=3089 comm="apparmor_parser" [ +0.002667] audit: type=1400 audit(1580358920.416:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=3093 comm="apparmor_parser" [ +0.04] audit: type=1400 audit(1580358920.416:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=3093 comm="apparmor_parser" [ +1.382579] igb :92:00.1 enp146s0f1: igb: enp146s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ +0.000299] IPv6: ADDRCONF(NETDEV_CHANGE): enp146s0f1: link becomes ready [ +3.131173] mpt3sas_cm0: port enable: SUCCESS [Jan29 20:36] random: crng init done [ +0.04] random: 7 urandom warning(s) missed due to ratelimiting *[Jan29 20:37] rfkill: input handler disabled* *[Jan29 20:57] PM: suspend entry (deep)* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927037] [NEW] ath9k driver: miniPCIe Atheros AR93xx not recognized
Public bug reported: Expected behavior: Network adapter should be visible via `iw list`, `iwconfig`, and `ifconfig`. Actual behavior: Network adapter is visible in `lspci` and `lshw`, but not in `iw list`, `iwconfig`, or `ifconfig` Details: The Atheros network card is detected by the ath9k driver when installed into a machine with x86_64 architecture. When the same card is installed into a miniPCIe-to-PCIe adapter, then plugged into a Raspberry Pi CM4 IO breakout board, the network adapter can be seen via lspci and lshw but is not seen by iw, iwconfig, or ifconfig. lspci: ubuntu@ubuntu:~$ sudo lspci -v 00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 20) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 41 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: -0fff [size=4K] Memory behind bridge: f800-f80f [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: [48] Power Management version 3 Capabilities: [ac] Express Root Port (Slot-), MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [180] Vendor Specific Information: ID= Rev=0 Len=028 Capabilities: [240] L1 PM Substates Kernel driver in use: pcieport 01:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01) Subsystem: Qualcomm Atheros AR93xx Wireless Network Adapter Flags: fast devsel, IRQ 255 Memory at 6 (64-bit, non-prefetchable) [disabled] [size=128K] Expansion ROM at 60002 [virtual] [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [300] Device Serial Number 00-00-00-00-00-00-00-00 - lshw: ubuntu@ubuntu:~$ sudo lshw -c net *-network UNCLAIMED description: Network controller product: AR93xx Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:01:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress cap_list configuration: latency=0 resources: memory:6-60001 memory:60002-60002 *-network description: Ethernet interface physical id: 1 logical name: eth0 serial: dc:a6:32:f4:69:36 size: 1Gbit/s capacity: 1Gbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=bcmgenet driverversion=v2.0 duplex=full ip=REDACTED link=yes multicast=yes port=MII speed=1Gbit/s - iw list/iwconfig: ubuntu@ubuntu:~$ iw list ubuntu@ubuntu:~$ iwconfig lono wireless extensions. eth0 no wireless extensions. - ubuntu@ubuntu:~$ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-1034-raspi 5.4.0-1034.37 ProcVersionSignature: User Name 5.4.0-1034.37-raspi 5.4.101 Uname: Linux 5.4.0-1034-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: arm64 CasperMD5CheckResult: skip Date: Tue May 4 02:59:25 2021 ImageMediaBuild: 20210201.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 focal uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1927037 Title: ath9k driver: miniPCIe Atheros AR93xx not recognized Status in linux-raspi package in Ubuntu: New Bug description: Expected behavior: Network adapter should be visible via `iw list`, `iwconfig`, and `ifconfig`. Actual behavior: Network adapter is visible in `lspci` and `lshw`, but not in `iw list`, `iwconfig`, or `ifconfig` Details: The Atheros network card is detected by the ath9k driver when installed into a machine with x86_64 architecture. When the same card is installed into a miniPCIe-to-PCIe adapter, then plugged into a Raspberry Pi CM4 IO breakout board, the network adapter can be seen via lspci and lshw but is not seen by iw, iwconfig, or ifconfig. lspci: ubuntu@ubuntu:~$ sudo lspci -v 00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 20) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 41 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O
[Kernel-packages] [Bug 1920246] Re: Focal update: v5.4.106 upstream stable release
** Also affects: linux-aws-5.4 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-aws-5.4 (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux-aws-5.4 (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1920246 Title: Focal update: v5.4.106 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: New Status in linux-aws-5.4 package in Ubuntu: New Status in linux-gkeop-5.4 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-aws source package in Bionic: New Status in linux-aws-5.4 source package in Bionic: In Progress Status in linux-gkeop-5.4 source package in Bionic: In Progress Status in linux source package in Focal: Fix Committed Status in linux-aws source package in Focal: In Progress Status in linux-aws-5.4 source package in Focal: New Status in linux-gkeop-5.4 source package in Focal: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.106 upstream stable release from git://git.kernel.org/ uapi: nfnetlink_cthelper.h: fix userspace compilation error powerpc/pseries: Don't enforce MSI affinity with kdump ath9k: fix transmitting to stations in dynamic SMPS mode net: Fix gro aggregation for udp encaps with zero csum net: check if protocol extracted by virtio_net_hdr_set_proto is correct net: avoid infinite loop in mpls_gso_segment when mpls_hlen == 0 sh_eth: fix TRSCER mask for SH771x can: skb: can_skb_set_owner(): fix ref counting if socket was closed before setting skb ownership can: flexcan: assert FRZ bit in flexcan_chip_freeze() can: flexcan: enable RX FIFO after FRZ/HALT valid can: flexcan: invoke flexcan_chip_freeze() to enter freeze mode can: tcan4x5x: tcan4x5x_init(): fix initialization - clear MRAM before entering Normal Mode tcp: add sanity tests to TCP_QUEUE_SEQ netfilter: nf_nat: undo erroneous tcp edemux lookup netfilter: x_tables: gpf inside xt_find_revision() selftests/bpf: No need to drop the packet when there is no geneve opt selftests/bpf: Mask bpf_csum_diff() return value to 16 bits in test_verifier samples, bpf: Add missing munmap in xdpsock ibmvnic: always store valid MAC address mt76: dma: do not report truncated frames to mac80211 powerpc/603: Fix protection of user pages mapped with PROT_NONE mount: fix mounting of detached mounts onto targets that reside on shared mounts cifs: return proper error code in statfs(2) Revert "mm, slub: consider rest of partial list if acquire_slab() fails" net: enetc: don't overwrite the RSS indirection table when initializing net/mlx4_en: update moderation when config reset net: stmmac: fix incorrect DMA channel intr enable setting of EQoS v4.10 nexthop: Do not flush blackhole nexthops when loopback goes down net: sched: avoid duplicates in classes dump net: usb: qmi_wwan: allow qmimux add/del with master up netdevsim: init u64 stats for 32bit hardware cipso,calipso: resolve a number of problems with the DOI refcounts net: lapbether: Remove netif_start_queue / netif_stop_queue net: davicom: Fix regulator not turned off on failed probe net: davicom: Fix regulator not turned off on driver removal net: qrtr: fix error return code of qrtr_sendmsg() ixgbe: fail to create xfrm offload of IPsec tunnel mode SA net: stmmac: stop each tx channel independently net: stmmac: fix watchdog timeout during suspend/resume stress test selftests: forwarding: Fix race condition in mirror installation perf traceevent: Ensure read cmdlines are null terminated. net: hns3: fix query vlan mask value error for flow director net: hns3: fix bug when calculating the TCAM table info s390/cio: return -EFAULT if copy_to_user() fails again bnxt_en: reliably allocate IRQ table on reset to avoid crash drm/compat: Clear bounce structures drm/shmem-helper: Check for purged buffers in fault handler drm/shmem-helper: Don't remove the offset in vm_area_struct pgoff drm: meson_drv add shutdown function s390/cio: return -EFAULT if copy_to_user() fails s390/crypto: return -EFAULT if copy_to_user() fails qxl: Fix uninitialised struct field head.surface_id sh_eth: fix TRSCER mask for R7S9210 media: usbtv: Fix deadlock on suspend media: v4l: vsp1: Fix uif null pointer access media: v4l: vsp1: Fix bru null pointer
[Kernel-packages] [Bug 1925824] 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/1925824 Title: [Avita NS14A2] Screen doesn't display on warm boot and turning on after Suspend (i915 :00:02.0: [drm] *ERROR* failed to enable link training) Status in linux package in Ubuntu: Confirmed Bug description: I have Avita NS14A2 laptop where i dual boot windows 10 and Ubuntu 20.04. In past few days might be after installing updates I am facing issue where my screen dont display at all when i first boot it and after multiple force shut down and then boot in it work, even on doing Suspend and then opening it, screen didnt not display for about 5-6 minutes, and then shows login screen. On checking logs software i got these line on those time stamp when display doesnt shows this is the line: (Hardware) i915 :00:02.0: [drm] *ERROR* failed to enable link training this line continues for about 30-40 times on average during time when screen doesnt display anything on turing on. So I think there is some issue with it. As I primarily use Ubuntu 20.04 so didnt check it with windows 10 but on doing cold boot it didnt even shows the boot menu where i can choose between Ubuntu 20.04 and Windows 10. But once screen starts displaying i dont see that error in logs software anymore and screen doesnt freezes or hangs. It only happen when i either open after suspend or do cold boot. Please consider this issue on urgent basis, as it takes a lot of time and efforts to make screen display something. :( And please let me know whether I should do fresh installation of ubuntu 20.04 again. Sorry for any grammatical mistakes. :) Thank you, Bipul Harsh bipulharsh...@gmail.com ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 20:36:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation UHD Graphics 620 [8086:5917] InstallationDate: Installed on 2020-11-22 (151 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: AVITA NS14A2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=011d61ba-ef72-40ed-9957-25830622d9c7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2019 dmi.bios.release: 0.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BSR5IPHK-14UF80-AVI-V22 dmi.board.asset.tag: Default string dmi.board.name: 6614UFWC80 dmi.board.vendor: AVITA dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: AVITA dmi.chassis.version: Default string dmi.ec.firmware.release: 0.22 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBSR5IPHK-14UF80-AVI-V22:bd04/19/2019:br0.22:efr0.22:svnAVITA:pnNS14A2:pvrDefaultstring:rvnAVITA:rn6614UFWC80:rvrDefaultstring:cvnAVITA:ct10:cvrDefaultstring: dmi.product.family: CN6614 dmi.product.name: NS14A2 dmi.product.sku: CN6614F56U1IN-MB dmi.product.version: Default string dmi.sys.vendor: AVITA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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/1925824/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926050] Re: Web benchmark freezing and crashing the system
Next time the problem happens, after rebooting please run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. Please also follow these instructions to check for application crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: linux (Ubuntu) => linux-hwe-5.8 (Ubuntu) ** Changed in: linux-hwe-5.8 (Ubuntu) Status: Confirmed => Incomplete ** Summary changed: - Web benchmark freezing and crashing the system + [radeon] Web benchmark freezing and crashing the system ** No longer affects: mesa (Ubuntu) ** No longer affects: wayland (Ubuntu) ** No longer affects: xorg-server (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/1926050 Title: [radeon] Web benchmark freezing and crashing the system Status in linux-hwe-5.8 package in Ubuntu: Incomplete Bug description: Expected behavior: perform the "Basemark Web 3.0" benchmark (Firefox 87 and 88), at most a loss of performance. Real behavior: the benchmark completely crashes the system in one of the initial stages (4). The screen presents graphical distortion (it never happens), intense crashes and sometimes it is solved with the automatic suspension of the computer (which remains on at times). But it doesn't usually come back from the crash. The problem happens with the onboard ATI RADEON 3000 (RS780 driver) and it happens in both xorg and wayland. Ubuntu and kernel duly updated to the present date. Crash moment: WebGL 1.0.2 Test (test 4/20); "Loading scene_uv2.DAE" Benchmark website: https://web.basemark.com/ Motherboard: GA78LMT Ubuntu 20.04.2 LTS Kernel 5.8.0-50-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: poe1860 F pulseaudio /dev/snd/pcmC2D0p: poe1860 F...m pulseaudio /dev/snd/controlC0: poe1860 F pulseaudio /dev/snd/controlC1: poe1860 F pulseaudio BootLog: Error: [Errno 13] Permissão recusada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2021-03-25 15:17:02,784 DEBUG /openCache(), new cache size 67025 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2021-03-04 (51 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 Package: xorg-server (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash radeon.audio=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal wayland-session wayland-session ubuntu Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-03-25 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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-hwe-5.8/+bug/1926050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packag
[Kernel-packages] [Bug 1926032] Re: Screen "disconnects" when updating screen buffer
This sounds like an HDMI connection/signalling problem. Please check to see if a direct connection (no receiver), and even a new cable, exhibits the same problem. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Summary changed: - Screen "disconnects" when updating screen buffer + [i915] Screen "disconnects" when updating screen buffer ** 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/1926032 Title: [i915] Screen "disconnects" when updating screen buffer Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a problem in which the screen will behave as if I pulled the HDMI or turned the computer off (no source) for a few seconds until the screen comes back on again. This happens a lot when I open a new window, moves the mouse after it has been still for a while or I open a new window or move the current window. I can watch a whole movie without this problem but as soon as I pause or touch the controls of VLC or move the mouse the problem reocurr. It seems to be after a certain idle period most of the time, but not always. Sometimes it happens many times in a row. The setup is my home built media PC with intel integrated graphics (i5-9400) connected to a philips 55" TV (55POS901F) through a Pioneer AV receiver. I have tried probably every possible resolution and screen update frequency and the problem is still there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 24 21:57:54 2021 DistUpgraded: 2020-12-01 07:11:08,428 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation UHD Graphics 630 (Desktop 9 Series) [1849:3e98] InstallationDate: Installed on 2020-12-01 (144 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-12-01 (144 days ago) dmi.bios.date: 05/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.10 dmi.board.name: H310CM-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.10:bd05/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH310CM-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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/1926032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926023] Re: display broken on logout
** Tags added: nvidia ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Package changed: xorg-server (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu) ** Summary changed: - display broken on logout + [nvidia] display broken on logout ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1926023 Title: [nvidia] display broken on logout Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: I can login and use the system, but when I logout, the monitor complains that it can't display the video mode. Pressing various keys and clicking randomly doesn't help, I have to press the hard reset button to login again. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:07: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 460.73.01 Thu Apr 1 21:40:36 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 24 18:13:51 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU106 [GeForce RTX 2060 SUPER] [1462:c752] InstallationDate: Installed on 2021-04-24 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=901be83b-8764-4544-acd9-b13439d1ab8f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: B450M Pro4-F dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/01/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4-F:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 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.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1926023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922334] Re: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16)
@Georgi, Please help to collect another one. Change kernel to 5.10-oem-1025 and enable drm debug(0x10e) please dump dmesg after issue is triggered. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1922334 Title: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16) Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-oem-5.6 package in Ubuntu: New Bug description: I've recently upgraded my workhorse from XPS 9560 (2016) to a newer generation XPS 9500 (2020) and ran into several things that feel like regressions, but are probably related to hardware changes. This is one of them. tl;dr: When using XPS 9500 with a TB16 dock and an external monitor (Benq EX2780Q) connected to the dock via USB-C to USB-C (DP alternate mode), most of the time the monitor fails to wake up after going blank. details: Simplest way to reproduce is for hit Super+L, wait for the monitor to properly go in standby, then type something in or move the mouse to wake it up. 8 times out of 10 it does not wake up when using XPS 9500. Most of the time this can be fixed by power cycling the monitor, however this has a seemingly random chance of triggering two other issues: 1. The system to lose sight of the monitor for a brief period of time, which sometimes causes it to hang with a black screen and needs some combination of restarting the monitor, the dock, and the laptop, because there is a separate USB issue making hot-plugging unusable. 2. The monitor itself gets stuck in a weird standby state where it stops reacting to button presses and I need to hold the power button a bit longer for it to sort of hard reset? Notably, it wakes up fine every time when using XPS 9560 or Precision 5520 in the same setup which I have been using for ages. This becomes particularly troublesome when screens go into short-lived standby during boot: after the Dell logo, after entering the LUKS password, after logging in. Each of these points has a chance of triggering the bug, because it looks like there is some sort of mode change and waking signal submission happening between them that triggers it. I had to disable screen timeout as a temporary workaround to be able to work on this system at all without having to play "monitor wake lottery" every time I go brew a cuppa. The workaround at boot time is to either re-roll the lottery, or boot with the dock connected and lid open, then close the lid and keep working from there. The dock, the monitor, all USB peripherals are the same in both cases - it's literally just the TB16 cable plugged into a different laptop. I have attempted 5.8 Ubuntu generic, 5.6 OEM (-20.04) and 5.10 OEM (-20.04b and -20.04-edge) kernels on the 9500 with same results. I have attempted disabling USB autosuspend via a GRUB kernel parameter to usbcore. I have attempted both NVidia and Intel GPUs. I have attempted playing with BIOS settings: wake on dell usb-c docks, disable early sign of life for both checkboxes, disabling SGX and SMM, checking all 3 boxes for Thunderbolt and switching off Thunderbolt security. None of these make a noticeable difference. Since it was fine with 9560, 5520 and a friend with a 9570 has no issues either, my gut feeling is that this is due to the upgrade from Alpine Ridge to a Titan Ridge Thunderbolt controller that happened in this generation - something wrong with the driver, or the firmware may have missed some of the "lessons learned" in Alpine Ridge and caused this regression. That would also make it applicable to 9300, which has a "developer edition" option under Project Sputnik and several reports of the same problem scattered across the internet: https://www.dell.com/community/XPS/XPS-13-9300-with-WD19TB-External-display-not-coming-on-after/td-p/7676922 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342 (may be a duplicate, but for WD19TB dock on 9300, so may be slightly different too) https://www.reddit.com/r/linuxquestions/comments/ka0w2j/monitor_doesnt_wake_from_sleep/ etc etc. Those reports suggest high bandwidth usage sometimes affects it, so it's worth noting that my external monitor is a 1440p 144Hz one that uses tons of bandwidth indeed. The only hint in terms of logs seems to be this message in dmesg that I see when power cycling the monitor and getting back into the system: [ 250.777684] pcieport :09:04.0: pciehp: Slot(0-1): Card not present [ 250.777695] xhci_hcd :0b:00.0: can't change power state from D3cold to D0 (config space inaccessible) [ 250.778293] xhci_hcd :0b:00.0: can't change power state from D3hot to D0 (config space inaccessible) [ 250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19 [ 250.7783
[Kernel-packages] [Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA
@Henrik, When you try the kernel(#31), is issue gone? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912057 Title: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA Status in linux package in Ubuntu: Incomplete Bug description: After boot the idle power consumption is around 2.3 W but after suspend it is 4.7 W. The measurement is 5-10 min after boot/resume - looking at "top" to see system was idle. This is consistent - I have tried more that 10 times. BIOS is updated to latest version. I have checked power consumption with external meter - and confirmed that it is higher. I have attached output of: sudo powertop -t 60 -r --html=before.html (and after) I have noticed that Package C-state 6 is reached before suspend but not after. I expect that idle power consumption after suspend should be the same as before. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-38-generic 5.8.0-38.43 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hjh1448 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 15:49:32 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2021-01-03 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425JA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425JA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425JA_UX425JA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925824] Re: [Avita NS14A2] Screen doesn't display on warm boot and turning on after Suspend (i915 0000:00:02.0: [drm] *ERROR* failed to enable link training)
** Summary changed: - Display Error (hardware bug: Screen doesnt display on warm boot and turning on after Suspend) + [Avita NS14A2] Screen doesn't display on warm boot and turning on after Suspend (i915 :00:02.0: [drm] *ERROR* failed to enable link training) ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925824 Title: [Avita NS14A2] Screen doesn't display on warm boot and turning on after Suspend (i915 :00:02.0: [drm] *ERROR* failed to enable link training) Status in linux package in Ubuntu: New Bug description: I have Avita NS14A2 laptop where i dual boot windows 10 and Ubuntu 20.04. In past few days might be after installing updates I am facing issue where my screen dont display at all when i first boot it and after multiple force shut down and then boot in it work, even on doing Suspend and then opening it, screen didnt not display for about 5-6 minutes, and then shows login screen. On checking logs software i got these line on those time stamp when display doesnt shows this is the line: (Hardware) i915 :00:02.0: [drm] *ERROR* failed to enable link training this line continues for about 30-40 times on average during time when screen doesnt display anything on turing on. So I think there is some issue with it. As I primarily use Ubuntu 20.04 so didnt check it with windows 10 but on doing cold boot it didnt even shows the boot menu where i can choose between Ubuntu 20.04 and Windows 10. But once screen starts displaying i dont see that error in logs software anymore and screen doesnt freezes or hangs. It only happen when i either open after suspend or do cold boot. Please consider this issue on urgent basis, as it takes a lot of time and efforts to make screen display something. :( And please let me know whether I should do fresh installation of ubuntu 20.04 again. Sorry for any grammatical mistakes. :) Thank you, Bipul Harsh bipulharsh...@gmail.com ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 20:36:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation UHD Graphics 620 [8086:5917] InstallationDate: Installed on 2020-11-22 (151 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: AVITA NS14A2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=011d61ba-ef72-40ed-9957-25830622d9c7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2019 dmi.bios.release: 0.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BSR5IPHK-14UF80-AVI-V22 dmi.board.asset.tag: Default string dmi.board.name: 6614UFWC80 dmi.board.vendor: AVITA dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: AVITA dmi.chassis.version: Default string dmi.ec.firmware.release: 0.22 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBSR5IPHK-14UF80-AVI-V22:bd04/19/2019:br0.22:efr0.22:svnAVITA:pnNS14A2:pvrDefaultstring:rvnAVITA:rn6614UFWC80:rvrDefaultstring:cvnAVITA:ct10:cvrDefaultstring: dmi.product.family: CN6614 dmi.product.name: NS14A2 dmi.product.sku: CN6614F56U1IN-MB dmi.product.version: Default string dmi.sys.vendor: AVITA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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/1925824/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages P
[Kernel-packages] [Bug 1922336] Re: ACPI errors and USB reset loop when hot-plugging a Titan Ridge laptop into a dock (9500, TB16)
@Georgi, When you try drm-tip, did you find this issue? https://bugs.launchpad.net/dell-sputnik/+bug/1922334/comments/25 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1922336 Title: ACPI errors and USB reset loop when hot-plugging a Titan Ridge laptop into a dock (9500, TB16) Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-oem-5.6 package in Ubuntu: New Bug description: I've recently upgraded my workhorse from XPS 9560 (2016) to a newer generation XPS 9500 (2020) and ran into several things that feel like regressions, but are probably related to hardware changes. This is one of them. tl;dr: When using XPS 9500 with a TB16 dock, hot-plugging the dock causes ACPI errors in dmesg and some kind of reset loop with USB peripherals connected via the dock. details: USB peripherals keep reconnecting according to dmesg, but in practice they barely ever finish registering with the system before disappearing again. Maybe 1 out of 40 USB keyboard presses registers while this is happening. At this point my choices are to either reboot with the dock connected or work without the dock and consequently without any peripherals on my desk. Booting with an open lid and the dock connected works fine until I re-plug the dock. Notably, it hot-plugs fine every time when using XPS 9560 or Precision 5520 in the same setup which I have been using for ages and which had similar problems until around kernel 4.13. Since it was fine with 9560, 5520 and a friend with a 9570 has no issues either, my gut feeling is that this is due to the upgrade from Alpine Ridge to a Titan Ridge Thunderbolt controller that happened in this generation - something wrong with the driver, or the firmware may have missed some of the "lessons learned" in Alpine Ridge and caused this regression. That would also make it applicable to 9300, which has a "developer edition" option under Project Sputnik. I have attempted 5.8 Ubuntu generic, 5.6 OEM (-20.04) and 5.10 OEM (-20.04b and -20.04-edge) kernels on the 9500 with same results. I have attempted rebinding the XHCI controller after reconnecting the dock. I have attempted disabling USB autosuspend and ASPM via a GRUB kernel parameter. I have attempted playing with BIOS settings: wake on dell usb-c docks, disable early sign of life for both checkboxes, disabling SGX and SMM, checking all 3 boxes for Thunderbolt and switching off Thunderbolt security. None of these make a noticeable difference. System config: XPS 9500, i7, 32GB RAM BIOS 1.6.1, TB3 firmware NVM60 Ubuntu 20.04.02 LTS, kernels 5.6-oem, 5.8-generic, 5.10-oem (same behaviour) TB16 dock firmware 1.0.4 (MST 3.12.02) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: gboiko 1990 F pulseaudio /dev/snd/controlC2: gboiko 1990 F pulseaudio /dev/snd/controlC1: gboiko 1990 F pulseaudio /dev/snd/controlC0: gboiko 1990 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-31 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-meta-oem-5.6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1052-oem root=/dev/mapper/vgubuntu-root ro net.ifnames=0 biosdevname=0 ipv6.disable=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1052.56-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1052-oem N/A linux-backports-modules-5.6.0-1052-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.6.0-1052-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 0RHXRG dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd12/24/2020:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0RHXRG:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1922336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926023] [NEW] display broken on logout
You have been subscribed to a public bug: I can login and use the system, but when I logout, the monitor complains that it can't display the video mode. Pressing various keys and clicking randomly doesn't help, I have to press the hard reset button to login again. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:07: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 460.73.01 Thu Apr 1 21:40:36 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 24 18:13:51 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU106 [GeForce RTX 2060 SUPER] [1462:c752] InstallationDate: Installed on 2021-04-24 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=901be83b-8764-4544-acd9-b13439d1ab8f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: B450M Pro4-F dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/01/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4-F:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 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.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug hirsute nvidia ubuntu -- display broken on logout https://bugs.launchpad.net/bugs/1926023 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 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 1925739] 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 1925739 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/1925739 Title: [Dell Vostro 3668] Strange sound when speaker is muted Status in linux package in Ubuntu: Incomplete Bug description: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bapi 1453 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-22 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.2-1ubuntu2.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Tags: groovy Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.1 dmi.board.name: 0VFD52 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.1:bd09/30/2020:br1.14:svnDellInc.:pnVostro3668:pvr:rvnDellInc.:rn0VFD52:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3668 dmi.product.sku: 0760 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925739/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925739] Re: Strange sound when speaker is muted
If the problem was /sys/module/snd_hda_intel/parameters/power_save then this should be assigned to the kernel. ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) ** Summary changed: - Strange sound when speaker is muted + [Dell Vostro 3668] Strange sound when speaker is muted -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925739 Title: [Dell Vostro 3668] Strange sound when speaker is muted Status in linux package in Ubuntu: Incomplete Bug description: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bapi 1453 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-22 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.2-1ubuntu2.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Tags: groovy Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.1 dmi.board.name: 0VFD52 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.1:bd09/30/2020:br1.14:svnDellInc.:pnVostro3668:pvr:rvnDellInc.:rn0VFD52:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3668 dmi.product.sku: 0760 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925739/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925824] [NEW] [Avita NS14A2] Screen doesn't display on warm boot and turning on after Suspend (i915 0000:00:02.0: [drm] *ERROR* failed to enable link training)
You have been subscribed to a public bug: I have Avita NS14A2 laptop where i dual boot windows 10 and Ubuntu 20.04. In past few days might be after installing updates I am facing issue where my screen dont display at all when i first boot it and after multiple force shut down and then boot in it work, even on doing Suspend and then opening it, screen didnt not display for about 5-6 minutes, and then shows login screen. On checking logs software i got these line on those time stamp when display doesnt shows this is the line: (Hardware) i915 :00:02.0: [drm] *ERROR* failed to enable link training this line continues for about 30-40 times on average during time when screen doesnt display anything on turing on. So I think there is some issue with it. As I primarily use Ubuntu 20.04 so didnt check it with windows 10 but on doing cold boot it didnt even shows the boot menu where i can choose between Ubuntu 20.04 and Windows 10. But once screen starts displaying i dont see that error in logs software anymore and screen doesnt freezes or hangs. It only happen when i either open after suspend or do cold boot. Please consider this issue on urgent basis, as it takes a lot of time and efforts to make screen display something. :( And please let me know whether I should do fresh installation of ubuntu 20.04 again. Sorry for any grammatical mistakes. :) Thank you, Bipul Harsh bipulharsh...@gmail.com ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 20:36:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation UHD Graphics 620 [8086:5917] InstallationDate: Installed on 2020-11-22 (151 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: AVITA NS14A2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=011d61ba-ef72-40ed-9957-25830622d9c7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2019 dmi.bios.release: 0.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BSR5IPHK-14UF80-AVI-V22 dmi.board.asset.tag: Default string dmi.board.name: 6614UFWC80 dmi.board.vendor: AVITA dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: AVITA dmi.chassis.version: Default string dmi.ec.firmware.release: 0.22 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBSR5IPHK-14UF80-AVI-V22:bd04/19/2019:br0.22:efr0.22:svnAVITA:pnNS14A2:pvrDefaultstring:rvnAVITA:rn6614UFWC80:rvrDefaultstring:cvnAVITA:ct10:cvrDefaultstring: dmi.product.family: CN6614 dmi.product.name: NS14A2 dmi.product.sku: CN6614F56U1IN-MB dmi.product.version: Default string dmi.sys.vendor: AVITA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- [Avita NS14A2] Screen doesn't display on warm boot and turning on after Suspend (i915 :00:02.0: [drm] *ERROR* failed to enable link training) https://bugs.launchpad.net/bugs/1925824 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 1925739] [NEW] Strange sound when speaker is muted
You have been subscribed to a public bug: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bapi 1453 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-22 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.2-1ubuntu2.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Tags: groovy Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.1 dmi.board.name: 0VFD52 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.1:bd09/30/2020:br1.14:svnDellInc.:pnVostro3668:pvr:rvnDellInc.:rn0VFD52:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3668 dmi.product.sku: 0760 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Low Status: New ** Tags: apport-collected groovy -- Strange sound when speaker is muted https://bugs.launchpad.net/bugs/1925739 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 1873052] Re: X11 fractional scaling causes two cursors after login (usually with amdgpu)
** Summary changed: - Showing two cursors after login (usually with amdgpu) + X11 fractional scaling causes two cursors after login (usually with amdgpu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: X11 fractional scaling causes two cursors after login (usually with amdgpu) Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in mutter source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720438] Re: brightness control broken nvidia
Judging by the age of this bug and the number of people subscribed, this page seems to have become a forum and not a current relevant bug report. The release 17.10 this bug was about is no longer supported anyway. Anyone experiencing problems please open a new bug of your own by running: ubuntu-bug xorg ** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid ** Changed in: mutter (Ubuntu) Status: Incomplete => Invalid ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia Status in gnome-power: Confirmed Status in gnome-power-manager package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Bug description: Ubuntu 17.10 beta 2 Nvidia 310M, 340.x official driver installed with Additional Drivers program The brightness control built into the laptop (Dell Vostro 3300) isn't changing the brightness. Normally I can use Fn + Up/Down arrow keys to change the brightness. The brightness control works fine in Ubuntu 16.04 with the same driver series. I don't know if this is a GNOME 3.26 bug but it's likely as I'm having the exact same problem with Fedora 26 on this laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1720438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915704] Re: Specific pointing device disappear/disconnect when standby
I'm not familiar with "Lightdm & Cinnamon" but regardless you should probably open a new bug about that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915704 Title: Specific pointing device disappear/disconnect when standby Status in linux package in Ubuntu: Invalid Bug description: Ubuntu 20.10 groovy (x86-64) Cinnamon 4.6.7 Kernel 5.8.0-43-generic I installed Ubuntu while using a Microsft mise. This one works great with no problem. The buttons are old and used out, so I changed it with a Trust with RGB. The Trust mouse seems disconnected when going to standby (need keyboard, since mouse seems disconnected to show password prompt). The only way to get the mouse back to work, is to disconnect and reconnect it. What's narrow in this, is that I've tried again with the old pointing device (from Microsoft), and this one still is recognised in standby, and I'm able to click to open the password prompt. I've read this repport: https://bugs.launchpad.net/ubuntu/+bug/1573454 But it seems not totaly the same, since I've the problem with a pointer and not the other one. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Mon Feb 15 12:07:10 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.32.03, 5.8.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GK107 [GeForce GTX 650] [19da:1288] MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=1768f602-2494-474b-970a-2f71d61fca4b ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2020 dmi.bios.release: 14.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1403 dmi.board.asset.tag: Default string dmi.board.name: PRIME B460-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1403:bd07/21/2020:br14.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB460-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 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.9-2ubuntu1.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-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/1915704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
Though this problem also just appeared for me on ubuntu 20.10, when I tried to upgrade my working mainline kernel from 5.11.16 to 5.11.17. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926395] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494538/+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/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-02 (427 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO PAWGC_GD Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: PAWGC_GD dmi.product.sku: 123456789 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. These commits have now landed in 5.10-rc1. commit cf78408f937a67f59f5e90ee8e6cadeed7c128a8 Author: Xiao Ni Date: Thu Feb 4 15:50:43 2021 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://github.com/torvalds/linux/commit/cf78408f937a67f59f5e90ee8e6cadeed7c128a8 commit c2968285925adb97b9aa4ede94c1f1ab61ce0925 Author: Xiao Ni Date: Thu Feb 4 15:50:44 2021 +0800 Subject: md/raid10: extend r10bio devs to raid disks Link: https://github.com/torvalds/linux/commit/c2968285925adb97b9aa4ede94c1f1ab61ce0925 commit f2e7e269a7525317752d472bb48a549780e87d22 Author: Xiao Ni Date: Thu Feb 4 15:50:45 2021 +0800 Subject: md/raid10: pull the code that wait for blocked dev into one function Link: https://github.com/torvalds/linux/commit/f2e7e269a7525317752d472bb48a549780e87d22 commit d30588b2731fb01e1616cf16c3fe79a1443e29aa Author: Xiao Ni Date: Thu Feb 4 15:50:46 2021 +0800 Subject: md/raid10: improve raid10 discard request Link: https://github.com/torvalds/linux/commit/d30588b2731fb01e1616cf16c3fe79a1443e29aa commit 254c271da0712ea8914f187588e0f81f7678ee2f Author: Xiao Ni Date: Thu Feb 4 15:50:47 2021 +0800 Subject: md/raid10: improve discard request for far layout Link: https://github.com/torvalds/linux/commit/254c271da0712ea8914f187588e0f81f7678ee2f There is also an additional commit which is required, and was merged after "md/raid10: improve raid10 discard request" was merged. The following commits enable Radid10 to use large discards, instead of splitting into many bios, since the technical hurdles have now been removed. commit ca4a4e9a55beeb138bb06e3867f5e486da896d44 Author: Mike Snitzer Date: Fri Apr 30 14:38:37 2021 -0400 Subject: dm raid: remove unnecessary discard limits for raid0 and raid10 Link: https://github.com/torvalds/linux/commit/ca4a4e9a55beeb138bb06e3867f5e486da896d44 The commits more or less cherry pick to the 5.11, 5.8, 5.4 and 4.15 kernels, with the following minor backports: 1) submit_bio_noacct() needed to be renamed to generic_make_request() since it was recently changed in: commit ed00aabd5eb9fb44d6aff1173234a2e911b9fead Author: Christoph Hellwig Date: Wed Jul 1 10:59:44 2020 +0200 Subject: block: rename generic_make_request to submit_bio_noacct Link: https://github.com/torvalds/linux/commit/ed00aabd5eb9fb44d6aff1173234a2e911b9fead - 2) bio_split(), mempool_alloc(), bio_clone_fast() all needed their + 2) In the 4.15, 5.4 and 5.8 kernels, trace_block_bio_remap() needs to + have its request_queue argument put back in place. It was recently + removed in: + + commit 1c02fca620f7273b597591065d366e2cca948d8f + Author: Christoph Hellwig + Date: Thu D
[Kernel-packages] [Bug 1926395] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494540/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-02 (427 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO PAWGC_GD Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: PAWGC_GD dmi.product.sku: 123456789 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926395] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494539/+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/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-02 (427 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO PAWGC_GD Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: PAWGC_GD dmi.product.sku: 123456789 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926395] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494541/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-02 (427 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO PAWGC_GD Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: PAWGC_GD dmi.product.sku: 123456789 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926395] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494529/+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/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-02 (427 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO PAWGC_GD Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: PAWGC_GD dmi.product.sku: 123456789 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926395] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494535/+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/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-02 (427 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO PAWGC_GD Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: PAWGC_GD dmi.product.sku: 123456789 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926395] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494531/+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/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-02 (427 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO PAWGC_GD Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: PAWGC_GD dmi.product.sku: 123456789 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926395] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494537/+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/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-02 (427 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO PAWGC_GD Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: PAWGC_GD dmi.product.sku: 123456789 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926395] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494528/+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/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-02 (427 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO PAWGC_GD Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: PAWGC_GD dmi.product.sku: 123456789 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926395] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494525/+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/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-02 (427 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO PAWGC_GD Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: PAWGC_GD dmi.product.sku: 123456789 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926395] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494534/+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/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-02 (427 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO PAWGC_GD Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: PAWGC_GD dmi.product.sku: 123456789 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926395] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494536/+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/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-02 (427 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO PAWGC_GD Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: PAWGC_GD dmi.product.sku: 123456789 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926395] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494533/+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/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-02 (427 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO PAWGC_GD Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: PAWGC_GD dmi.product.sku: 123456789 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926395] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494526/+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/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-02 (427 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO PAWGC_GD Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: PAWGC_GD dmi.product.sku: 123456789 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926395] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494530/+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/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-02 (427 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO PAWGC_GD Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: PAWGC_GD dmi.product.sku: 123456789 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926395] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494532/+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/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-02 (427 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO PAWGC_GD Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: PAWGC_GD dmi.product.sku: 123456789 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926395] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494527/+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/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-02 (427 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO PAWGC_GD Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: PAWGC_GD dmi.product.sku: 123456789 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926395] Re: apagado inesperado
apport information ** Tags added: apport-collected ** Description changed: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.17 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: joy1439 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-03-02 (427 days ago) + InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) + Lsusb: + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 003 Device 002: ID 0458:0185 KYE Systems Corp. (Mouse Systems) Wireless Mouse + Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: LENOVO PAWGC_GD + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c603edbf-0151-4041-8a4a-fa02e43ad0f2 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-73-generic N/A + linux-backports-modules-5.4.0-73-generic N/A + linux-firmware1.187.12 + Tags: focal + Uname: Linux 5.4.0-73-generic x86_64 + UpgradeStatus: Upgraded to focal on 2021-04-27 (6 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/03/2012 + dmi.bios.vendor: LENOVO + dmi.bios.version: 41CN28WW(V2.04) + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: Inagua + dmi.board.vendor: LENOVO + dmi.board.version: Base Board Version + dmi.chassis.asset.tag: Chassis Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Chassis Manufacturer + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pnPAWGC_GD:pvrINVALID:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: + dmi.product.family: IDEAPAD + dmi.product.name: PAWGC_GD + dmi.product.sku: 123456789 + dmi.product.version: INVALID + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1926395/+attachment/5494524/+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/1926395 Title: apagado inesperado Status in linux package in Ubuntu: Incomplete Bug description: uso mi noterbook y de repente se apaga, al intentar prenderla tarda unos min. con la imagen negra despues un destello blanco y se repite 3 veces luego aparece la imagen violeta se queda unos minutos y hay recien aparece el usuario y demas al iniciar lo hace pero despues aparece la pantalla negra o se vuelve a apagar y si quiero ver un video se repite el proceso seguido ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 00:40:04 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-02 (422 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2021-04-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joy1439 F pulse
[Kernel-packages] [Bug 1925075] Re: Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode
** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925075 Title: Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: The Gigabyte R120-T33 platform provides both device-tree and ACPI hardware descriptions. By default, the Linux kernel will boot in device-tree mode. A user can override this and choose ACPI mode by passing acpi=force. This system boots fine in DTB mode, but fails when booted in ACPI mode with acpi=force. [7.936228] ACPI: Power Button [PWRB] [7.941359] ACPI GTDT: [Firmware Bug]: failed to get the Watchdog base address. [7.948807] Unable to handle kernel read from unreadable memory at virtual address 0028 [7.957843] Mem abort info: [7.960625] ESR = 0x9604 [7.963667] EC = 0x25: DABT (current EL), IL = 32 bits [7.968968] SET = 0, FnV = 0 [7.972010] EA = 0, S1PTW = 0 [7.975140] Data abort info: [7.978008] ISV = 0, ISS = 0x0004 [7.981832] CM = 0, WnR = 0 [7.984788] [0028] user address but active_mm is swapper [7.991131] Internal error: Oops: 9604 [#1] SMP [7.996000] Modules linked in: [7.999047] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.11.0-16-generic #17-Ubuntu [8.006606] Hardware name: GIGABYTE R120-T33/MT30-GS1, BIOS F02 08/06/2019 [8.013469] pstate: 40400085 (nZcv daIf +PAN -UAO -TCO BTYPE=--) [8.019465] pc : __ipi_send_mask+0x60/0x114 [8.023645] lr : smp_cross_call+0x3c/0xdc [8.027648] sp : 8000127a3c90 [8.030951] x29: 8000127a3c90 x28: 000a [8.036256] x27: 800011b60510 x26: 8000122e5108 [8.041560] x25: 0001 x24: [8.046864] x23: 8000122ee000 x22: 8000123f8448 [8.052168] x21: 800010fd9a28 x20: 800010fd9a28 [8.056864] Unable to handle kernel read from unreadable memory at virtual address 0028 [8.057472] x19: 000100157c60 x18: 0020 [8.067011] Mem abort info: [8.067013] ESR = 0x9604 [8.072308] [8.072310] x17: c2da3fd1 [8.075089] EC = 0x25: DABT (current EL), IL = 32 bits [8.078131] x16: 1b5980d2 [8.079609] SET = 0, FnV = 0 [8.082998] [8.082999] x15: [8.088295] EA = 0, S1PTW = 0 [8.091684] x14: [8.094725] Data abort info: [8.096203] [8.096204] x13: 003d0900 [8.099591] ISV = 0, ISS = 0x0004 [8.102719] x12: 3d09 [8.106108] CM = 0, WnR = 0 [8.108975] [8.108977] x11: [8.110453] [0028] user address but active_mm is swapper [8.113841] x10: 3d09 [8.138598] x9 : 800010028c80 x8 : 0001 [8.143902] x7 : x6 : 000ff61d7318 [8.149206] x5 : 800011620080 x4 : 800011620150 [8.154510] x3 : 800010fd99e8 x2 : [8.159815] x1 : 800010fd9a28 x0 : [8.165120] Call trace: [8.167556] __ipi_send_mask+0x60/0x114 [8.171383] smp_cross_call+0x3c/0xdc [8.175036] smp_send_reschedule+0x3c/0x50 [8.179123] resched_curr+0x5c/0xb0 [8.182603] check_preempt_curr+0x58/0x90 [8.186604] ttwu_do_wakeup+0x2c/0x1a0 [8.190343] ttwu_do_activate+0x7c/0x114 [8.194256] try_to_wake_up+0x2cc/0x5b0 [8.198082] wake_up_process+0x24/0x30 [8.201821] swake_up_one+0x48/0x9c [8.205300] rcu_gp_kthread_wake+0x68/0x8c [8.209388] rcu_accelerate_cbs_unlocked+0xb4/0xf0 [8.214168] rcu_core+0x208/0x230 [8.217473] rcu_core_si+0x1c/0x30 [8.220865] __do_softirq+0x128/0x3a4 [8.224517] irq_exit+0xc4/0xec [8.227649] __handle_domain_irq+0x8c/0xec [8.231737] gic_handle_irq+0x84/0xfc [8.235389] el1_irq+0xc0/0x180 [8.238520] klist_next+0xc0/0x180 [8.241913] bus_for_each_dev+0x68/0xe0 [8.245740] driver_attach+0x30/0x3c [8.249306] bus_add_driver+0x154/0x250 [8.253131] driver_register+0x84/0x140 [8.256958] __platform_driver_register+0x34/0x40 [8.261653] of_fixed_clk_driver_init+0x28/0x34 [8.266176] do_one_initcall+0x50/0x290 [8.
[Kernel-packages] [Bug 1925685] Re: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer
** Summary changed: - [SRU] Patch for flicker and glitching on certain hardware, intel framebuffer, + [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925685 Title: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.8 package in Ubuntu: Confirmed Status in linux source package in Bionic: Won't Fix Status in linux-hwe-5.8 source package in Bionic: Confirmed Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.8 source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux-hwe-5.8 source package in Groovy: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux-hwe-5.8 source package in Hirsute: Confirmed Status in linux source package in Impish: Confirmed Status in linux-hwe-5.8 source package in Impish: Confirmed Bug description: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. The patch that works best was created in collaboration with Kai-Heng Feng, is attached to this bug report, and can be found here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+attachment/5491421/+files /drm-intel-both.patch Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) * Notice screen glitching/flickering after wake-from-suspend. * Install kernel compiled with the attached patch. Boot from patched kernel. * Suspend laptop, resume. No glitches. [Where problems could occur] * Although this solves the problem for us and has been confirmed to work with the Intel developers that developed this patch, it could cause another display type to have problems. This is unlikely as it has been vetted by Intel and by the mainline Linux kernel developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905466] Re: drm/i915: Drop force_probe requirement for Rocket Lake
@Christian: if you are experiencing bugs with mainline kernel, perhaps this would be more appropriate: https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905466 Title: drm/i915: Drop force_probe requirement for Rocket Lake Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] drm/i915 currently requires using i915.force_probe= to load the driver on RKL, but we should drop the requirement from this kernel so that machines being tested don't need to work around it locally. [Test case] Enable in the kernel, boot it on RKL, see that graphics use the native driver. [What could go wrong] Only affects RKL, so it's possible that RKL hw that would fail to boot with the native driver would regress, compared to fallback driver. But we've had this enabled for oem-5.10 since the start, and there are no RKL related fixes not already found in 5.11, so it should be safe to enable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926999] [NEW] Hirsute update: v5.11.16 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.11.16 upstream stable release
from git://git.kernel.org/
AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct
AMD_SFH: Add sensor_mask module parameter
AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits
mtd: rawnand: mtk: Fix WAITRDY break condition and timeout
Input: nspire-keypad - enable interrupts only when opened
gpio: sysfs: Obey valid_mask
dmaengine: idxd: Fix clobbering of SWERR overflow bit on writeback
dmaengine: idxd: fix delta_rec and crc size field for completion record
dmaengine: idxd: fix opcap sysfs attribute output
dmaengine: idxd: fix wq size store permission state
dmaengine: dw: Make it dependent to HAS_IOMEM
dmaengine: Fix a double free in dma_async_device_register
dmaengine: plx_dma: add a missing put_device() on error path
dmaengine: idxd: clear MSIX permission entry on shutdown
dmaengine: idxd: fix wq cleanup of WQCFG registers
ACPI: x86: Call acpi_boot_table_init() after acpi_table_upgrade()
ARM: dts: Drop duplicate sha2md5_fck to fix clk_disable race
ARM: dts: Fix moving mmc devices with aliases for omap4 & 5
remoteproc: pru: Fix loading of GNU Binutils ELF
lockdep: Add a missing initialization hint to the "INFO: Trying to register
non-static key" message
arc: kernel: Return -EFAULT if copy_to_user() fails
iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_enqueue_hcmd()
xfrm: BEET mode doesn't support fragments for inner packets
ASoC: max98373: Changed amp shutdown register as volatile
ASoC: max98373: Added 30ms turn on/off time delay
net: axienet: allow setups without MDIO
gpu/xen: Fix a use after free in xen_drm_drv_init
bpf: Take module reference for trampoline in module
neighbour: Disregard DEAD dst in neigh_update
powerpc/signal32: Fix Oops on sigreturn with unmapped VDSO
ARM: keystone: fix integer overflow warning
ARM: omap1: fix building with clang IAS
drm/msm: Fix a5xx/a6xx timestamps
ASoC: fsl_esai: Fix TDM slot setup for I2S mode
scsi: scsi_transport_srp: Don't block target in SRP_PORT_LOST state
iwlwifi: add support for Qu with AX201 device
net: ieee802154: stop dump llsec keys for monitors
net: ieee802154: forbid monitor for add llsec key
net: ieee802154: forbid monitor for del llsec key
net: ieee802154: stop dump llsec devs for monitors
net: ieee802154: forbid monitor for add llsec dev
net: ieee802154: forbid monitor for del llsec dev
net: ieee802154: stop dump llsec devkeys for monitors
net: ieee802154: forbid monitor for add llsec devkey
net: ieee802154: forbid monitor for del llsec devkey
net: ieee802154: stop dump llsec seclevels for monitors
net: ieee802154: forbid monitor for add llsec seclevel
pcnet32: Use pci_resource_len to validate PCI resource
drm/amd/display: Add missing mask for DCN3
mac80211: clear sta->fast_rx when STA removed from 4-addr VLAN
virt_wifi: Return micros for BSS TSF values
lib: fix kconfig dependency on ARCH_WANT_FRAME_POINTERS
net/sctp: fix race condition in sctp_destroy_sock
Input: s6sy761 - fix coordinate read bit shift
Input: i8042 - fix Pegatron C15B ID entry
HID: wacom: set EV_KEY and EV_ABS only for non-HID_GENERIC type of devices
dm verity fec: fix misaligned RS roots IO
readdir: make sure to verify directory entry for legacy interfaces too
drm/i915: Don't zero out the Y plane's watermarks
arm64: fix inline asm in load_unaligned_zeropad()
arm64: mte: Ensure TIF_MTE_ASYNC_FAULT is set atomically
UBUNTU: [Config] updateconfigs for AS_HAS_LSE_ATOMICS
arm64: alternatives: Move length validation in alternative_{insn, endif}
vfio/pci: Add missing range check in vfio_pci_mmap
riscv: Fix spelling mistake "SPARSEMEM" to "SPARSMEM"
scsi: libsas: Reset num_scatter if libata marks qc as NODATA
drm/vmwgfx: Make sure we unpin no longer needed buffers
ixgbe: Fix NULL pointer dereference in ethtool loopback test
ixgbe: fix unbalanced device enable/disable in suspend/resume
netfilter: flowtable: fix NAT IPv6 offload mangling
netfilter: conntrack: do not print icmpv6 as unknown via /proc
ice: Fix potential infinite loop when using u8 loop counter
libnvdimm/region: Fix nvdimm_has_flush() to handle ND_REGION_ASYNC
netfilter: bridge: add pre_exit hooks for ebtable unregistration
netfilter: arp_tables: add pre_exit hook for table unregister
libbpf: Fix potential NULL pointer dereference
drm/i915/display/vlv_dsi: Do not skip panel_pwr_cycle_delay when disabling the
panel
net: macb: fix the restore of cmp registers
net/mlx5e: fix ingress_ifindex check in mlx5e_flower_parse_meta
netfilter: nft_limit: avoid possible divide e
[Kernel-packages] [Bug 1920246] Re: Focal update: v5.4.106 upstream stable release
** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1920246 Title: Focal update: v5.4.106 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: New Status in linux-gkeop-5.4 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-aws source package in Bionic: New Status in linux-gkeop-5.4 source package in Bionic: In Progress Status in linux source package in Focal: Fix Committed Status in linux-aws source package in Focal: In Progress Status in linux-gkeop-5.4 source package in Focal: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.106 upstream stable release from git://git.kernel.org/ uapi: nfnetlink_cthelper.h: fix userspace compilation error powerpc/pseries: Don't enforce MSI affinity with kdump ath9k: fix transmitting to stations in dynamic SMPS mode net: Fix gro aggregation for udp encaps with zero csum net: check if protocol extracted by virtio_net_hdr_set_proto is correct net: avoid infinite loop in mpls_gso_segment when mpls_hlen == 0 sh_eth: fix TRSCER mask for SH771x can: skb: can_skb_set_owner(): fix ref counting if socket was closed before setting skb ownership can: flexcan: assert FRZ bit in flexcan_chip_freeze() can: flexcan: enable RX FIFO after FRZ/HALT valid can: flexcan: invoke flexcan_chip_freeze() to enter freeze mode can: tcan4x5x: tcan4x5x_init(): fix initialization - clear MRAM before entering Normal Mode tcp: add sanity tests to TCP_QUEUE_SEQ netfilter: nf_nat: undo erroneous tcp edemux lookup netfilter: x_tables: gpf inside xt_find_revision() selftests/bpf: No need to drop the packet when there is no geneve opt selftests/bpf: Mask bpf_csum_diff() return value to 16 bits in test_verifier samples, bpf: Add missing munmap in xdpsock ibmvnic: always store valid MAC address mt76: dma: do not report truncated frames to mac80211 powerpc/603: Fix protection of user pages mapped with PROT_NONE mount: fix mounting of detached mounts onto targets that reside on shared mounts cifs: return proper error code in statfs(2) Revert "mm, slub: consider rest of partial list if acquire_slab() fails" net: enetc: don't overwrite the RSS indirection table when initializing net/mlx4_en: update moderation when config reset net: stmmac: fix incorrect DMA channel intr enable setting of EQoS v4.10 nexthop: Do not flush blackhole nexthops when loopback goes down net: sched: avoid duplicates in classes dump net: usb: qmi_wwan: allow qmimux add/del with master up netdevsim: init u64 stats for 32bit hardware cipso,calipso: resolve a number of problems with the DOI refcounts net: lapbether: Remove netif_start_queue / netif_stop_queue net: davicom: Fix regulator not turned off on failed probe net: davicom: Fix regulator not turned off on driver removal net: qrtr: fix error return code of qrtr_sendmsg() ixgbe: fail to create xfrm offload of IPsec tunnel mode SA net: stmmac: stop each tx channel independently net: stmmac: fix watchdog timeout during suspend/resume stress test selftests: forwarding: Fix race condition in mirror installation perf traceevent: Ensure read cmdlines are null terminated. net: hns3: fix query vlan mask value error for flow director net: hns3: fix bug when calculating the TCAM table info s390/cio: return -EFAULT if copy_to_user() fails again bnxt_en: reliably allocate IRQ table on reset to avoid crash drm/compat: Clear bounce structures drm/shmem-helper: Check for purged buffers in fault handler drm/shmem-helper: Don't remove the offset in vm_area_struct pgoff drm: meson_drv add shutdown function s390/cio: return -EFAULT if copy_to_user() fails s390/crypto: return -EFAULT if copy_to_user() fails qxl: Fix uninitialised struct field head.surface_id sh_eth: fix TRSCER mask for R7S9210 media: usbtv: Fix deadlock on suspend media: v4l: vsp1: Fix uif null pointer access media: v4l: vsp1: Fix bru null pointer access media: rc: compile rc-cec.c into rc-core UBUNTU: [Config] update abi for rc-cec net: hns3: fix error mask definition of flow director net: enetc: initialize RFS/RSS memories for unused ports too net: phy: fix save wrong speed and duplex prob
[Kernel-packages] [Bug 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
** Changed in: linux (Ubuntu Focal) Status: Fix Committed => 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/1856608 Title: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Confirmed Bug description: This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81. This bug was fixed by simply reverting the offending change. Bug 1859873 tracks root causing the issue and reapplying the change w/ any necessary fixes. [Impact] USB port unusable and boot time takes ~5 minutes longer to complete. Kernel emits messages like: usb usb2-port2: Cannot enable. Maybe the USB cable is bad? [Test Case] dmesg | grep "Cannot enable" [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925075] Re: Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode
** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925075 Title: Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode Status in linux package in Ubuntu: In Progress Bug description: The Gigabyte R120-T33 platform provides both device-tree and ACPI hardware descriptions. By default, the Linux kernel will boot in device-tree mode. A user can override this and choose ACPI mode by passing acpi=force. This system boots fine in DTB mode, but fails when booted in ACPI mode with acpi=force. [7.936228] ACPI: Power Button [PWRB] [7.941359] ACPI GTDT: [Firmware Bug]: failed to get the Watchdog base address. [7.948807] Unable to handle kernel read from unreadable memory at virtual address 0028 [7.957843] Mem abort info: [7.960625] ESR = 0x9604 [7.963667] EC = 0x25: DABT (current EL), IL = 32 bits [7.968968] SET = 0, FnV = 0 [7.972010] EA = 0, S1PTW = 0 [7.975140] Data abort info: [7.978008] ISV = 0, ISS = 0x0004 [7.981832] CM = 0, WnR = 0 [7.984788] [0028] user address but active_mm is swapper [7.991131] Internal error: Oops: 9604 [#1] SMP [7.996000] Modules linked in: [7.999047] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.11.0-16-generic #17-Ubuntu [8.006606] Hardware name: GIGABYTE R120-T33/MT30-GS1, BIOS F02 08/06/2019 [8.013469] pstate: 40400085 (nZcv daIf +PAN -UAO -TCO BTYPE=--) [8.019465] pc : __ipi_send_mask+0x60/0x114 [8.023645] lr : smp_cross_call+0x3c/0xdc [8.027648] sp : 8000127a3c90 [8.030951] x29: 8000127a3c90 x28: 000a [8.036256] x27: 800011b60510 x26: 8000122e5108 [8.041560] x25: 0001 x24: [8.046864] x23: 8000122ee000 x22: 8000123f8448 [8.052168] x21: 800010fd9a28 x20: 800010fd9a28 [8.056864] Unable to handle kernel read from unreadable memory at virtual address 0028 [8.057472] x19: 000100157c60 x18: 0020 [8.067011] Mem abort info: [8.067013] ESR = 0x9604 [8.072308] [8.072310] x17: c2da3fd1 [8.075089] EC = 0x25: DABT (current EL), IL = 32 bits [8.078131] x16: 1b5980d2 [8.079609] SET = 0, FnV = 0 [8.082998] [8.082999] x15: [8.088295] EA = 0, S1PTW = 0 [8.091684] x14: [8.094725] Data abort info: [8.096203] [8.096204] x13: 003d0900 [8.099591] ISV = 0, ISS = 0x0004 [8.102719] x12: 3d09 [8.106108] CM = 0, WnR = 0 [8.108975] [8.108977] x11: [8.110453] [0028] user address but active_mm is swapper [8.113841] x10: 3d09 [8.138598] x9 : 800010028c80 x8 : 0001 [8.143902] x7 : x6 : 000ff61d7318 [8.149206] x5 : 800011620080 x4 : 800011620150 [8.154510] x3 : 800010fd99e8 x2 : [8.159815] x1 : 800010fd9a28 x0 : [8.165120] Call trace: [8.167556] __ipi_send_mask+0x60/0x114 [8.171383] smp_cross_call+0x3c/0xdc [8.175036] smp_send_reschedule+0x3c/0x50 [8.179123] resched_curr+0x5c/0xb0 [8.182603] check_preempt_curr+0x58/0x90 [8.186604] ttwu_do_wakeup+0x2c/0x1a0 [8.190343] ttwu_do_activate+0x7c/0x114 [8.194256] try_to_wake_up+0x2cc/0x5b0 [8.198082] wake_up_process+0x24/0x30 [8.201821] swake_up_one+0x48/0x9c [8.205300] rcu_gp_kthread_wake+0x68/0x8c [8.209388] rcu_accelerate_cbs_unlocked+0xb4/0xf0 [8.214168] rcu_core+0x208/0x230 [8.217473] rcu_core_si+0x1c/0x30 [8.220865] __do_softirq+0x128/0x3a4 [8.224517] irq_exit+0xc4/0xec [8.227649] __handle_domain_irq+0x8c/0xec [8.231737] gic_handle_irq+0x84/0xfc [8.235389] el1_irq+0xc0/0x180 [8.238520] klist_next+0xc0/0x180 [8.241913] bus_for_each_dev+0x68/0xe0 [8.245740] driver_attach+0x30/0x3c [8.249306] bus_add_driver+0x154/0x250 [8.253131] driver_register+0x84/0x140 [8.256958] __platform_driver_register+0x34/0x40 [8.261653] of_fixed_clk_driver_init+0x28/0x34 [8.266176] do_one_initcall+0x50/0x290 [8.270001] do_initcalls+0x104/0x144 [8.273659] kernel_init_freeable+0x174/0x1c0 [8.278005] kernel_init+0x20/0x134 [8.281486] ret_from_fork+0x10/0x18 [8.285056] Code: a90363f7 aa0103f5 b0010db7 f9401260 (b9402800) [8.291168] ---[ end trace e85c5f6ac85cc1e3 ]--- [8.295774] Kernel panic - not syncing:
[Kernel-packages] [Bug 1926993] [NEW] Hirsute update: v5.11.15 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.11.15 upstream stable release from git://git.kernel.org/ interconnect: core: fix error return code of icc_link_destroy() gfs2: Flag a withdraw if init_threads() fails KVM: arm64: Hide system instruction access to Trace registers KVM: arm64: Disable guest access to trace filter controls drm/imx: imx-ldb: fix out of bounds array access warning gfs2: report "already frozen/thawed" errors ftrace: Check if pages were allocated before calling free_pages() tools/kvm_stat: Add restart delay drm/tegra: dc: Don't set PLL clock to 0Hz gpu: host1x: Use different lock classes for each client XArray: Fix splitting to non-zero orders radix tree test suite: Fix compilation block: only update parent bi_status when bio fail radix tree test suite: Register the main thread with the RCU library idr test suite: Take RCU read lock in idr_find_test_1 idr test suite: Create anchor before launching throbber null_blk: fix command timeout completion handling io_uring: don't mark S_ISBLK async work as unbounded riscv,entry: fix misaligned base for excp_vect_table block: don't ignore REQ_NOWAIT for direct IO netfilter: x_tables: fix compat match/target pad out-of-bound write perf map: Tighten snprintf() string precision to pass gcc check on some 32-bit arches net: sfp: cope with SFPs that set both LOS normal and LOS inverted Linux 5.11.15 UBUNTU: upstream stable to v5.11.15 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Hirsute) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.11.15 upstream stable release + from git://git.kernel.org/ -v5.11.15 upstream stable release -from git://git.kernel.org/ + interconnect: core: fix error return code of icc_link_destroy() + gfs2: Flag a withdraw if init_threads() fails + KVM: arm64: Hide system instruction access to Trace registers + KVM: arm64: Disable guest access to trace filter controls + drm/imx: imx-ldb: fix out of bounds array access warning + gfs2: report "already frozen/thawed" errors + ftrace: Check if pages were allocated before calling free_pages() + tools/kvm_stat: Add restart delay + drm/tegra: dc: Don't set PLL clock to 0Hz + gpu: host1x: Use different lock classes for each client + XArray: Fix splitting to non-zero orders + radix tree test suite: Fix compilation + block: only update parent bi_status when bio fail + radix tree test suite: Register the main thread with the RCU library + idr test suite: Take RCU read lock in idr_find_test_1 + idr test suite: Create anchor before launching throbber + null_blk: fix command timeout completion handling + io_uring: don't mark S_ISBLK async work as unbounded + riscv,entry: fix misaligned base for excp_vect_table + block: don't ignore REQ_NOWAIT for direct IO + netfilter: x_tables: fix compat match/target pad out-of-bound write + perf map: Tighten snprintf() string precision to
[Kernel-packages] [Bug 1474171] Re: Wily boot failure on HP proliant m400 server
** Changed in: linux (Ubuntu) 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/1474171 Title: Wily boot failure on HP proliant m400 server Status in linux package in Ubuntu: Fix Released Bug description: Looks kernel crashs inside mlx4_en_xmit() of mlx ethernet driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1474171/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
** Changed in: linux-base (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: New Status in linux-base package in Debian: New Bug description: [Impact] Systems that use flash-kernel may end up installing the wrong kernel image. `linux-version sort` can provide different answers depending on how it is called (see Test Case). The stdin behavior appears to be a bug, and this is the mode flash-kernel uses. So, for example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic-64k instead of the expected 5.8.0-50-generic if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an old HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server, and is long out of support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720438] Re: brightness control broken nvidia
I've found this forum thread: https://forums.developer.nvidia.com/t/solus-nvidia-gtx-1070-brightness- control-not-working/54472 If I understand correctly, the OP resolved his issue by setting the kernel boot parameter nvidia.NVreg_EnableBacklightHandler=1 This did not solve the issue for me, however. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia Status in gnome-power: Confirmed Status in gnome-power-manager package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 beta 2 Nvidia 310M, 340.x official driver installed with Additional Drivers program The brightness control built into the laptop (Dell Vostro 3300) isn't changing the brightness. Normally I can use Fn + Up/Down arrow keys to change the brightness. The brightness control works fine in Ubuntu 16.04 with the same driver series. I don't know if this is a GNOME 3.26 bug but it's likely as I'm having the exact same problem with Fedora 26 on this laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1720438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926955] Re: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x000000009BC11F38"
FTR, I just checked with Canonical IS and the affected host systems are running Xenial. (We also have some different hardware which is running the same versions too and doesn't suffer from this bug, so I do suspect it is somehow hw specific.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926955 Title: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 Steps to reproduce: 1. Boot a current impish daily cloud image (have not confirmed other releases) in a VM on an Ampere eMAG (have not verified bare metal). 2. Wait for it to come up, and then issue `sudo reboot` 3. If the machine comes back up again, repeat #2 a few times. This is intermittent. 3a. If it fails, take a look at "openstack console log " for the IRQ exception which repeats indefinitely. (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] [NEW] linux-version sort: argv and stdin behaviors differ
Public bug reported: [Impact] Systems that use flash-kernel may end up installing the wrong kernel image. `linux-version sort` can provide different answers depending on how it is called (see Test Case). The stdin behavior appears to be a bug, and this is the mode flash-kernel uses. So, for example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic-64k instead of the expected 5.8.0-50-generic if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an old HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server, and is long out of support. ** Affects: linux-base (Ubuntu) Importance: Undecided Status: New ** Affects: linux-base (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #987851 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987851 ** Also affects: linux-base (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987851 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: New Status in linux-base package in Debian: Unknown Bug description: [Impact] Systems that use flash-kernel may end up installing the wrong kernel image. `linux-version sort` can provide different answers depending on how it is called (see Test Case). The stdin behavior appears to be a bug, and this is the mode flash-kernel uses. So, for example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic-64k instead of the expected 5.8.0-50-generic if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an old HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server, and is long out of support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926184] Re: locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
This bug was fixed in the package linux-aws - 5.4.0-1047.49
---
linux-aws (5.4.0-1047.49) focal; urgency=medium
* focal/linux-aws: 5.4.0-1047.49 -proposed tracker (LP: #1926522)
* locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184)
- locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
-- Kelsey Skunberg Wed, 28 Apr 2021
16:08:07 -0600
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1926184
Title:
locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
Status in linux package in Ubuntu:
In Progress
Status in linux-aws package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Confirmed
Status in linux-aws source package in Bionic:
Fix Released
Status in linux source package in Focal:
Confirmed
Status in linux-aws source package in Focal:
Fix Released
Status in linux source package in Groovy:
Confirmed
Status in linux-aws source package in Groovy:
Confirmed
Status in linux source package in Hirsute:
Confirmed
Status in linux-aws source package in Hirsute:
Confirmed
Bug description:
[Impact]
* Out of order reads can fetch a NULL pointer causing a kernel crash. Affects
kernels from v4.15 to v5.11.
[Fix]
* commit 84a24bf8c52e ("locking/qrwlock: Fix ordering in
queued_write_lock_slowpath()")
* For Bionic, we also require an additional patch: commit fcfdfe30e324
("locking/barriers: Introduce smp_cond_load_relaxed() and
atomic_cond_read_relaxed()")
[Where problems could occur]
* This is quite a subtle bug. It is more prevalent on arm64. Regression
possibility seems quite low. The worst impact could be a minor performance
degradation.
* Kernels 4.15 / 5.4 / 5.8 / 5.11 were successfully built and booted
with this patch. Also, by using ftrace we could see that the changed
function was executed with success multiple times.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926184/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926184] Re: locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
This bug was fixed in the package linux-aws - 4.15.0-1101.108
---
linux-aws (4.15.0-1101.108) bionic; urgency=medium
* bionic/linux-aws: 4.15.0-1101.108 -proposed tracker (LP: #1926302)
* locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184)
- locking/barriers: Introduce smp_cond_load_relaxed() and
atomic_cond_read_relaxed()
- locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
-- Tim Gardner Tue, 27 Apr 2021 09:12:22
-0600
** Changed in: linux-aws (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: linux-aws (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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1926184
Title:
locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
Status in linux package in Ubuntu:
In Progress
Status in linux-aws package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Confirmed
Status in linux-aws source package in Bionic:
Fix Released
Status in linux source package in Focal:
Confirmed
Status in linux-aws source package in Focal:
Fix Released
Status in linux source package in Groovy:
Confirmed
Status in linux-aws source package in Groovy:
Confirmed
Status in linux source package in Hirsute:
Confirmed
Status in linux-aws source package in Hirsute:
Confirmed
Bug description:
[Impact]
* Out of order reads can fetch a NULL pointer causing a kernel crash. Affects
kernels from v4.15 to v5.11.
[Fix]
* commit 84a24bf8c52e ("locking/qrwlock: Fix ordering in
queued_write_lock_slowpath()")
* For Bionic, we also require an additional patch: commit fcfdfe30e324
("locking/barriers: Introduce smp_cond_load_relaxed() and
atomic_cond_read_relaxed()")
[Where problems could occur]
* This is quite a subtle bug. It is more prevalent on arm64. Regression
possibility seems quite low. The worst impact could be a minor performance
degradation.
* Kernels 4.15 / 5.4 / 5.8 / 5.11 were successfully built and booted
with this patch. Also, by using ftrace we could see that the changed
function was executed with success multiple times.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926184/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926955] Re: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x000000009BC11F38"
** Summary changed: - arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" + [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x9BC11F38" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926955 Title: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 Steps to reproduce: 1. Boot a current impish daily cloud image (have not confirmed other releases) in a VM on an Ampere eMAG (have not verified bare metal). 2. Wait for it to come up, and then issue `sudo reboot` 3. If the machine comes back up again, repeat #2 a few times. This is intermittent. 3a. If it fails, take a look at "openstack console log " for the IRQ exception which repeats indefinitely. (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926974] Re: The graphics drivers ppa dropped the 32bit compat libs needed by steam
I couldn't execute `apport-collect 1926974` command. I'll try to contact `https://launchpad.net/~graphics-drivers` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926974 Title: The graphics drivers ppa dropped the 32bit compat libs needed by steam Status in linux package in Ubuntu: Incomplete Bug description: Steam doesn't start after installing nvidia-driver-465. It works with nvidia-driver-460, however. ``` Running Steam on linuxmint 20.1 64-bit STEAM_RUNTIME is enabled automatically Pins up-to-date! Steam client's requirements are satisfied WARNING: Using default/fallback debugger launch /home/cuysaurus/.steam/debian-installation/ubuntu12_32/steam -nominidumps -nobreakpad [2021-05-02 20:23:00] Startup - updater built Apr 12 2021 18:51:36 SteamUpdateUI: An X Error occurred X Error of failed request: GLXBadContext SteamUpdateUI: An X Error occurred X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 151 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 45 xerror_handler: X failed, continuing Major opcode of failed request: 151 (GLX) Minor opcode of failed request: 6 (X_GLXIsDirect) Serial number of failed request: 46 xerror_handler: X failed, continuing [2021-05-02 20:23:03] Using the following download hosts for Public, Realm steamglobal [2021-05-02 20:23:03] 1. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf' [2021-05-02 20:23:03] 2. https://cdn.akamai.steamstatic.com, /client/, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf' [2021-05-02 20:23:03] 3. http://media.steampowered.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in' [2021-05-02 20:23:03] Verifying installation... [2021-05-02 20:23:04] Verification complete ``` results from `apt policy libnvidia-gl-465 libnvidia-gl-465:i386`: ``` libnvidia-gl-465: Installed: 465.24.02-0ubuntu0~0.20.04.1 Candidate: 465.24.02-0ubuntu0~0.20.04.1 Version table: *** 465.24.02-0ubuntu0~0.20.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status libnvidia-gl-465:i386: Installed: (none) Candidate: (none) Version table: ``` results from `sudo apt install libnvidia-gl-465:i386`: ``` Reading package lists... Done Building dependency tree Reading state information... Done Package libnvidia-gl-465:i386 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: libnvidia-common-465 E: Package 'libnvidia-gl-465:i386' has no installation candidate ``` I would like to add that I tested a game outside steam and it works normally. I'm using Linux Mint 20.1 x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
> Should mainline kernels work on the previous LTS or not? I think the main issue is with focal, the *current* LTS, which can't use mainline kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926974] Re: The graphics drivers ppa dropped the 32bit compat libs needed by steam
If this is about a PPA; the page to report this is on the "Contact this team's admins" link on the PPA page (which sends an email to the team that works on the personal package archive). You've filed a bug report on Ubuntu itself, which should be done with `ubuntu-bug` on the system impacted. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926974 Title: The graphics drivers ppa dropped the 32bit compat libs needed by steam Status in linux package in Ubuntu: Incomplete Bug description: Steam doesn't start after installing nvidia-driver-465. It works with nvidia-driver-460, however. ``` Running Steam on linuxmint 20.1 64-bit STEAM_RUNTIME is enabled automatically Pins up-to-date! Steam client's requirements are satisfied WARNING: Using default/fallback debugger launch /home/cuysaurus/.steam/debian-installation/ubuntu12_32/steam -nominidumps -nobreakpad [2021-05-02 20:23:00] Startup - updater built Apr 12 2021 18:51:36 SteamUpdateUI: An X Error occurred X Error of failed request: GLXBadContext SteamUpdateUI: An X Error occurred X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 151 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 45 xerror_handler: X failed, continuing Major opcode of failed request: 151 (GLX) Minor opcode of failed request: 6 (X_GLXIsDirect) Serial number of failed request: 46 xerror_handler: X failed, continuing [2021-05-02 20:23:03] Using the following download hosts for Public, Realm steamglobal [2021-05-02 20:23:03] 1. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf' [2021-05-02 20:23:03] 2. https://cdn.akamai.steamstatic.com, /client/, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf' [2021-05-02 20:23:03] 3. http://media.steampowered.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in' [2021-05-02 20:23:03] Verifying installation... [2021-05-02 20:23:04] Verification complete ``` results from `apt policy libnvidia-gl-465 libnvidia-gl-465:i386`: ``` libnvidia-gl-465: Installed: 465.24.02-0ubuntu0~0.20.04.1 Candidate: 465.24.02-0ubuntu0~0.20.04.1 Version table: *** 465.24.02-0ubuntu0~0.20.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status libnvidia-gl-465:i386: Installed: (none) Candidate: (none) Version table: ``` results from `sudo apt install libnvidia-gl-465:i386`: ``` Reading package lists... Done Building dependency tree Reading state information... Done Package libnvidia-gl-465:i386 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: libnvidia-common-465 E: Package 'libnvidia-gl-465:i386' has no installation candidate ``` I would like to add that I tested a game outside steam and it works normally. I'm using Linux Mint 20.1 x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926974] Re: The graphics drivers ppa dropped the 32bit compat libs needed by steam
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1926974 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Please note: `ubuntu-bug`, `apport` & bug reporting tools are provided with Ubuntu by default, many require manual addition for some releases of downstream OSes based on Ubuntu (eg. Linux Mint). You should check with your distribution first. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926974 Title: The graphics drivers ppa dropped the 32bit compat libs needed by steam Status in linux package in Ubuntu: Incomplete Bug description: Steam doesn't start after installing nvidia-driver-465. It works with nvidia-driver-460, however. ``` Running Steam on linuxmint 20.1 64-bit STEAM_RUNTIME is enabled automatically Pins up-to-date! Steam client's requirements are satisfied WARNING: Using default/fallback debugger launch /home/cuysaurus/.steam/debian-installation/ubuntu12_32/steam -nominidumps -nobreakpad [2021-05-02 20:23:00] Startup - updater built Apr 12 2021 18:51:36 SteamUpdateUI: An X Error occurred X Error of failed request: GLXBadContext SteamUpdateUI: An X Error occurred X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 151 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 45 xerror_handler: X failed, continuing Major opcode of failed request: 151 (GLX) Minor opcode of failed request: 6 (X_GLXIsDirect) Serial number of failed request: 46 xerror_handler: X failed, continuing [2021-05-02 20:23:03] Using the following download hosts for Public, Realm steamglobal [2021-05-02 20:23:03] 1. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf' [2021-05-02 20:23:03] 2. https://cdn.akamai.steamstatic.com, /client/, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf' [2021-05-02 20:23:03] 3. http://media.steampowered.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in' [2021-05-02 20:23:03] Verifying installation... [2021-05-02 20:23:04] Verification complete ``` results from `apt policy libnvidia-gl-465 libnvidia-gl-465:i386`: ``` libnvidia-gl-465: Installed: 465.24.02-0ubuntu0~0.20.04.1 Candidate: 465.24.02-0ubuntu0~0.20.04.1 Version table: *** 465.24.02-0ubuntu0~0.20.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status libnvidia-gl-465:i386: Installed: (none) Candidate: (none) Version table: ``` results from `sudo apt install libnvidia-gl-465:i386`: ``` Reading package lists... Done Building dependency tree Reading state information... Done Package libnvidia-gl-465:i386 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: libnvidia-common-465 E: Package 'libnvidia-gl-465:i386' has no installation candidate ``` I would like to add that I tested a game outside steam and it works normally. I'm using Linux Mint 20.1 x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926974] Re: The graphics drivers ppa dropped the 32bit compat libs needed by steam
Ubuntu ** Package changed: ubuntu => steam (Ubuntu) ** Changed in: steam (Ubuntu) Status: New => Incomplete ** Package changed: steam (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926974 Title: The graphics drivers ppa dropped the 32bit compat libs needed by steam Status in linux package in Ubuntu: Incomplete Bug description: Steam doesn't start after installing nvidia-driver-465. It works with nvidia-driver-460, however. ``` Running Steam on linuxmint 20.1 64-bit STEAM_RUNTIME is enabled automatically Pins up-to-date! Steam client's requirements are satisfied WARNING: Using default/fallback debugger launch /home/cuysaurus/.steam/debian-installation/ubuntu12_32/steam -nominidumps -nobreakpad [2021-05-02 20:23:00] Startup - updater built Apr 12 2021 18:51:36 SteamUpdateUI: An X Error occurred X Error of failed request: GLXBadContext SteamUpdateUI: An X Error occurred X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 151 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 45 xerror_handler: X failed, continuing Major opcode of failed request: 151 (GLX) Minor opcode of failed request: 6 (X_GLXIsDirect) Serial number of failed request: 46 xerror_handler: X failed, continuing [2021-05-02 20:23:03] Using the following download hosts for Public, Realm steamglobal [2021-05-02 20:23:03] 1. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf' [2021-05-02 20:23:03] 2. https://cdn.akamai.steamstatic.com, /client/, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf' [2021-05-02 20:23:03] 3. http://media.steampowered.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in' [2021-05-02 20:23:03] Verifying installation... [2021-05-02 20:23:04] Verification complete ``` results from `apt policy libnvidia-gl-465 libnvidia-gl-465:i386`: ``` libnvidia-gl-465: Installed: 465.24.02-0ubuntu0~0.20.04.1 Candidate: 465.24.02-0ubuntu0~0.20.04.1 Version table: *** 465.24.02-0ubuntu0~0.20.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status libnvidia-gl-465:i386: Installed: (none) Candidate: (none) Version table: ``` results from `sudo apt install libnvidia-gl-465:i386`: ``` Reading package lists... Done Building dependency tree Reading state information... Done Package libnvidia-gl-465:i386 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: libnvidia-common-465 E: Package 'libnvidia-gl-465:i386' has no installation candidate ``` I would like to add that I tested a game outside steam and it works normally. I'm using Linux Mint 20.1 x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926974] [NEW] The graphics drivers ppa dropped the 32bit compat libs needed by steam
You have been subscribed to a public bug: Steam doesn't start after installing nvidia-driver-465. It works with nvidia-driver-460, however. ``` Running Steam on linuxmint 20.1 64-bit STEAM_RUNTIME is enabled automatically Pins up-to-date! Steam client's requirements are satisfied WARNING: Using default/fallback debugger launch /home/cuysaurus/.steam/debian-installation/ubuntu12_32/steam -nominidumps -nobreakpad [2021-05-02 20:23:00] Startup - updater built Apr 12 2021 18:51:36 SteamUpdateUI: An X Error occurred X Error of failed request: GLXBadContext SteamUpdateUI: An X Error occurred X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 151 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 45 xerror_handler: X failed, continuing Major opcode of failed request: 151 (GLX) Minor opcode of failed request: 6 (X_GLXIsDirect) Serial number of failed request: 46 xerror_handler: X failed, continuing [2021-05-02 20:23:03] Using the following download hosts for Public, Realm steamglobal [2021-05-02 20:23:03] 1. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf' [2021-05-02 20:23:03] 2. https://cdn.akamai.steamstatic.com, /client/, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf' [2021-05-02 20:23:03] 3. http://media.steampowered.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in' [2021-05-02 20:23:03] Verifying installation... [2021-05-02 20:23:04] Verification complete ``` results from `apt policy libnvidia-gl-465 libnvidia-gl-465:i386`: ``` libnvidia-gl-465: Installed: 465.24.02-0ubuntu0~0.20.04.1 Candidate: 465.24.02-0ubuntu0~0.20.04.1 Version table: *** 465.24.02-0ubuntu0~0.20.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status libnvidia-gl-465:i386: Installed: (none) Candidate: (none) Version table: ``` results from `sudo apt install libnvidia-gl-465:i386`: ``` Reading package lists... Done Building dependency tree Reading state information... Done Package libnvidia-gl-465:i386 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: libnvidia-common-465 E: Package 'libnvidia-gl-465:i386' has no installation candidate ``` I would like to add that I tested a game outside steam and it works normally. I'm using Linux Mint 20.1 x86_64 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- The graphics drivers ppa dropped the 32bit compat libs needed by steam https://bugs.launchpad.net/bugs/1926974 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 1926955] Re: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x000000009BC11F38"
I couldn't find anywhere in the kernel that might be printing this message so I went searching, looks like it is probably coming from the firmware: https://github.com/tianocore/edk2/blob/master/ArmPlatformPkg/PrePeiCore/AArch64/ArchPrePeiCore.c#L29 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926955 Title: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 Steps to reproduce: 1. Boot a current impish daily cloud image (have not confirmed other releases) in a VM on an Ampere eMAG (have not verified bare metal). 2. Wait for it to come up, and then issue `sudo reboot` 3. If the machine comes back up again, repeat #2 a few times. This is intermittent. 3a. If it fails, take a look at "openstack console log " for the IRQ exception which repeats indefinitely. (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923670] Re: CIFS DFS entries not accessible with 5.4.0-71.74-generic
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Bionic) 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/1923670 Title: CIFS DFS entries not accessible with 5.4.0-71.74-generic Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Bug description: When booting 5.4.0-71-generic I can not access DFS entries anymore, with 5.4.0-70-generic this still works. Some details: fstab entry: //example.com/public /home/user/remotecifs noauto,vers=default,noserverino,users,_netdev,user=remote_user,domain=example.com 00 shell session ~$ mount /home/user/remote Password for remote_user@//example.com/public: ~$ ls /home/user/remote/dfs-folder dfs-subfolder dfs-entry ~$ ls /home/user/remote/dfs-folder/dfs-entry ls: cannot access '/home/user/remote/dfs-folder/dfs-entry': No such file or directory dmesg excerpt [ 1219.568778] CIFS: Attempting to mount //DC01.example.com/Public/dfs-folder/dfs-entry [ 1219.584975] FS-Cache: Duplicate cookie detected [ 1219.584986] FS-Cache: O-cookie c=6e995395 [p=f4725c61 fl=222 nc=0 na=1] [ 1219.584990] FS-Cache: O-cookie d=a11c1428 n=71ab21ba [ 1219.584993] FS-Cache: O-key=[6] '5075626c6963' [ 1219.585001] FS-Cache: N-cookie c=a0608786 [p=f4725c61 fl=2 nc=0 na=1] [ 1219.585004] FS-Cache: N-cookie d=a11c1428 n=901f6a53 [ 1219.585007] FS-Cache: N-key=[6] '5075626c6963' [ 1219.725834] FS-Cache: Duplicate cookie detected [ 1219.725847] FS-Cache: O-cookie c=6e995395 [p=f4725c61 fl=222 nc=0 na=1] [ 1219.725851] FS-Cache: O-cookie d=a11c1428 n=71ab21ba [ 1219.725854] FS-Cache: O-key=[6] '5075626c6963' [ 1219.725864] FS-Cache: N-cookie c=0509709f [p=f4725c61 fl=2 nc=0 na=1] [ 1219.725868] FS-Cache: N-cookie d=a11c1428 n=556f158b [ 1219.725870] FS-Cache: N-key=[6] '5075626c6963' [ 1220.216524] CIFS VFS: cifs_read_super: get root inode failed The dmesg from 5.4.0-70-generic does not have the line CIFS VFS: cifs_read_super: get root inode failed ~$ lsb_release -rd Description:KDE neon User Edition 5.21 Release: ~$ lsb_release -rd Description:KDE neon User Edition 5.21 Release:20.04 20.04 ~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.71.74 Candidate: 5.4.0.71.74 Version table: *** 5.4.0.71.74 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.26.32 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dirk 2946 F pulseaudio /dev/snd/controlC1: dirk 2946 F pulseaudio /dev/snd/controlC0: dirk 2946 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: KDE neon 20.04 InstallationDate: Installed on 2017-07-27 (1356 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20170614-00:52 MachineType: LENOVO 20HMS00T00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic root=/dev/mapper/vg00-lv_root ro intel_iommu=off ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-71-generic N/A linux-backports-modules-5.4.0-71-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.4.0-71-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: Upgraded to focal on 2020-11-22 (142 days ago) UserGroups: adm cdrom davfs2 dialout dip kvm libvirt lpadmin plugdev roccat sambashare scanner sudo vboxusers _MarkForUpload: False dmi.bios.date: 04/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET61W (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS00T00 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:bvrR0IET61W(1.39):bd04/20/2020:svnLENOVO:pn20HMS00T00:pvrThinkPadX270:rvnLENOVO:rn20HMS00T00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.prod
[Kernel-packages] [Bug 1926517] Re: [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES
** Description changed: [Impact] Whenever the driver is adding a vSES to virtual-phys list it is reinitializing the list head. Hence those vSES devices which were added previously are lost. [FIXES] Stop reinitializing the list every time a new vSES device is added. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=4c51f9569651 CommitID: 4c51f956965120b3441cdd39c358b87daba13e19 [TESTING] + Load the mpt3sas driver on the system where Brodcom's HBA 9500 Tri-Mode Storage Adapter (IT HBA Aero/Ventura) is connected to two backplanes (so that two vSES device get configured on the HBA). After loading the driver user should able to access both the vSES devices. Also even after performing host reset operation user must able to access both the vSES devices. + i.e. lsscsi must list both the vSES devices after loading the driver and also after performing host reset operation. [REGRESSION RISK] + + There is no regression risk with this bug fix 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/1926517 Title: [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: New Bug description: [Impact] Whenever the driver is adding a vSES to virtual-phys list it is reinitializing the list head. Hence those vSES devices which were added previously are lost. [FIXES] Stop reinitializing the list every time a new vSES device is added. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=4c51f9569651 CommitID: 4c51f956965120b3441cdd39c358b87daba13e19 [TESTING] Load the mpt3sas driver on the system where Brodcom's HBA 9500 Tri-Mode Storage Adapter (IT HBA Aero/Ventura) is connected to two backplanes (so that two vSES device get configured on the HBA). After loading the driver user should able to access both the vSES devices. Also even after performing host reset operation user must able to access both the vSES devices. i.e. lsscsi must list both the vSES devices after loading the driver and also after performing host reset operation. [REGRESSION RISK] There is no regression risk with this bug fix patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926955] Re: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x000000009BC11F38"
I captured the console log when the bug happens, was hoping there would be something interesting just before the exception starts spamming the console, but sadly not. [ OK ] Finished Reboot. [ OK ] Reached target Reboot. [ 17.856242] reboot: Restarting system IRQ Exception at 0xBBC11F38 IRQ Exception at 0xBBC11F38 IRQ Exception at 0xBBC11F38 IRQ Exception at 0xBBC11F38 (keeps spamming this message) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926955 Title: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 Steps to reproduce: 1. Boot a current impish daily cloud image (have not confirmed other releases) in a VM on an Ampere eMAG (have not verified bare metal). 2. Wait for it to come up, and then issue `sudo reboot` 3. If the machine comes back up again, repeat #2 a few times. This is intermittent. 3a. If it fails, take a look at "openstack console log " for the IRQ exception which repeats indefinitely. (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926960] Re: [Ubuntu 21.04] - OpenSSL 1.1.1g function EC_KEY_set_group() causes illegal instruction SIGILL in file crypto/ec/ec_key:477 (openssl-ibmca)
** Package changed: linux (Ubuntu) => openssl-ibmca (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/1926960 Title: [Ubuntu 21.04] - OpenSSL 1.1.1g function EC_KEY_set_group() causes illegal instruction SIGILL in file crypto/ec/ec_key:477 (openssl- ibmca) Status in openssl-ibmca package in Ubuntu: New Bug description: Problem Description: Loading and initializing the OpenSSL configuration twice causes ibmca to prematurely destroy global data. This then causes crashes in applications that do this. It might happen if an application first initializes OpenSSls libcrypto and then libssl. Solution: Please backport https://github.com/juergenchrist/openssl-ibmca/commit/40928425d848827fa8427d677e37178ab3b57e50 to fix this problem. focal (20.04LTS) (libs): 2.1.0-0ubuntu1 [ports]: s390x groovy (20.10) (libs): 2.1.1-0ubuntu1 [ports]: s390x hirsute (21.04) (libs): 2.1.1-0ubuntu1 [ports]: s390x git commit applies here cleanly. impish (libs): 2.1.2-0ubuntu1 [ports]: s390x git commit should already be contained in this. So no need for another patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl-ibmca/+bug/1926960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926960] [NEW] [Ubuntu 21.04] - OpenSSL 1.1.1g function EC_KEY_set_group() causes illegal instruction SIGILL in file crypto/ec/ec_key:477 (openssl-ibmca)
Public bug reported: Problem Description: Loading and initializing the OpenSSL configuration twice causes ibmca to prematurely destroy global data. This then causes crashes in applications that do this. It might happen if an application first initializes OpenSSls libcrypto and then libssl. Solution: Please backport https://github.com/juergenchrist/openssl-ibmca/commit/40928425d848827fa8427d677e37178ab3b57e50 to fix this problem. focal (20.04LTS) (libs): 2.1.0-0ubuntu1 [ports]: s390x groovy (20.10) (libs): 2.1.1-0ubuntu1 [ports]: s390x hirsute (21.04) (libs): 2.1.1-0ubuntu1 [ports]: s390x git commit applies here cleanly. impish (libs): 2.1.2-0ubuntu1 [ports]: s390x git commit should already be contained in this. So no need for another patch. ** Affects: openssl-ibmca (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-192575 severity-critical targetmilestone-inin2104 ** Tags added: architecture-s39064 bugnameltc-192575 severity-critical targetmilestone-inin2104 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926960 Title: [Ubuntu 21.04] - OpenSSL 1.1.1g function EC_KEY_set_group() causes illegal instruction SIGILL in file crypto/ec/ec_key:477 (openssl- ibmca) Status in openssl-ibmca package in Ubuntu: New Bug description: Problem Description: Loading and initializing the OpenSSL configuration twice causes ibmca to prematurely destroy global data. This then causes crashes in applications that do this. It might happen if an application first initializes OpenSSls libcrypto and then libssl. Solution: Please backport https://github.com/juergenchrist/openssl-ibmca/commit/40928425d848827fa8427d677e37178ab3b57e50 to fix this problem. focal (20.04LTS) (libs): 2.1.0-0ubuntu1 [ports]: s390x groovy (20.10) (libs): 2.1.1-0ubuntu1 [ports]: s390x hirsute (21.04) (libs): 2.1.1-0ubuntu1 [ports]: s390x git commit applies here cleanly. impish (libs): 2.1.2-0ubuntu1 [ports]: s390x git commit should already be contained in this. So no need for another patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl-ibmca/+bug/1926960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926960] [NEW] [Ubuntu 21.04] - OpenSSL 1.1.1g function EC_KEY_set_group() causes illegal instruction SIGILL in file crypto/ec/ec_key:477 (openssl-ibmca)
You have been subscribed to a public bug: Problem Description: Loading and initializing the OpenSSL configuration twice causes ibmca to prematurely destroy global data. This then causes crashes in applications that do this. It might happen if an application first initializes OpenSSls libcrypto and then libssl. Solution: Please backport https://github.com/juergenchrist/openssl-ibmca/commit/40928425d848827fa8427d677e37178ab3b57e50 to fix this problem. focal (20.04LTS) (libs): 2.1.0-0ubuntu1 [ports]: s390x groovy (20.10) (libs): 2.1.1-0ubuntu1 [ports]: s390x hirsute (21.04) (libs): 2.1.1-0ubuntu1 [ports]: s390x git commit applies here cleanly. impish (libs): 2.1.2-0ubuntu1 [ports]: s390x git commit should already be contained in this. So no need for another patch. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-192575 severity-critical targetmilestone-inin2104 -- [Ubuntu 21.04] - OpenSSL 1.1.1g function EC_KEY_set_group() causes illegal instruction SIGILL in file crypto/ec/ec_key:477 (openssl-ibmca) https://bugs.launchpad.net/bugs/1926960 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 1926955] Re: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x000000009BC11F38"
** Description changed: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: - IRQ Exception at 0x9BC11F38 + IRQ Exception at 0x9BC11F38 + + Steps to reproduce: + + 1. Boot a current impish daily cloud image (have not confirmed other releases) in a VM on an Ampere eMAG (have not verified bare metal). + 2. Wait for it to come up, and then issue `sudo reboot` + 3. If the machine comes back up again, repeat #2 a few times. This is intermittent. + 3a. If it fails, take a look at "openstack console log " for the IRQ exception which repeats indefinitely. (stand by, I will get something to attach shortly) - --- + --- ProblemType: Bug AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 May 3 12:45 seq - crw-rw 1 root audio 116, 33 May 3 12:45 timer + total 0 + crw-rw 1 root audio 116, 1 May 3 12:45 seq + crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: unknown DistroRelease: Ubuntu 21.10 Ec2AMI: ami-fd9f Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: - -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge - \-01.0-[01-02]01.0-[02]-- + -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge + \-01.0-[01-02]01.0-[02]-- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: - + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU KVM Virtual Machine Package: linux (not installed) PciMultimedia: - + ProcFB: - + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: - linux-restricted-modules-5.11.0-16-generic N/A - linux-backports-modules-5.11.0-16-generic N/A - linux-firmware 1.197 + linux-restricted-modules-5.11.0-16-generic N/A + linux-backports-modules-5.11.0-16-generic N/A + linux-firmware 1.197 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: impish ec2-images Uname: Linux 5.11.0-16-generic aarch64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: - + dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0: dmi.product.name: KVM Virtual Machine dmi.product.version: 1.0 dmi.sys.vendor: QEMU -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926955 Title: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" Status in linux package in Ubuntu: Confirmed Bug description: We recently installed some new arm64 Ampere eMAG hardware in the ScalingStack region which we use to run autopkgtests. Guests (currently impish VMs on OpenStack) which we spawn often fail to reboot, repeating this over and over: IRQ Exception at 0x9BC11F38 Steps to reproduce: 1. Boot a current impish daily cloud image (have not confirmed other releases) in a VM on an Ampere eMAG (have not verified bare metal). 2. Wait for it to come up, and then issue `sudo reboot` 3. If the machine comes back up again, repeat #2 a few times. This is intermittent. 3a. If it fails, take a look at "openstack console log " for the IRQ exception which repeats indefinitely. (stand by, I will get something to attach shortly) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 3 12:45 seq crw-rw 1 root audio 116, 33 May 3 12:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 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: Casper
[Kernel-packages] [Bug 1700563] Re: linux: 3.2.0-129.174 -proposed tracker
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives: 1700565,1700566
-- swm properties --
boot-testing-requested: true
+ packages:
+ lbm: linux-backports-modules-3.2.0
+ main: linux
+ meta: linux-meta
phase: Released
proposed-announcement-sent: true
proposed-testing-requested: true
+ reason: {}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1700563
Title:
linux: 3.2.0-129.174 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Invalid
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Precise:
Fix Released
Bug description:
This bug is for tracking the upload package.
This bug will contain status and testing results related to that
upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives: 1700565,1700566
-- swm properties --
boot-testing-requested: true
packages:
lbm: linux-backports-modules-3.2.0
main: linux
meta: linux-meta
phase: Released
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1700563/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704996] Re: linux: 3.2.0-130.176 -proposed tracker
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives: 1704997,1704999
-- swm properties --
boot-testing-requested: true
+ packages:
+ lbm: linux-backports-modules-3.2.0
+ main: linux
+ meta: linux-meta
phase: Released
proposed-announcement-sent: true
proposed-testing-requested: true
+ reason: {}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1704996
Title:
linux: 3.2.0-130.176 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Invalid
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Precise:
Fix Released
Bug description:
This bug is for tracking the upload package.
This bug will contain status and testing results related to that
upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives: 1704997,1704999
-- swm properties --
boot-testing-requested: true
packages:
lbm: linux-backports-modules-3.2.0
main: linux
meta: linux-meta
phase: Released
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1704996/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741612] Re: linux: 3.2.0-132.178 -proposed tracker
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives:
-- swm properties --
+ packages:
+ lbm: linux-backports-modules-3.2.0
+ main: linux
+ meta: linux-meta
phase: Released
+ reason: {}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1741612
Title:
linux: 3.2.0-132.178 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Invalid
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Invalid
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Precise:
Fix Released
Bug description:
This bug is for tracking the upload package.
This bug will contain status and testing results related to that
upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives:
-- swm properties --
packages:
lbm: linux-backports-modules-3.2.0
main: linux
meta: linux-meta
phase: Released
reason: {}
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1741612/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716644] Re: linux: 3.2.0-131.177 -proposed tracker
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives:
-- swm properties --
boot-testing-requested: true
+ packages:
+ lbm: linux-backports-modules-3.2.0
+ main: linux
+ meta: linux-meta
phase: Released
proposed-announcement-sent: true
proposed-testing-requested: true
+ reason: {}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1716644
Title:
linux: 3.2.0-131.177 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Precise:
Fix Released
Bug description:
This bug is for tracking the upload package.
This bug will contain status and testing results related to that
upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives:
-- swm properties --
boot-testing-requested: true
packages:
lbm: linux-backports-modules-3.2.0
main: linux
meta: linux-meta
phase: Released
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1716644/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745959] Re: linux: 3.2.0-133.179 -proposed tracker
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives:
-- swm properties --
boot-testing-requested: true
+ packages:
+ lbm: linux-backports-modules-3.2.0
+ main: linux
+ meta: linux-meta
phase: Released
proposed-announcement-sent: true
proposed-testing-requested: true
+ reason: {}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1745959
Title:
linux: 3.2.0-133.179 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Precise:
Fix Released
Bug description:
This bug is for tracking the upload package.
This bug will contain status and testing results related to that
upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives:
-- swm properties --
boot-testing-requested: true
packages:
lbm: linux-backports-modules-3.2.0
main: linux
meta: linux-meta
phase: Released
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1745959/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788762] Re: linux: 3.2.0-135.181 -proposed tracker
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives:
-- swm properties --
boot-testing-requested: true
bugs-spammed: true
+ packages:
+ lbm: linux-backports-modules-3.2.0
+ main: linux
+ meta: linux-meta
phase: Released
proposed-announcement-sent: true
proposed-testing-requested: true
+ reason: {}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788762
Title:
linux: 3.2.0-135.181 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
New
Status in Kernel SRU Workflow verification-testing series:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Precise:
Fix Released
Bug description:
This bug is for tracking the upload package.
This bug will contain status and testing results related to that
upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives:
-- swm properties --
boot-testing-requested: true
bugs-spammed: true
packages:
lbm: linux-backports-modules-3.2.0
main: linux
meta: linux-meta
phase: Released
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788762/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799398] Re: linux: 3.2.0-137.183 -proposed tracker
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives:
-- swm properties --
boot-testing-requested: true
bugs-spammed: true
+ packages:
+ lbm: linux-backports-modules-3.2.0
+ main: linux
+ meta: linux-meta
phase: Released
proposed-announcement-sent: true
proposed-testing-requested: true
+ reason: {}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799398
Title:
linux: 3.2.0-137.183 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Precise:
Fix Released
Bug description:
This bug is for tracking the upload package.
This bug will contain status and testing results related to that
upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives:
-- swm properties --
boot-testing-requested: true
bugs-spammed: true
packages:
lbm: linux-backports-modules-3.2.0
main: linux
meta: linux-meta
phase: Released
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799398/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
