[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
** Tags added: regression-release ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: linux (Ubuntu Impish) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in alsa-topology-conf package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Confirmed Status in alsa-topology-conf source package in Focal: New Status in alsa-ucm-conf source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in linux-firmware source package in Focal: Confirmed Status in alsa-topology-conf source package in Hirsute: New Status in alsa-ucm-conf source package in Hirsute: Won't Fix Status in linux source package in Hirsute: Fix Released Status in linux-firmware source package in Hirsute: Confirmed Status in alsa-topology-conf source package in Impish: New Status in alsa-ucm-conf source package in Impish: Won't Fix Status in linux source package in Impish: Fix Released Status in linux-firmware source package in Impish: Confirmed Bug description: [SRU Justification] [Impact] Skylake, Kabylake, Kabylake-refresh, Amberlake and some other platforms where audio is of SPT (PCH) type, HDA (with DSP capabilities) plus DMIC configuration is supported on these with skylake driver since kernel 5.8. However, no sound card can be detected w/o the topology binary file in /lib/firmware and corresponding ucm file. [Fix] The kernel config CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC needa to be enabled for the snd_soc_skl driver to support HDA+DMIC configuration. And the topology binary file and UCM files need to be located in the correct path based on Intel's suggestion. https://gist.github.com/crojewsk/4e6382bfb0dbfaaf60513174211f29cb. [Test] On the Skylake/Kabylake platforms with either the PCI device 8086:9d70 and 8086:9d71, boot up the machine and check the existence of the sound card by either 'aplay -l' or 'pactl list' command. [Where problems could occur] Should be low risk, it only affects limited Intel Platforms with particular PCI device IDs + HDA plus DMIC configuration. == Original Bug Description == Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvr
[Kernel-packages] [Bug 1944991] Re: Resume on glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) when shadowPrimary is off
** Package changed: linux (Ubuntu) => xserver-xorg-video-ati (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/1944991 Title: Resume on glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics" (ChipID = 0x9611) when shadowPrimary is off Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Bug description: GPU: ATI Radeon 3100 Graphics (ChipID = 0x9611) (RS780) GPU Lockup message in dmesg output after resume: [ 916.000550] radeon :01:05.0: ring 0 stalled for more than 10084msec [ 916.000569] radeon :01:05.0: GPU lockup (current fence id 0x20cc last fence id 0x20d6 on ring 0) [ 916.516556] radeon :01:05.0: ring 0 stalled for more than 10600msec [ 916.516569] radeon :01:05.0: GPU lockup (current fence id 0x20cc last fence id 0x20d6 on ring 0) [ 917.024566] radeon :01:05.0: ring 0 stalled for more than 11108msec [ 917.024575] radeon :01:05.0: GPU lockup (current fence id 0x20cc last fence id 0x20d6 on ring 0) [ 917.536558] radeon :01:05.0: ring 0 stalled for more than 11620msec [ 917.536570] radeon :01:05.0: GPU lockup (current fence id 0x20cc last fence id 0x20d6 on ring 0) [ 918.048571] radeon :01:05.0: ring 0 stalled for more than 12132msec [ 918.048580] radeon :01:05.0: GPU lockup (current fence id 0x20cc last fence id 0x20d6 on ring 0) ... [ 935.726783] radeon :01:05.0: GPU softreset: 0x0019 [ 935.726788] radeon :01:05.0: R_008010_GRBM_STATUS = 0xE57034E0 [ 935.726793] radeon :01:05.0: R_008014_GRBM_STATUS2 = 0x00110103 [ 935.726797] radeon :01:05.0: R_000E50_SRBM_STATUS = 0x2040 [ 935.726801] radeon :01:05.0: R_008674_CP_STALLED_STAT1 = 0x0100 [ 935.726805] radeon :01:05.0: R_008678_CP_STALLED_STAT2 = 0x1002 [ 935.726809] radeon :01:05.0: R_00867C_CP_BUSY_STAT = 0x00028486 [ 935.726813] radeon :01:05.0: R_008680_CP_STAT = 0x80838645 [ 935.726817] radeon :01:05.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 935.779906] radeon :01:05.0: R_008020_GRBM_SOFT_RESET=0x7FEF [ 935.779962] radeon :01:05.0: SRBM_SOFT_RESET=0x0100 [ 935.782061] radeon :01:05.0: R_008010_GRBM_STATUS = 0xA0003030 [ 935.782066] radeon :01:05.0: R_008014_GRBM_STATUS2 = 0x0003 [ 935.782070] radeon :01:05.0: R_000E50_SRBM_STATUS = 0x20008040 [ 935.782074] radeon :01:05.0: R_008674_CP_STALLED_STAT1 = 0x [ 935.782078] radeon :01:05.0: R_008678_CP_STALLED_STAT2 = 0x [ 935.782081] radeon :01:05.0: R_00867C_CP_BUSY_STAT = 0x [ 935.782085] radeon :01:05.0: R_008680_CP_STAT = 0x8010 [ 935.782089] radeon :01:05.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 935.782097] radeon :01:05.0: GPU reset succeeded, trying to resume Graphics is broken... text hardly readable, interface not responding. First observed on latest Mint (20.2)... then discovered Peppermint 10 was not affected. I believe Peppermint 10 is based on 18.04 and I am unsure why it is not affected. I tested with many versions of Ubuntu... Before 17.04... no problem... but was using EXA acceleration. 17.04 first to use Glamor... screen corruption is not obvious... but dmesg show GPU lockup... 17.10 and following is really problematic after resume, but possible to Ctrl-Alt-F4 to go to a text console and ... sudo reboot. There is a possibility I missed the exact version as I don't have my notes near me. Adding Option "AccelMethod" "EXA" at the good place in xorg.conf file have fixed the issue. I am unlikely to have access again to that specific computer in the future. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 6610 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.465 DistroRelease: Ubuntu 21.10 IwConfig: lono wireless extensions. enp63s0 no wireless extensions. LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210920) MachineType: Hewlett-Packard HP Compaq dc5850 Small Form Factor NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon runn
[Kernel-packages] [Bug 1912935] Re: battery drain while notebook off / shutdown
@kaihengfeng Please let me know as soon as you have a new kernel to test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
I can confirm this also happens on elementary OS 6 with nvidia-driver-470. I tried to add a limit to /etc/systemd/journald.conf, but it didn't help at all. Finally I managed to limit the log size using this tutorial: https://askubuntu.com/questions/184949/how-do-i-limit-the-size-of-my-syslog I still have problems with hight CPU & SSD usage caused by the logging, but at least it doesn't fill my disk entirely. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0
This is the correct patch for the AER message spew. ** Patch removed: "0001-PCI-AER-Clear-error-device-AER-registers-in-aer_irq.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+attachment/5530246/+files/0001-PCI-AER-Clear-error-device-AER-registers-in-aer_irq.patch ** Patch added: "0001-PCI-AER-Clear-error-device-AER-registers-in-aer_irq.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+attachment/5530304/+files/0001-PCI-AER-Clear-error-device-AER-registers-in-aer_irq.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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1521173]
Created attachment 299047 attachment-6460-0.html Hi Naveen. Absolutely, I can test. I can try it out this weekend. Chris Get BlueMail for Android On Oct 1, 2021, 2:35 AM, at 2:35 AM, bugzilla-dae...@bugzilla.kernel.org wrote: >https://bugzilla.kernel.org/show_bug.cgi?id=109691 > >Naveen Naidu (naveennaidu...@gmail.com) changed: > > What|Removed |Added > > CC||naveennaidu...@gmail.com > >--- Comment #11 from Naveen Naidu (naveennaidu...@gmail.com) --- >Created attachment 299043 > --> https://bugzilla.kernel.org/attachment.cgi?id=299043&action=edit >Patch for the AER message spew > >Hello Folks, > >I have been working on a patch for the AER message spew. I have a >potential >patch ready for the problem, but unfortunately, I do not have a system >that >outputs the same AER errors so I am unable to test it out. > >It would really help if anyone could please test this patch and see if >it >solved the AER message spew. > >Thanks, >Naveen Naidu > >-- >You may reply to this email to add a comment. > >You are receiving this mail because: >You reported the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc.
[Kernel-packages] [Bug 1521173]
Created attachment 299073 Patch for the AER message spew -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1521173]
Created attachment 299071 Patch for the AER message spew This is the correct patch. Please use this and ignore the previous 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1521173]
Comment on attachment 299043 Patch for the AER message spew I apologize, please ignore this patch. I realized there is a bug in the patch. I have fixed it now and will upload it. I apologized for the inconvenience caused. I do not know how to delete this patch, so I'll reupload a new patch. Apologies again ^^' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945905] [NEW] Not working with sysvinit
Public bug reported: Please ignore, submitted in error. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945905 Title: Not working with sysvinit Status in linux package in Ubuntu: Invalid Bug description: Please ignore, submitted in error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945905] Re: Not working with sysvinit
** Description changed: - I'm running an Asus Zenbook UX425EA with MX Linux 19.4 AHS, with - sysvinit as its init, not systemd. Is there a way to make it work with - sysvinit? + Please ignore, submitted in error. ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945905 Title: Not working with sysvinit Status in linux package in Ubuntu: Invalid Bug description: Please ignore, submitted in error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Is there a way to get this working with sysvinit (I'm not using systemd)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945309] Re: Screen flickering on Ubuntu 20.04 - HP Spectre X360 with Intel Skylake GT2 [HD Graphics 520]
Alright I will be waiting for that, thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1945309 Title: Screen flickering on Ubuntu 20.04 - HP Spectre X360 with Intel Skylake GT2 [HD Graphics 520] Status in linux-hwe-5.11 package in Ubuntu: New Bug description: I am using Ubuntu 20.04.3 LTS on my HP Spectre X360 with Intel Skylake GT2 [HD Graphics 520] and I am having flickering graphics. The problem sometimes happens showing grey flickering boxes 5-6 times in a minute, and sometimes it does not happen for 2-3 minutes. Overall, it annoys me quite a lot. I have tried decreasing the refresh rate from 60Hz to lower options, but that didn't work. Updating the drivers or purging Intel graphics didn't work either. I also tried a couple of stuff I saw online regarding /etc/X11/xorg.conf.d/. I do not have this issue on Windows, therefore it must be Ubuntu- related. When I set nomodeset on GRUB and update it, flickering disappears, but at the cost of my brightness adjuster and Night Light. As for package I have: apt-cache policy pkgname N: Unable to locate package pkgname dpkg -l |grep xserver-xorg-core ii xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 amd64 Xorg X server - core server ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 28 11:55:47 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:804e] InstallationDate: Installed on 2021-09-22 (5 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: HP HP Spectre x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-36-generic root=UUID=c68313b0-c9ba-4714-abc0-dff5762a92b2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree""true" EndSection dmi.bios.date: 12/27/2019 dmi.bios.release: 15.54 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.54 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 804E dmi.board.vendor: HP dmi.board.version: 33.24 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 33.24 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.54:bd12/27/2019:br15.54:efr33.24:svnHP:pnHPSpectrex360Convertible:pvr:skuN7H72EA#AB8:rvnHP:rn804E:rvr33.24:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible dmi.product.sku: N7H72EA#AB8 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1028 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~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.11/+bug/1945309/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945868] [NEW] focal kvm virtio_net set_features failed (-22)
You have been subscribed to a public bug: Setup linux-modules-5.4.0-88-generic within focal guest on a (equal) ubuntu 20.04 kvm bare metal machine. When using virtio as network driver it is failing with: net eth0: Fail to set guest offload. virtio_net virtio1 eth0: set_features() failed (-22); wanted 0x008000174a29, left 0x0 0800017ca29 followed by further kern log entries: [ cut here ] netdevice: br0: failed to disable 0x8000 on eth0! WARNING: CPU: 0 PID: 1048 at net/core/dev.c:8683 __netdev_update_features+0x4d1/0x9f0 Modules linked in: macvlan virtio_gpu ttm drm_kms_helper fb_sys_fops input_leds syscopyarea joydev sysfillrect serio_raw sysimgblt mac_hid sch_fq_codel 9p fscache 9pnet_virtio 9pnet bridge stp llc drm virtio_rng ip_tables x_tables autofs4 dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c psmouse virtio_net i2c_piix4 virtio_blk net_failover failover pata_acpi floppy CPU: 0 PID: 1048 Comm: brctl Tainted: GW 5.4.0-88-generic #99-Ubuntu Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 RIP: 0010:__netdev_update_features+0x4d1/0x9f0 Code: c7 c2 9b 30 9b a0 4c 8b 4d 88 48 85 c0 4d 0f 44 d4 4d 89 f0 48 8d 4d b8 4c 89 ca 4c 89 d6 48 c7 c7 d0 94 a3 a0 e8 dc 2d 19 00 <0f> 0b e9 5b fe ff ff 8b 45 9c 85 c0 0f 84 96 00 00 00 8b 45 9c f7 RSP: 0018:bf1840e0ba98 EFLAGS: 00010282 RAX: RBX: 000f RCX: 0006 RDX: 0007 RSI: 0082 RDI: 9c2c13a178c0 RBP: bf1840e0bb10 R08: 02d1 R09: 0004 R10: R11: 0001 R12: 9c2c0b258000 R13: 9c2c0b2580c0 R14: 9c2c0615a000 R15: 000f FS: 7f98be558580() GS:9c2c13a0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7fffc24a1080 CR3: 00030b3e4000 CR4: 06f0 Call Trace: netdev_update_features+0x25/0x60 br_device_event+0x20f/0x300 [bridge] notifier_call_chain+0x55/0x80 raw_notifier_call_chain+0x16/0x20 call_netdevice_notifiers_info+0x2e/0x60 netdev_update_features+0x59/0x60 dev_disable_lro+0x21/0xf0 br_add_if+0x301/0x650 [bridge] add_del_if+0x67/0x80 [bridge] br_dev_ioctl+0x54/0x80 [bridge] dev_ifsioc+0xe5/0x3e0 ? _cond_resched+0x19/0x30 dev_ioctl+0x2dd/0x470 sock_do_ioctl+0xa8/0x140 ? evict+0x14c/0x1b0 sock_ioctl+0x24f/0x3c0 ? _cond_resched+0x19/0x30 ? get_max_files+0x20/0x20 do_vfs_ioctl+0x407/0x670 ksys_ioctl+0x67/0x90 __x64_sys_ioctl+0x1a/0x20 do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f98be47c50b Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 RSP: 002b:7ffd783321e8 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 0002 RCX: 7f98be47c50b RDX: 7ffd78332210 RSI: 89a2 RDI: 0003 RBP: 7ffd78332210 R08: 0020 R09: fefefeff77686d74 R10: 7ffd78333e80 R11: 0246 R12: 7ffd78333e7e R13: 7ffd78333e7e R14: R15: ---[ end trace 240d361752e8f3f0 ]--- [ cut here ] Temporary solution is to return to the old rtl8139 driver and slow network down ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: focal kvm virtio -- focal kvm virtio_net set_features failed (-22) https://bugs.launchpad.net/bugs/1945868 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 1945868] Re: focal kvm virtio_net set_features failed (-22)
There is no 'focal' package in any current release of Ubuntu. Assuming you meant to task against the kernel. So moving to 'linux'. ** Package changed: focal (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/1945868 Title: focal kvm virtio_net set_features failed (-22) Status in linux package in Ubuntu: New Status in qemu-kvm package in Ubuntu: New Bug description: Setup linux-modules-5.4.0-88-generic within focal guest on a (equal) ubuntu 20.04 kvm bare metal machine. When using virtio as network driver it is failing with: net eth0: Fail to set guest offload. virtio_net virtio1 eth0: set_features() failed (-22); wanted 0x008000174a29, left 0x0 0800017ca29 followed by further kern log entries: [ cut here ] netdevice: br0: failed to disable 0x8000 on eth0! WARNING: CPU: 0 PID: 1048 at net/core/dev.c:8683 __netdev_update_features+0x4d1/0x9f0 Modules linked in: macvlan virtio_gpu ttm drm_kms_helper fb_sys_fops input_leds syscopyarea joydev sysfillrect serio_raw sysimgblt mac_hid sch_fq_codel 9p fscache 9pnet_virtio 9pnet bridge stp llc drm virtio_rng ip_tables x_tables autofs4 dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c psmouse virtio_net i2c_piix4 virtio_blk net_failover failover pata_acpi floppy CPU: 0 PID: 1048 Comm: brctl Tainted: GW 5.4.0-88-generic #99-Ubuntu Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 RIP: 0010:__netdev_update_features+0x4d1/0x9f0 Code: c7 c2 9b 30 9b a0 4c 8b 4d 88 48 85 c0 4d 0f 44 d4 4d 89 f0 48 8d 4d b8 4c 89 ca 4c 89 d6 48 c7 c7 d0 94 a3 a0 e8 dc 2d 19 00 <0f> 0b e9 5b fe ff ff 8b 45 9c 85 c0 0f 84 96 00 00 00 8b 45 9c f7 RSP: 0018:bf1840e0ba98 EFLAGS: 00010282 RAX: RBX: 000f RCX: 0006 RDX: 0007 RSI: 0082 RDI: 9c2c13a178c0 RBP: bf1840e0bb10 R08: 02d1 R09: 0004 R10: R11: 0001 R12: 9c2c0b258000 R13: 9c2c0b2580c0 R14: 9c2c0615a000 R15: 000f FS: 7f98be558580() GS:9c2c13a0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7fffc24a1080 CR3: 00030b3e4000 CR4: 06f0 Call Trace: netdev_update_features+0x25/0x60 br_device_event+0x20f/0x300 [bridge] notifier_call_chain+0x55/0x80 raw_notifier_call_chain+0x16/0x20 call_netdevice_notifiers_info+0x2e/0x60 netdev_update_features+0x59/0x60 dev_disable_lro+0x21/0xf0 br_add_if+0x301/0x650 [bridge] add_del_if+0x67/0x80 [bridge] br_dev_ioctl+0x54/0x80 [bridge] dev_ifsioc+0xe5/0x3e0 ? _cond_resched+0x19/0x30 dev_ioctl+0x2dd/0x470 sock_do_ioctl+0xa8/0x140 ? evict+0x14c/0x1b0 sock_ioctl+0x24f/0x3c0 ? _cond_resched+0x19/0x30 ? get_max_files+0x20/0x20 do_vfs_ioctl+0x407/0x670 ksys_ioctl+0x67/0x90 __x64_sys_ioctl+0x1a/0x20 do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f98be47c50b Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 RSP: 002b:7ffd783321e8 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 0002 RCX: 7f98be47c50b RDX: 7ffd78332210 RSI: 89a2 RDI: 0003 RBP: 7ffd78332210 R08: 0020 R09: fefefeff77686d74 R10: 7ffd78333e80 R11: 0246 R12: 7ffd78333e7e R13: 7ffd78333e7e R14: R15: ---[ end trace 240d361752e8f3f0 ]--- [ cut here ] Temporary solution is to return to the old rtl8139 driver and slow network down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945868] 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 1945868 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/1945868 Title: focal kvm virtio_net set_features failed (-22) Status in linux package in Ubuntu: Incomplete Status in qemu-kvm package in Ubuntu: New Bug description: Setup linux-modules-5.4.0-88-generic within focal guest on a (equal) ubuntu 20.04 kvm bare metal machine. When using virtio as network driver it is failing with: net eth0: Fail to set guest offload. virtio_net virtio1 eth0: set_features() failed (-22); wanted 0x008000174a29, left 0x0 0800017ca29 followed by further kern log entries: [ cut here ] netdevice: br0: failed to disable 0x8000 on eth0! WARNING: CPU: 0 PID: 1048 at net/core/dev.c:8683 __netdev_update_features+0x4d1/0x9f0 Modules linked in: macvlan virtio_gpu ttm drm_kms_helper fb_sys_fops input_leds syscopyarea joydev sysfillrect serio_raw sysimgblt mac_hid sch_fq_codel 9p fscache 9pnet_virtio 9pnet bridge stp llc drm virtio_rng ip_tables x_tables autofs4 dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c psmouse virtio_net i2c_piix4 virtio_blk net_failover failover pata_acpi floppy CPU: 0 PID: 1048 Comm: brctl Tainted: GW 5.4.0-88-generic #99-Ubuntu Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 RIP: 0010:__netdev_update_features+0x4d1/0x9f0 Code: c7 c2 9b 30 9b a0 4c 8b 4d 88 48 85 c0 4d 0f 44 d4 4d 89 f0 48 8d 4d b8 4c 89 ca 4c 89 d6 48 c7 c7 d0 94 a3 a0 e8 dc 2d 19 00 <0f> 0b e9 5b fe ff ff 8b 45 9c 85 c0 0f 84 96 00 00 00 8b 45 9c f7 RSP: 0018:bf1840e0ba98 EFLAGS: 00010282 RAX: RBX: 000f RCX: 0006 RDX: 0007 RSI: 0082 RDI: 9c2c13a178c0 RBP: bf1840e0bb10 R08: 02d1 R09: 0004 R10: R11: 0001 R12: 9c2c0b258000 R13: 9c2c0b2580c0 R14: 9c2c0615a000 R15: 000f FS: 7f98be558580() GS:9c2c13a0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7fffc24a1080 CR3: 00030b3e4000 CR4: 06f0 Call Trace: netdev_update_features+0x25/0x60 br_device_event+0x20f/0x300 [bridge] notifier_call_chain+0x55/0x80 raw_notifier_call_chain+0x16/0x20 call_netdevice_notifiers_info+0x2e/0x60 netdev_update_features+0x59/0x60 dev_disable_lro+0x21/0xf0 br_add_if+0x301/0x650 [bridge] add_del_if+0x67/0x80 [bridge] br_dev_ioctl+0x54/0x80 [bridge] dev_ifsioc+0xe5/0x3e0 ? _cond_resched+0x19/0x30 dev_ioctl+0x2dd/0x470 sock_do_ioctl+0xa8/0x140 ? evict+0x14c/0x1b0 sock_ioctl+0x24f/0x3c0 ? _cond_resched+0x19/0x30 ? get_max_files+0x20/0x20 do_vfs_ioctl+0x407/0x670 ksys_ioctl+0x67/0x90 __x64_sys_ioctl+0x1a/0x20 do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f98be47c50b Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 RSP: 002b:7ffd783321e8 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 0002 RCX: 7f98be47c50b RDX: 7ffd78332210 RSI: 89a2 RDI: 0003 RBP: 7ffd78332210 R08: 0020 R09: fefefeff77686d74 R10: 7ffd78333e80 R11: 0246 R12: 7ffd78333e7e R13: 7ffd78333e7e R14: R15: ---[ end trace 240d361752e8f3f0 ]--- [ cut here ] Temporary solution is to return to the old rtl8139 driver and slow network down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Hmm. Got 5.14.9 running directly from the https://kernel.ubuntu.com/~kernel-ppa/mainline/ repository. Works with nvidia driver 4.70 on Mint 20.2 :) build sequence: - checkout cod/mainline/v5.14.9 from git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack - install libfuse-dev (shown in the selftest fail log, so I guessed it can't hurt) - time sudo debian/rules clean - time sudo dpkg-buildpackage -d -nc --no-sign -j33 - sudo chown -R : .. Prerequisites is having built dwarves, libbpf, and probably zstd like mentioned in #71. Package runs successfully on several machines. One oddity I've seen: running the build again will fail. You need to git clean -df multiple times, and do a git reset --hard . But pretty straight forward anyway. -- You 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 1944389] Re: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz
Checked with kernel 5.13.0-1014-oem (5.11.0-37-generic is not usable for this laptop as wifi and external display are not recognized) Both # echo idle > workload_type or # echo bursty > workload_type are not helpful. Also balance_power is in /sys/devices/system/cpu/cpufreq/policy$i/energy_performance_preference for every CPU by default. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1944389 Title: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz Status in thermald package in Ubuntu: New Bug description: After update to 1.9.1-1ubuntu0.6 from 1.9.1-1ubuntu0.4 thermald keeps Tigerlake Iris Xe GPU frequency on 400 MHz after reaching some high temperature value. It became impossible to play video games on the laptop. System: Ubuntu 20.04.3 LTS Kernel: 5.10.0-1045-oem Laptop: Dell XPS 9310, CPU: Intel Core i7-1165G7 (Tigerlake), Integrated GPU Iris Xe. BIOS 2.1.1 03/25/2021 Display: 2560x1440 144Hz HDMI USB-C connection Room temperature is 23.5-25.4 degrees Game: Stalker Clear Sky (Wine/Proton Steam) Note: The game itself is very old and loads 100% of one CPU core disregarding of frequency. GPU frequency is monitored by intel-gpu-top GPU frequencies (according to /sys/class/drm/card0/) min/max/boost/efficiency: 100/1300/1300/400 Previous behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. After some time when threshold temperature value (~78 degrees) is reached the GPU frequency decreases to ~660 MHz and FPS to 40-48 FPS. Package temperature decreases to 66-68 degrees. It's possible to play for indefinite amount of time. New behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. But after reaching the threshold temperature (about 81 degrees) GPU frequency decreases to 400 MHz (gt_RP1_freq_mhz -- "efficiency" temperature for the GPU) and stays on this value for the indefinite amount of time. The temperature is maintained on 70-74 degrees. FPS is about 25-30 FPS, it is not possible to play the game anymore. The only way to return the good FPS and frequency is to fold the game window, wait some time and open it again. Also there is a workaround -- limit the CPU frequency to 2001 MHz and disable Intel turbo boost. With such approach package temperature never reaches 80 degrees and it is possible to play game with 500 MHz and 35-40 FPS. Better than nothing. If it is needed I can perform any additional checks, provide CPU frequencies and so on. Most probably regression happened with 1.9.1-1ubuntu0.5, but I tried only versions 0.4 and 0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1944389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945749] Re: Xorg freeze
I had yet another freeze... ** Attachment added: "prevboot2.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1945749/+attachment/5530376/+files/prevboot2.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1945749 Title: Xorg freeze Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: System randomly freezes, no clue how to reproduce it. Multiple people have the same issue. Dell Precision 5550 running Ubuntu 20.04.3 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:41:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.11.0-36-generic, x86_64: installed nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:097e] Subsystem: Dell TU117GLM [Quadro T1000 Mobile] [1028:097e] InstallationDate: Installed on 2021-08-27 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=42e96b11-9efb-45e0-ace2-85fe35b2047b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnPrecision5550:pvr:sku097E:rvnDellInc.:rn0V6K79:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5550 dmi.product.sku: 097E dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.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~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/nvidia-graphics-drivers-470/+bug/1945749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
In Ubuntu 21.10 with 5.13.0-16-generic kernel, I don't get any dmesg errors after I "modprobe b44" and Ethernet works initially at reasonable speed, but the whole system freezes totally after a few minutes. I suppose this means the b44 driver still doesn't work properly, because I don't get such freezes when using WiFi. Though I don't know for sure, because I don't have any error messages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821564 Title: b44 Ethernet driver null pointer during initialization Status in linux package in Ubuntu: Incomplete Bug description: This problem started after upgrading to Ubuntu 19.04. It was not present with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic kernel. Ever time during boot there is a null pointer dereference in the b44 driver for the on-board Ethernet on this Dell Inspiron 6400. After that I can log in but networking related commands hang and the computer eventually locks up. Blacklisting the b44 module so it doesn't load works as a workaround, though of course the on board Ethernet can't be used that way. The b43 WiFi still works then. The following is pasted from the log of one crash: 6.483003] BUG: unable to handle kernel NULL pointer dereference at 6.483052] #PF error: [normal kernel read fault] 6.483093] PGD 0 P4D 0 6.483133] Oops: [#1] SMP PTI 6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 5.0.0-7-generic #8-Ubuntu 6.483217] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f 6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016 6.483416] RAX: 0001 RBX: RCX: 6.483467] RDX: RSI: 001f RDI: 0001 6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001 6.483572] R10: R11: R12: 6.483621] R13: R14: 0001 R15: 0020 6.483670] FS: 7f2cb49ccbc0() GS:9d8a4c40() knlGS: 6.483726] CS: 0010 DS: ES: CR0: 80050033 6.483773] CR2: CR3: c72ce000 CR4: 06f0 6.483820] Call Trace: 6.483869] swiotlb_map+0x6c/0x1c0 6.483915] dma_direct_map_page+0xc5/0x160 6.483965] b44_alloc_rx_skb+0x18e/0x3f0 [b44] 6.484013] b44_init_rings+0xbe/0x1b0 [b44] 6.484060] b44_open+0xfc/0x3f0 [b44] 6.484107] __dev_open+0xd4/0x170 6.484153] __dev_change_flags+0x18f/0x200 6.484199] dev_change_flags+0x27/0x60 6.484246] do_setlink+0x31c/0xe30 6.484292] ? __nla_parse+0xf1/0x120 6.484340] ? cpumask_next+0x1b/0x20 6.484388] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 6.484439] ? __nla_parse+0x38/0x120 6.484488] __rtnl_newlink+0x531/0x910 6.484535] ? __nla_put+0x20/0x30 6.484586] ? __kmalloc_node_track_caller+0x1e6/0x2b0 6.484636] ? pskb_expand_head+0x70/0x2e0 6.484693] ? __kmalloc_reserve.isra.53+0x31/0x90 6.484751] ? apparmor_inet_conn_request+0x40/0x40 6.484822] ? security_sock_rcv_skb+0x2f/0x50 6.484879] ? skb_queue_tail+0x43/0x50 6.484934] ? __netlink_sendskb+0x53/0x70 6.484992] ? syscall_return_via_sysret+0xf/0x7f 6.485043] ? __switch_to_asm+0x40/0x70 6.485097] ? syscall_return_via_sysret+0xf/0x7f 6.485153] ? _cond_resched+0x19/0x30 6.485204] ? kmem_cache_alloc_trace+0x153/0x1d0 6.485253] rtnl_newlink+0x48/0x70 6.485301] rtnetlink_rcv_msg+0x213/0x300 6.485348] ? __d_lookup+0x126/0x140 6.485393] ? rtnl_calcit.isra.31+0x100/0x100 6.485440] netlink_rcv_skb+0x4f/0x120 6.485485] rtnetlink_rcv+0x15/0x20 6.485518] netlink_unicast+0x1a1/0x260 6.485518] netlink_sendmsg+0x20d/0x3c0 6.485518] sock_sendmsg+0x3e/0x50 6.485518] ___sys_sendmsg+0x295/0x2f0 6.485518] ? rtnl_unlock+0xe/0x10 6.485518] ? addrconf_sysctl_forward+0x114/0x280 6.485518] ? dev_forward_change+0x140/0x140 6.485518] ? __fget_light+0x54/0x60 6.485518] __sys_sendmsg+0x5c/0xa0 6.485518] __x64_sys_sendmsg+0x1f/0x30 6.485518] do_syscall_64+0x5a/0x110 6.485518] entry_SYSCALL_64_after_hwframe+0x44/0xa9 6.485518] RIP: 0033:0x7f2cb6153cb7 6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48 6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293 ORIG_RAX: 002e 6.485518] RAX: ffda RBX: 0008 RCX: 7f2cb6153
[Kernel-packages] [Bug 1945927] [NEW] Terrible resolution on integrated webcam on Dell XPS 13 Developer Edition 9310
Public bug reported: This seems to be a known issue, but I couldn't find any launchpad bug corresponding to it. Apologies if I missed it, or if there is a better place for reporting a bug like this. When I try to use the webcam on my newly purchased Dell XPS-13-9310 Developer Edition, using Cheese (or any other app) on Ubuntu 20.04.2 LTS (fossa-bulbasaur X55), as it came out of the box, I only get a very pixelated low quality 640x480 resolution instead of the hardware's 1280×720 capability as advertised here: https://www.dell.com/en-us/work/shop/dell-laptops-and- notebooks/xps-13-developer-edition/spd/xps-13-9310-laptop From what I gather, no linux driver exist that can use the full resolution of this webcam. I hope that it is somehow possible to get a proper driver from Dell / Realtek. If not, I hope that Realtek can provide documentation for the interface so that a proper driver can be written. I'm tempted to try to make that my first contribution of a driver, but in all likelihood I won't have the time or motivation to learn all that's needed and actually write it. Until a driver is available, I would appreciate if Dell would clarify on their website that their 9310 Developer Edition can only use the full advertised resolution in Windows. (I would not have bought this laptop if I had known about this limitation, as I frequently use Google Meet / Zoom and the current quality is not acceptable to me). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1045-oem 5.10.0-1045.47 ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46 Uname: Linux 5.10.0-1045-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 3 15:40:31 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2021-09-22 (11 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1945927 Title: Terrible resolution on integrated webcam on Dell XPS 13 Developer Edition 9310 Status in linux-signed-oem-5.10 package in Ubuntu: New Bug description: This seems to be a known issue, but I couldn't find any launchpad bug corresponding to it. Apologies if I missed it, or if there is a better place for reporting a bug like this. When I try to use the webcam on my newly purchased Dell XPS-13-9310 Developer Edition, using Cheese (or any other app) on Ubuntu 20.04.2 LTS (fossa-bulbasaur X55), as it came out of the box, I only get a very pixelated low quality 640x480 resolution instead of the hardware's 1280×720 capability as advertised here: https://www.dell.com/en-us/work/shop/dell-laptops-and- notebooks/xps-13-developer-edition/spd/xps-13-9310-laptop From what I gather, no linux driver exist that can use the full resolution of this webcam. I hope that it is somehow possible to get a proper driver from Dell / Realtek. If not, I hope that Realtek can provide documentation for the interface so that a proper driver can be written. I'm tempted to try to make that my first contribution of a driver, but in all likelihood I won't have the time or motivation to learn all that's needed and actually write it. Until a driver is available, I would appreciate if Dell would clarify on their website that their 9310 Developer Edition can only use the full advertised resolution in Windows. (I would not have bought this laptop if I had known about this limitation, as I frequently use Google Meet / Zoom and the current quality is not acceptable to me). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1045-oem 5.10.0-1045.47 ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46 Uname: Linux 5.10.0-1045-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 3 15:40:31 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2021-09-22 (11 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
[Kernel-packages] [Bug 1930754] Re: e1000e extremly slow
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1930754 Title: e1000e extremly slow Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] e1000e on TGP PCH encounters a network speed issue that rx speed is below 1MB/s [Fix] Intel provides 2 patches to fix this https://patchwork.ozlabs.org/project/intel-wired-lan/list/?series=263466 [Test] Verified by our Dell and Lenovo platforms and the bug reporter. [Where problems could occur] The fix only applies to e1000e with TGP PCH, and add a flag "E1000_FFLT_DBG_DONT_GATE_WAKE_DMA_CLK". The impact should be minimized and should not lead to other regressions. = We have dell latitude 5420 & 5520 laptops with onboard intel ethernet controller. Problem is that the ethernet port is extremely slow. about 100kbyte/s download throughput while on a gigabit connection. Upload seems to work just fine. Also when I pxe boot the system it's also painfully slow. But here comes the funny part. When I attach a usb memory stick the throughput of the networkcontroller is as expected. I've used latest ubuntu 20.04.2 kernel 5.8.0-55 I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem Turns out this problem is not showing up when I manually install the 5.8.18 kernel. Also when I create my own iso with the help of Cubic and install the 5.8.18 kernel in it the pxe boot is working as expected with high throughput system: Dell latitude 5420 + 5520 nic: Ethernet Connection (13) I219-LM ubuntu 20.04.2 module: e1000e Please assist. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930754] Re: e1000e extremly slow
5.10.0-1049.51 does test passed from my side. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1930754 Title: e1000e extremly slow Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] e1000e on TGP PCH encounters a network speed issue that rx speed is below 1MB/s [Fix] Intel provides 2 patches to fix this https://patchwork.ozlabs.org/project/intel-wired-lan/list/?series=263466 [Test] Verified by our Dell and Lenovo platforms and the bug reporter. [Where problems could occur] The fix only applies to e1000e with TGP PCH, and add a flag "E1000_FFLT_DBG_DONT_GATE_WAKE_DMA_CLK". The impact should be minimized and should not lead to other regressions. = We have dell latitude 5420 & 5520 laptops with onboard intel ethernet controller. Problem is that the ethernet port is extremely slow. about 100kbyte/s download throughput while on a gigabit connection. Upload seems to work just fine. Also when I pxe boot the system it's also painfully slow. But here comes the funny part. When I attach a usb memory stick the throughput of the networkcontroller is as expected. I've used latest ubuntu 20.04.2 kernel 5.8.0-55 I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem Turns out this problem is not showing up when I manually install the 5.8.18 kernel. Also when I create my own iso with the help of Cubic and install the 5.8.18 kernel in it the pxe boot is working as expected with high throughput system: Dell latitude 5420 + 5520 nic: Ethernet Connection (13) I219-LM ubuntu 20.04.2 module: e1000e Please assist. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945932] [NEW] Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
Public bug reported: [Impact] *** this issue happen with secure boot on and issue gone when secure boot is off*** After the BIOS loading screen, a yellow screen pops up in an instant (< 1 second) and then disappears. Attached a demo video. [Fix] do what intel_color_commit() does to make sure the bottom color state matches whatever out hardware readout produced. Ref. https://patchwork.freedesktop.org/patch/456170/?series=95171&rev=1 [Test] 1. Power on the system 2. Check if any unusual screen shows before and after the system loading screen. 3. No unusual screen shows before and after the system loading screen [Regression Potential] Medium, maintainer still not totally sure what should do about color management features here in general. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.13 (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: linux (Ubuntu Impish) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu Impish) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Impish) 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/1945932 Title: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.10 source package in Focal: New Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: In Progress Status in linux-oem-5.13 source package in Hirsute: New Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: New Status in linux-oem-5.13 source package in Impish: New Bug description: [Impact] *** this issue happen with secure boot on and issue gone when secure boot is off*** After the BIOS loading screen, a yellow screen pops up in an instant (< 1 second) and then disappears. Attached a demo video. [Fix] do what intel_color_commit() does to make sure the bottom color state matches whatever out hardware readout produced. Ref. https://patchwork.freedesktop.org/patch/456170/?series=95171&rev=1 [Test] 1. Power on the system 2. Check if any unusual screen shows before and after the system loading screen. 3. No unusual screen shows before and after the system loading screen [Regression Potential] Medium, maintainer still not totally sure what should do about color management features here in general. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945932/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More hel
[Kernel-packages] [Bug 1945932] 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 1945932 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 ** Changed in: linux (Ubuntu Focal) Status: New => Incomplete ** Changed in: linux (Ubuntu Hirsute) 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/1945932 Title: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.10 source package in Focal: New Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: In Progress Status in linux-oem-5.13 source package in Hirsute: New Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: New Status in linux-oem-5.13 source package in Impish: New Bug description: [Impact] *** this issue happen with secure boot on and issue gone when secure boot is off*** After the BIOS loading screen, a yellow screen pops up in an instant (< 1 second) and then disappears. Attached a demo video. [Fix] do what intel_color_commit() does to make sure the bottom color state matches whatever out hardware readout produced. Ref. https://patchwork.freedesktop.org/patch/456170/?series=95171&rev=1 [Test] 1. Power on the system 2. Check if any unusual screen shows before and after the system loading screen. 3. No unusual screen shows before and after the system loading screen [Regression Potential] Medium, maintainer still not totally sure what should do about color management features here in general. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945932/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945932] Re: A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Hirsute) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Impish) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => koba (kobako) ** Summary changed: - A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system + Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945932 Title: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.10 source package in Focal: New Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: In Progress Status in linux-oem-5.13 source package in Hirsute: New Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: New Status in linux-oem-5.13 source package in Impish: New Bug description: [Impact] *** this issue happen with secure boot on and issue gone when secure boot is off*** After the BIOS loading screen, a yellow screen pops up in an instant (< 1 second) and then disappears. Attached a demo video. [Fix] do what intel_color_commit() does to make sure the bottom color state matches whatever out hardware readout produced. Ref. https://patchwork.freedesktop.org/patch/456170/?series=95171&rev=1 [Test] 1. Power on the system 2. Check if any unusual screen shows before and after the system loading screen. 3. No unusual screen shows before and after the system loading screen [Regression Potential] Medium, maintainer still not totally sure what should do about color management features here in general. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945932/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945895] [NEW] [HP EliteBook 820 G2] screen flickring after installing cpufreq
You have been subscribed to a public bug: after installing cpufreq the screen flickring and smoothness disappeared in ubuntu . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 3 18:57:55 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:225a] InstallationDate: Installed on 2021-07-01 (94 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard HP EliteBook 820 G2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3a425ccf-6b17-4740-a951-62415983b2e2 ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.release: 1.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M71 Ver. 01.04 dmi.board.name: 225A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.54 dmi.chassis.asset.tag: 5CG5172BFZ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 150.84 dmi.modalias: dmi:bvnHewlett-Packard:bvrM71Ver.01.04:bd02/24/2015:br1.4:efr150.84:svnHewlett-Packard:pnHPEliteBook820G2:pvrA3009C510203:skuN3F11EC#AB4:rvnHewlett-Packard:rn225A:rvrKBCVersion96.54:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 820 G2 dmi.product.sku: N3F11EC#AB4 dmi.product.version: A3009C510203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~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-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- [HP EliteBook 820 G2] screen flickring after installing cpufreq https://bugs.launchpad.net/bugs/1945895 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 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 1945932] Re: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
** Tags added: oem-priority originate-from-1923568 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945932 Title: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: New Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: In Progress Status in linux-oem-5.13 source package in Hirsute: New Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: New Status in linux-oem-5.13 source package in Impish: New Bug description: [Impact] *** this issue happen with secure boot on and issue gone when secure boot is off*** After the BIOS loading screen, a yellow screen pops up in an instant (< 1 second) and then disappears. Attached a demo video. [Fix] do what intel_color_commit() does to make sure the bottom color state matches whatever out hardware readout produced. Ref. https://patchwork.freedesktop.org/patch/456170/?series=95171&rev=1 [Test] 1. Power on the system 2. Check if any unusual screen shows before and after the system loading screen. 3. No unusual screen shows before and after the system loading screen [Regression Potential] Medium, maintainer still not totally sure what should do about color management features here in general. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945932/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945895] Re: screen flickring after installing cpufreq
Flickering and a lack of smoothness are two different issues. The lack of smoothness would just be due to your GPU staying at a lower frequency more often, so it's not a bug but something you would need to tune yourself. As for the flickering, please edit /etc/default/grub and change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0" and then run: sudo update-grub and reboot. If the problem still happens after that then while it is happening, please run: journalctl -b0 > journal.txt and attach the resulting text file here along with a video of the flickering problem. ** Summary changed: - screen flickring after installing cpufreq + [HP EliteBook 820 G2] screen flickring after installing cpufreq ** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu) ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1945895 Title: [HP EliteBook 820 G2] screen flickring after installing cpufreq Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: after installing cpufreq the screen flickring and smoothness disappeared in ubuntu . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 3 18:57:55 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:225a] InstallationDate: Installed on 2021-07-01 (94 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard HP EliteBook 820 G2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3a425ccf-6b17-4740-a951-62415983b2e2 ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.release: 1.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M71 Ver. 01.04 dmi.board.name: 225A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.54 dmi.chassis.asset.tag: 5CG5172BFZ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 150.84 dmi.modalias: dmi:bvnHewlett-Packard:bvrM71Ver.01.04:bd02/24/2015:br1.4:efr150.84:svnHewlett-Packard:pnHPEliteBook820G2:pvrA3009C510203:skuN3F11EC#AB4:rvnHewlett-Packard:rn225A:rvrKBCVersion96.54:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 820 G2 dmi.product.sku: N3F11EC#AB4 dmi.product.version: A3009C510203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~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.11/+bug/1945895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945932] Re: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
** Changed in: linux (Ubuntu Focal) Status: Incomplete => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: In Progress => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Assignee: koba (kobako) => (unassigned) ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945932 Title: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: New Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: New Status in linux-oem-5.13 source package in Impish: New Bug description: [Impact] *** this issue happen with secure boot on and issue gone when secure boot is off*** After the BIOS loading screen, a yellow screen pops up in an instant (< 1 second) and then disappears. Attached a demo video. [Fix] do what intel_color_commit() does to make sure the bottom color state matches whatever out hardware readout produced. Ref. https://patchwork.freedesktop.org/patch/456170/?series=95171&rev=1 [Test] 1. Power on the system 2. Check if any unusual screen shows before and after the system loading screen. 3. No unusual screen shows before and after the system loading screen [Regression Potential] Medium, maintainer still not totally sure what should do about color management features here in general. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945932/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945367] Re: [nvidia] Graphics freeze
The next step is to try uninstalling the Nvidia 470 driver and install 460 instead, using the 'Additional Drivers' app or: sudo apt remove nvidia-driver-470 sudo apt install nvidia-driver-460 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1945367 Title: [nvidia] Graphics freeze Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: i open a second bug report because i have already freeze problem after the installation of nvidia drivers and reboot. Freeze become generally when i am using firefox and visioning a video with youtube. I specify that since the last bug report, i re install ubuntu with official .iso without other package non official. To create the report, i have to connect to the PC from another one with ssh. When i use ubuntu-bug, it is not possible to join nvidia-bug-report because the application dont give me the hand to finish the report. When i try to execute nvidia-bug-report, i have the same thing. To use the PC, i have to use nouveau drivers and intel Xe GPU with poor performances ... Thanks for help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip Date: Tue Sep 28 21:13:05 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2090] NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2090] InstallationDate: Installed on 2021-09-26 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Intel(R) Client Systems NUC11PHi7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=24658b6f-3e37-4376-bc2e-2207e961c9c8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: PHTGL579.0063.2021.0707.1057 dmi.board.name: NUC11PHBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M26151-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 12.19 dmi.modalias: dmi:bvnIntelCorp.:bvrPHTGL579.0063.2021.0707.1057:bd07/07/2021:br5.19:efr12.19:svnIntel(R)ClientSystems:pnNUC11PHi7:pvrM26149-403:skuSWNUC11PHKi7C00:rvnIntelCorporation:rnNUC11PHBi7:rvrM26151-402:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: PH dmi.product.name: NUC11PHi7 dmi.product.sku: SWNUC11PHKi7C00 dmi.product.version: M26149-403 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.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~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/nvidia-graphics-drivers-470/+bug/1945367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packag
[Kernel-packages] [Bug 1945938] [NEW] [impish] Remove the downstream xr-usb-uart driver
Public bug reported: [Impact] The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS kernel to add support for USB UART chips: Family: USB UART Part Numbers: XR21V1410, XR21V1412, XR21V1414, XR21B1411, XR21B1420, XR21B1422, XR21B1424, XR22801, XR22802, XR22804 [Fix] In 5.13.x, support for these devices was added to the kernel via. following patch series: Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/ There have been long term maintenance challenges with the downstream vendor driver over the period of time (since 4.4.y based Xenial LTS). Now that upstream driver supports most of the above part numbers, let's remove this redundant out-of-tree driver. [Test] The driver was functionally verified to work fine with XR21V1412. The support for other chips with part numbers mentioned above are also supported with the above patch series. [Where problems could occur] Low. The downstream driver was designed to work with specific BIOS configs only defined on an IoT GW project which is locked to use only Xenial ESM and Bionic LTS kernels, there is a low chance of regression on the Impish series. ** Affects: linux (Ubuntu) Importance: High Status: Confirmed ** Affects: linux (Ubuntu Impish) Importance: High Status: Confirmed ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux (Ubuntu Impish) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945938 Title: [impish] Remove the downstream xr-usb-uart driver Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: [Impact] The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS kernel to add support for USB UART chips: Family: USB UART Part Numbers: XR21V1410, XR21V1412, XR21V1414, XR21B1411, XR21B1420, XR21B1422, XR21B1424, XR22801, XR22802, XR22804 [Fix] In 5.13.x, support for these devices was added to the kernel via. following patch series: Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/ There have been long term maintenance challenges with the downstream vendor driver over the period of time (since 4.4.y based Xenial LTS). Now that upstream driver supports most of the above part numbers, let's remove this redundant out-of-tree driver. [Test] The driver was functionally verified to work fine with XR21V1412. The support for other chips with part numbers mentioned above are also supported with the above patch series. [Where problems could occur] Low. The downstream driver was designed to work with specific BIOS configs only defined on an IoT GW project which is locked to use only Xenial ESM and Bionic LTS kernels, there is a low chance of regression on the Impish series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930754] Re: e1000e extremly slow
5.10.0-1049.51 works for me too, many thanks indeed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1930754 Title: e1000e extremly slow Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] e1000e on TGP PCH encounters a network speed issue that rx speed is below 1MB/s [Fix] Intel provides 2 patches to fix this https://patchwork.ozlabs.org/project/intel-wired-lan/list/?series=263466 [Test] Verified by our Dell and Lenovo platforms and the bug reporter. [Where problems could occur] The fix only applies to e1000e with TGP PCH, and add a flag "E1000_FFLT_DBG_DONT_GATE_WAKE_DMA_CLK". The impact should be minimized and should not lead to other regressions. = We have dell latitude 5420 & 5520 laptops with onboard intel ethernet controller. Problem is that the ethernet port is extremely slow. about 100kbyte/s download throughput while on a gigabit connection. Upload seems to work just fine. Also when I pxe boot the system it's also painfully slow. But here comes the funny part. When I attach a usb memory stick the throughput of the networkcontroller is as expected. I've used latest ubuntu 20.04.2 kernel 5.8.0-55 I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem Turns out this problem is not showing up when I manually install the 5.8.18 kernel. Also when I create my own iso with the help of Cubic and install the 5.8.18 kernel in it the pxe boot is working as expected with high throughput system: Dell latitude 5420 + 5520 nic: Ethernet Connection (13) I219-LM ubuntu 20.04.2 module: e1000e Please assist. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945938] Re: [impish] Remove the downstream xr-usb-uart driver
** Description changed: [Impact] - The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS kernel + The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS kernel to add support for USB UART chips: Family: USB UART Part Numbers: - XR21V1410, XR21V1412, XR21V1414, - XR21B1411, XR21B1420, XR21B1422, - XR21B1424, XR22801, XR22802, - XR22804 + XR21V1410, XR21V1412, XR21V1414, + XR21B1411, XR21B1420, XR21B1422, + XR21B1424, XR22801, XR22802, + XR22804 [Fix] In 5.13.x, support for these devices was added to the kernel via. following patch series: Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/ There have been long term maintenance challenges with the downstream vendor driver - over the period of time (since 4.4.y based Xenial LTS). Now that upstream driver + over the period of time (since 4.4.y based Xenial LTS). Now that upstream driver supports most of the above part numbers, let's remove this redundant out-of-tree driver. [Test] The driver was functionally verified to work fine with XR21V1412. The support for - other chips with part numbers mentioned above are also supported with the above + other chips with part numbers mentioned above are also supported with the above patch series. [Where problems could occur] - Low. The downstream driver was designed to work with specific BIOS configs only + The downstream driver was designed to work with specific BIOS configs only defined on an IoT GW project which is locked to use only Xenial ESM and Bionic LTS kernels, there is a low chance of regression on the Impish series. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945938 Title: [impish] Remove the downstream xr-usb-uart driver Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: [Impact] The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS kernel to add support for USB UART chips: Family: USB UART Part Numbers: XR21V1410, XR21V1412, XR21V1414, XR21B1411, XR21B1420, XR21B1422, XR21B1424, XR22801, XR22802, XR22804 [Fix] In 5.13.x, support for these devices was added to the kernel via. following patch series: Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/ There have been long term maintenance challenges with the downstream vendor driver over the period of time (since 4.4.y based Xenial LTS). Now that upstream driver supports most of the above part numbers, let's remove this redundant out-of-tree driver. [Test] The driver was functionally verified to work fine with XR21V1412. The support for other chips with part numbers mentioned above are also supported with the above patch series. [Where problems could occur] The downstream driver was designed to work with specific BIOS configs only defined on an IoT GW project which is locked to use only Xenial ESM and Bionic LTS kernels, there is a low chance of regression on the Impish series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945749] Re: Xorg freeze
Thanks but I can't see any relevant errors in those logs. Next please follow: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1945749 Title: [nvidia] Xorg freeze Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: System randomly freezes, no clue how to reproduce it. Multiple people have the same issue. Dell Precision 5550 running Ubuntu 20.04.3 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:41:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.11.0-36-generic, x86_64: installed nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:097e] Subsystem: Dell TU117GLM [Quadro T1000 Mobile] [1028:097e] InstallationDate: Installed on 2021-08-27 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=42e96b11-9efb-45e0-ace2-85fe35b2047b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnPrecision5550:pvr:sku097E:rvnDellInc.:rn0V6K79:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5550 dmi.product.sku: 097E dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.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~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/nvidia-graphics-drivers-470/+bug/1945749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945749] Re: [nvidia] Xorg freeze
** Summary changed: - Xorg freeze + [nvidia] Xorg freeze -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1945749 Title: [nvidia] Xorg freeze Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: System randomly freezes, no clue how to reproduce it. Multiple people have the same issue. Dell Precision 5550 running Ubuntu 20.04.3 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:41:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.11.0-36-generic, x86_64: installed nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:097e] Subsystem: Dell TU117GLM [Quadro T1000 Mobile] [1028:097e] InstallationDate: Installed on 2021-08-27 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=42e96b11-9efb-45e0-ace2-85fe35b2047b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnPrecision5550:pvr:sku097E:rvnDellInc.:rn0V6K79:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5550 dmi.product.sku: 097E dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.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~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/nvidia-graphics-drivers-470/+bug/1945749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945938] Re: [impish] Remove the downstream xr-usb-uart driver
** Description changed: [Impact] The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS kernel to add support for USB UART chips: Family: USB UART Part Numbers: XR21V1410, XR21V1412, XR21V1414, XR21B1411, XR21B1420, XR21B1422, XR21B1424, XR22801, XR22802, XR22804 [Fix] In 5.13.x, support for these devices was added to the kernel via. following patch series: Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/ There have been long term maintenance challenges with the downstream vendor driver over the period of time (since 4.4.y based Xenial LTS). Now that upstream driver supports most of the above part numbers, let's remove this redundant out-of-tree driver. [Test] The driver was functionally verified to work fine with XR21V1412. The support for other chips with part numbers mentioned above are also supported with the above patch series. [Where problems could occur] The downstream driver was designed to work with specific BIOS configs only defined on an IoT GW project which is locked to use only Xenial ESM and Bionic LTS kernels, there is a low chance of regression on the Impish series. + + [This is a tracking bug, please do not triage] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945938 Title: [impish] Remove the downstream xr-usb-uart driver Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: [Impact] The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS kernel to add support for USB UART chips: Family: USB UART Part Numbers: XR21V1410, XR21V1412, XR21V1414, XR21B1411, XR21B1420, XR21B1422, XR21B1424, XR22801, XR22802, XR22804 [Fix] In 5.13.x, support for these devices was added to the kernel via. following patch series: Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/ There have been long term maintenance challenges with the downstream vendor driver over the period of time (since 4.4.y based Xenial LTS). Now that upstream driver supports most of the above part numbers, let's remove this redundant out-of-tree driver. [Test] The driver was functionally verified to work fine with XR21V1412. The support for other chips with part numbers mentioned above are also supported with the above patch series. [Where problems could occur] The downstream driver was designed to work with specific BIOS configs only defined on an IoT GW project which is locked to use only Xenial ESM and Bionic LTS kernels, there is a low chance of regression on the Impish series. [This is a tracking bug, please do not triage] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945887] Re: org.bluez.obex.service contains unresolved '@libexecdir@'
Yes the bug seems to exist on impish in: /usr/share/dbus-1/services/org.bluez.obex.service Looks like it might originate from this 2013 patch: patches/0001-Allow-using-obexd-without-systemd-in-the-user- sessio.patch Perhaps it is meant to be @pkglibexecdir@ ? -- 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/1945887 Title: org.bluez.obex.service contains unresolved '@libexecdir@' Status in bluez package in Ubuntu: Confirmed Bug description: After upgrading a machine from Ubuntu Bionic to Ubuntu Focal yesterday, the following error message showed up in the syslog: Oct 2 23:14:52 desktop01 dbus-daemon[1764]: [session uid=0 pid=1760] Activated service 'org.bluez.obex' failed: Failed to execute program org.bluez.obex: No such file or directory Upon inspection, this was due to the fact that the service definition contained the line 'Exec=@libexecdir@/obexd' which could not be resolved (this placeholder is supposedly to be replaced at build time). Replacing '@libexecdir@' with '/usr/lib/bluetooth' resolved this (together with 'systemctl --user daemon-reload; systemctl --user restart obex'). Note that this problem should be part of *all* current versions of the bluez[-obexd] package, regardless of the used architecture (including Focal, Impish): % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.60-0ubuntu2_amd64.deb [...] Länge: 217906 (213K) [application/x-debian-package] Wird in »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert. [...] 2021-10-03 07:40:36 (1,53 MB/s) - »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert [217906/217906] % dpkg-deb -R bluez-obexd_5.60-0ubuntu2_amd64.deb impish % grep '@' impish/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.53-0ubuntu3.3_arm64.deb [...] Länge: 160832 (157K) [application/x-debian-package] Wird in »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert. [...] 2021-10-03 07:43:13 (2,06 MB/s) - »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert [160832/160832] % dpkg-deb -R bluez-obexd_5.53-0ubuntu3.3_arm64.deb focal % grep '@' focal/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % # lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 # apt-cache policy bluez-obexd bluez-obexd: [...] 5.53-0ubuntu3.3 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1945887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945887] Re: org.bluez.obex.service contains unresolved '@libexecdir@'
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/1945887 Title: org.bluez.obex.service contains unresolved '@libexecdir@' Status in bluez package in Ubuntu: Confirmed Bug description: After upgrading a machine from Ubuntu Bionic to Ubuntu Focal yesterday, the following error message showed up in the syslog: Oct 2 23:14:52 desktop01 dbus-daemon[1764]: [session uid=0 pid=1760] Activated service 'org.bluez.obex' failed: Failed to execute program org.bluez.obex: No such file or directory Upon inspection, this was due to the fact that the service definition contained the line 'Exec=@libexecdir@/obexd' which could not be resolved (this placeholder is supposedly to be replaced at build time). Replacing '@libexecdir@' with '/usr/lib/bluetooth' resolved this (together with 'systemctl --user daemon-reload; systemctl --user restart obex'). Note that this problem should be part of *all* current versions of the bluez[-obexd] package, regardless of the used architecture (including Focal, Impish): % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.60-0ubuntu2_amd64.deb [...] Länge: 217906 (213K) [application/x-debian-package] Wird in »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert. [...] 2021-10-03 07:40:36 (1,53 MB/s) - »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert [217906/217906] % dpkg-deb -R bluez-obexd_5.60-0ubuntu2_amd64.deb impish % grep '@' impish/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.53-0ubuntu3.3_arm64.deb [...] Länge: 160832 (157K) [application/x-debian-package] Wird in »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert. [...] 2021-10-03 07:43:13 (2,06 MB/s) - »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert [160832/160832] % dpkg-deb -R bluez-obexd_5.53-0ubuntu3.3_arm64.deb focal % grep '@' focal/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % # lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 # apt-cache policy bluez-obexd bluez-obexd: [...] 5.53-0ubuntu3.3 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1945887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945805] [NEW] Screen Won't Come Back After Blank Screen
You have been subscribed to a public bug: The Power Saving option was set for the screen to go blank after five minutes. After the update, the screen will now not come back on when the mouse or keyboard is utilized. The computer appears to be still operational as it's registering keystrokes, but it must be restarted in order for the screen to come back up. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22 Uname: Linux 5.11.0-1019-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:22:59 2021 DistUpgraded: 2021-08-11 11:39:13,437 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: ImageMediaBuild: 20201022 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 248a:8367 Maxxter Telink Wireless Receiver Bus 001 Device 003: ID 0424:2504 Microchip Technology, Inc. (formerly SMSC) Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1680x1050M@60 video=HDMI-A-2:1680x1050M@60 smsc95xx.macaddr=DC:A6:32:B4:5C:3E vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-08-11 (50 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image hirsute raspi-image ubuntu wayland-session -- Screen Won't Come Back After Blank Screen https://bugs.launchpad.net/bugs/1945805 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi 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 1945887] Re: org.bluez.obex.service contains unresolved '@libexecdir@'
** Changed in: bluez (Ubuntu) Importance: Undecided => Medium ** Changed in: bluez (Ubuntu) Status: Confirmed => Triaged -- 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/1945887 Title: org.bluez.obex.service contains unresolved '@libexecdir@' Status in bluez package in Ubuntu: Triaged Bug description: After upgrading a machine from Ubuntu Bionic to Ubuntu Focal yesterday, the following error message showed up in the syslog: Oct 2 23:14:52 desktop01 dbus-daemon[1764]: [session uid=0 pid=1760] Activated service 'org.bluez.obex' failed: Failed to execute program org.bluez.obex: No such file or directory Upon inspection, this was due to the fact that the service definition contained the line 'Exec=@libexecdir@/obexd' which could not be resolved (this placeholder is supposedly to be replaced at build time). Replacing '@libexecdir@' with '/usr/lib/bluetooth' resolved this (together with 'systemctl --user daemon-reload; systemctl --user restart obex'). Note that this problem should be part of *all* current versions of the bluez[-obexd] package, regardless of the used architecture (including Focal, Impish): % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.60-0ubuntu2_amd64.deb [...] Länge: 217906 (213K) [application/x-debian-package] Wird in »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert. [...] 2021-10-03 07:40:36 (1,53 MB/s) - »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert [217906/217906] % dpkg-deb -R bluez-obexd_5.60-0ubuntu2_amd64.deb impish % grep '@' impish/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.53-0ubuntu3.3_arm64.deb [...] Länge: 160832 (157K) [application/x-debian-package] Wird in »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert. [...] 2021-10-03 07:43:13 (2,06 MB/s) - »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert [160832/160832] % dpkg-deb -R bluez-obexd_5.53-0ubuntu3.3_arm64.deb focal % grep '@' focal/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % # lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 # apt-cache policy bluez-obexd bluez-obexd: [...] 5.53-0ubuntu3.3 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1945887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945805] Re: Screen Won't Come Back After Blank Screen
*** This bug is a duplicate of bug 1944397 *** https://bugs.launchpad.net/bugs/1944397 It appears the vc4 kernel driver (Broadcom GPU) is crashing a lot in HDMI functions. We should treat this as a duplicate of bug 1944397 until proven otherwise. ** Package changed: xorg (Ubuntu) => linux-raspi (Ubuntu) ** This bug has been marked a duplicate of bug 1944397 HDMI does not display anything with Impish RPi desktop image -- 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/1945805 Title: Screen Won't Come Back After Blank Screen Status in linux-raspi package in Ubuntu: New Bug description: The Power Saving option was set for the screen to go blank after five minutes. After the update, the screen will now not come back on when the mouse or keyboard is utilized. The computer appears to be still operational as it's registering keystrokes, but it must be restarted in order for the screen to come back up. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22 Uname: Linux 5.11.0-1019-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:22:59 2021 DistUpgraded: 2021-08-11 11:39:13,437 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: ImageMediaBuild: 20201022 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 248a:8367 Maxxter Telink Wireless Receiver Bus 001 Device 003: ID 0424:2504 Microchip Technology, Inc. (formerly SMSC) Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1680x1050M@60 video=HDMI-A-2:1680x1050M@60 smsc95xx.macaddr=DC:A6:32:B4:5C:3E vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-08-11 (50 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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-raspi/+bug/1945805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945749] Re: [nvidia] Xorg freeze
Hi Daniel, https://errors.ubuntu.com/oops/b0a77a90-23bd-11ec-b3fd-fa163e6cac46 https://errors.ubuntu.com/oops/fff3b31a-2023-11ec-b459-fa163ee63de6 https://errors.ubuntu.com/oops/9d40eec4-1d63-11ec-b3e2-fa163ee63de6 https://errors.ubuntu.com/oops/ba6ac63a-1211-11ec-b21c-fa163ee63de6 https://errors.ubuntu.com/oops/f746ff84-1094-11ec-b1eb-fa163ee63de6 https://errors.ubuntu.com/oops/520722ce-0734-11ec-ae9b-fa163e6cac46 These are the error reports sent from my system. If there is anything else I can do, I'm all ears. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1945749 Title: [nvidia] Xorg freeze Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: System randomly freezes, no clue how to reproduce it. Multiple people have the same issue. Dell Precision 5550 running Ubuntu 20.04.3 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:41:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.11.0-36-generic, x86_64: installed nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:097e] Subsystem: Dell TU117GLM [Quadro T1000 Mobile] [1028:097e] InstallationDate: Installed on 2021-08-27 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=42e96b11-9efb-45e0-ace2-85fe35b2047b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnPrecision5550:pvr:sku097E:rvnDellInc.:rn0V6K79:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5550 dmi.product.sku: 097E dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.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~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/nvidia-graphics-drivers-470/+bug/1945749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp