[Kernel-packages] [Bug 1888992] 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 1888992 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/1888992 Title: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones Status in linux package in Ubuntu: Incomplete Bug description: I boot my system without any sound devices plugged into any jacks; checking Gnome settings Sound, Output Device is "Dummy Output" (no other options available in drop-down list). I plug in headphones into the front jack and play some audio, but do not hear any sound from the headphones; checking Gnome settings Sound, the Output Device is still "Dummy Output", with no other options available. This is a regression from previous behaviour, when plugging in headphones into the front jack would automatically enable/switch to the front jack and its associated controller "Family 17h (Models 00h- 0fh) HD Audio Controller" (this is the motherboard's onboard audio hardware). I can currently workaround this each time I plug in the headphones by installing and running pavucontrol, and under Configuration selecting "Analogue Stereo Output (unplugged) (unavailable)" - this option becomes "Analogue Stereo Output" after I select it. This seems to be a regression in pulseaudio after an upgrade from from 1:13.99.1-1ubuntu3.3 to 1:13.99.1-1ubuntu3.5. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chinf 1741 F pulseaudio /dev/snd/pcmC1D0p: chinf 1741 F...m pulseaudio /dev/snd/controlC0: chinf 1741 F pulseaudio /dev/snd/timer: chinf 1741 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 12:46:52 2020 InstallationDate: Installed on 2018-10-29 (635 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chinf 1741 F pulseaudio /dev/snd/controlC0: chinf 1741 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-04 (83 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
> i2c-hid.polling_mode=1 to the kernel boot parameters to make the touchpad work. you mean that I can just flash 5.9 kernel and then add to grub this line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video.use_native_backlight=1 i2c-hid.polling_mode=1" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
Noctis, not yet. I just pinged the upstream devs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). WORKAROUND: I installed the 4.15 kernel, so at the moment I can work with this. Higher than 4.15 the second monitor doesn't work. Tested until 5.8 and without good results. Just with 4.15. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion:
[Kernel-packages] [Bug 1888992] Re: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones
** Package changed: alsa-driver (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/1888992 Title: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones Status in linux package in Ubuntu: New Bug description: I boot my system without any sound devices plugged into any jacks; checking Gnome settings Sound, Output Device is "Dummy Output" (no other options available in drop-down list). I plug in headphones into the front jack and play some audio, but do not hear any sound from the headphones; checking Gnome settings Sound, the Output Device is still "Dummy Output", with no other options available. This is a regression from previous behaviour, when plugging in headphones into the front jack would automatically enable/switch to the front jack and its associated controller "Family 17h (Models 00h- 0fh) HD Audio Controller" (this is the motherboard's onboard audio hardware). I can currently workaround this each time I plug in the headphones by installing and running pavucontrol, and under Configuration selecting "Analogue Stereo Output (unplugged) (unavailable)" - this option becomes "Analogue Stereo Output" after I select it. This seems to be a regression in pulseaudio after an upgrade from from 1:13.99.1-1ubuntu3.3 to 1:13.99.1-1ubuntu3.5. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chinf 1741 F pulseaudio /dev/snd/pcmC1D0p: chinf 1741 F...m pulseaudio /dev/snd/controlC0: chinf 1741 F pulseaudio /dev/snd/timer: chinf 1741 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 12:46:52 2020 InstallationDate: Installed on 2018-10-29 (635 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chinf 1741 F pulseaudio /dev/snd/controlC0: chinf 1741 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-04 (83 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891100] Re: hp notebook 15-da0001nk sound mute led not working
Oh, does the laptop have both mute led and mic-mute led? Is mic-mute LED working? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891100 Title: hp notebook 15-da0001nk sound mute led not working Status in linux package in Ubuntu: Incomplete Bug description: I install Ubuntu 20.04 with kernel 5.4 on my new HP Notebook - 15-da0001nk , the system run flawlessly except the Sound Mute LED on the F6 key. I try many solution after a humble search on the net but without success. The output of pactl list sinks/lscpi is attached. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: djalel 2167 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: HP HP Laptop 15-da0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=a4fd6950-d770-40a6-9863-f35146cfaf67 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/02/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd06/02/2020:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.47:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 4BY81EA#BH4 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891100] Re: hp notebook 15-da0001nk sound mute led not working
Does mute led work now? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891100 Title: hp notebook 15-da0001nk sound mute led not working Status in linux package in Ubuntu: Incomplete Bug description: I install Ubuntu 20.04 with kernel 5.4 on my new HP Notebook - 15-da0001nk , the system run flawlessly except the Sound Mute LED on the F6 key. I try many solution after a humble search on the net but without success. The output of pactl list sinks/lscpi is attached. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: djalel 2167 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: HP HP Laptop 15-da0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=a4fd6950-d770-40a6-9863-f35146cfaf67 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/02/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd06/02/2020:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.47:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 4BY81EA#BH4 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888992] [NEW] [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones
You have been subscribed to a public bug: I boot my system without any sound devices plugged into any jacks; checking Gnome settings Sound, Output Device is "Dummy Output" (no other options available in drop-down list). I plug in headphones into the front jack and play some audio, but do not hear any sound from the headphones; checking Gnome settings Sound, the Output Device is still "Dummy Output", with no other options available. This is a regression from previous behaviour, when plugging in headphones into the front jack would automatically enable/switch to the front jack and its associated controller "Family 17h (Models 00h-0fh) HD Audio Controller" (this is the motherboard's onboard audio hardware). I can currently workaround this each time I plug in the headphones by installing and running pavucontrol, and under Configuration selecting "Analogue Stereo Output (unplugged) (unavailable)" - this option becomes "Analogue Stereo Output" after I select it. This seems to be a regression in pulseaudio after an upgrade from from 1:13.99.1-1ubuntu3.3 to 1:13.99.1-1ubuntu3.5. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chinf 1741 F pulseaudio /dev/snd/pcmC1D0p: chinf 1741 F...m pulseaudio /dev/snd/controlC0: chinf 1741 F pulseaudio /dev/snd/timer: chinf 1741 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 12:46:52 2020 InstallationDate: Installed on 2018-10-29 (635 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chinf 1741 F pulseaudio /dev/snd/controlC0: chinf 1741 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-04 (83 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones https://bugs.launchpad.net/bugs/1888992 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 1891579] Re: Security enhanced Ubuntu distribution that would maintain system integrity.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891579 Title: Security enhanced Ubuntu distribution that would maintain system integrity. Status in linux package in Ubuntu: Expired Bug description: A user account allows a user to do restricted tasks. An admin account gives a user full control of the system. If the admin has full control of the system, the admin could cause unintentional damage. The admin should not be allowed to damage the system. A user could be tricked into revealing their admin password. There could be a new user called System, that would not be accessible to the Admin. The System account would have no login. The System account would protect the system from being damaged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891579/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
I tried that connect two monitors on wd19tb. can't trigger the issue on my side. Can you confirm is the issue be triggered after the fresh installation!? Thanks your effort -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 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 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895449] Re: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome
if the issue still can be triggered, please also dump the dmesg... i noticed one alarm. "No beacon heard and the time event is over already" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895449 Title: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome Status in linux package in Ubuntu: In Progress Bug description: A few issues: 1)With Intel(R) Wireless-AC 9560, under kernel 5.4 for Ubuntu 20.04.1, the system sometimes gets disconnected with the network and I get the following error in syslog: iwlwifi: BIOS contains WGDS but no WRDS It is unclear if this is the cause of the problem, but this is likely related to kernel. 2) Watching HTML5 videos on Chrome with Nvidia GPU (440 driver) will sometimes cause xorg freeze. The exact cause is unknown. (Mouse, control all freeze for 5-10 seconds) 3) After Wake up from sleep got the following error on screen sof-audio-pci error: no reply expected, received 0x0 iwlwifi: BIOS contains WGDS but no WRDS 4) After wake up from a long sleep session, sometimes chrome will not render web page correctly or even freeze. It is unclear if its a Chrome problem, or a Nvidia problem, or a Kernel Problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gao1931 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 09:14:36 2020 InstallationDate: Installed on 2020-08-25 (19 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron 7591 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=421f18c3-a8c8-4cf4-9b7b-5a7442595b1b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0JKGD4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd06/30/2020:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-09-07T23:43:13.736867 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895449] Re: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome
@Mike, could you help to try the mainline kernel(5.9)!? https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895449 Title: Internet disconnected unexpectly + Xorg freeze while watching html5 video in Chrome Status in linux package in Ubuntu: In Progress Bug description: A few issues: 1)With Intel(R) Wireless-AC 9560, under kernel 5.4 for Ubuntu 20.04.1, the system sometimes gets disconnected with the network and I get the following error in syslog: iwlwifi: BIOS contains WGDS but no WRDS It is unclear if this is the cause of the problem, but this is likely related to kernel. 2) Watching HTML5 videos on Chrome with Nvidia GPU (440 driver) will sometimes cause xorg freeze. The exact cause is unknown. (Mouse, control all freeze for 5-10 seconds) 3) After Wake up from sleep got the following error on screen sof-audio-pci error: no reply expected, received 0x0 iwlwifi: BIOS contains WGDS but no WRDS 4) After wake up from a long sleep session, sometimes chrome will not render web page correctly or even freeze. It is unclear if its a Chrome problem, or a Nvidia problem, or a Kernel Problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gao1931 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 09:14:36 2020 InstallationDate: Installed on 2020-08-25 (19 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron 7591 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=421f18c3-a8c8-4cf4-9b7b-5a7442595b1b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0JKGD4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd06/30/2020:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-09-07T23:43:13.736867 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
Happened out of the box from Dell, switching to 5.6 OEM didn't help. I think part of the key here is the double monitor in the dock with the laptop screen closed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 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 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899508] Re: alsa/hda/realtek - The front Mic on a HP machine doesn't work
** Tags added: oem-priority originate-from-1896461 stella ** Changed in: oem-priority Status: New => In Progress ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1899508 Title: alsa/hda/realtek - The front Mic on a HP machine doesn't work Status in OEM Priority Project: In Progress Status in linux-oem-5.6 package in Ubuntu: New Bug description: This fix is only for oem-5.6 kernel, other kernels will merge this patch with stable update. Our oem project needs this patch to be merged ASAP. [Impact] When using a HP machine, after plugging the headset at front jack, there is no any input device shows. [Fix] The codec of the HP ZCentrol is alc671 and it needs to override the pin configuration to enable the headset mic. This patch is going to be merged by upstream, now backport it to oem-5.6 kernel. [Test Case] Boot the system, plug a headset and check the gnome-control-center, the Mic is active in the UI, and record the sound, it could record the sound. [Regression Risk] Low, this patch is to add a platform specific quirk to override pin configuration and already tested in this HP machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1899508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885757] Re: seccomp_bpf fails on powerpc
** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885757 Title: seccomp_bpf fails on powerpc Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [Impact] seccomp_bpf test fails on powerpc and ends up being disabled on some series, or causing engineers to waste their time verifying the same failures are the only ones we see every kernel release. [Test case] Run the test and notice there are no more failures. [Regression potential] We may break the test on different architectures. That doesn't break users, though, as the changes are only on tests. It has been tested at least on ppc64el and amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1885757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894407] Re: linux-tools: can perf be linked against libbfd, maybe statically?
As it turns out Ubuntu *did* used to link perf statically: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/783660 So I really don't understand the objection here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894407 Title: linux-tools: can perf be linked against libbfd, maybe statically? Status in linux package in Ubuntu: Won't Fix Bug description: The perf tool has an optional dependency on libbfd. Per Debian policy, and due to some situation involving parallel installations of this library, no packages should link dynamically against libbfd. In the past, bugs have been filed to link perf statically against libbfd in bug 783660 (from 2011) and then to just not link against it at all in bug 1748922 (from 2018) and bug 1828234 (from 2019). The argument was made that perf does not need this dependency, as perf can use libiberty as an alternative to demangle C++ names. However, that is not the only thing perf is using libbfd for: the other is to implement an inlined version of addr2line. This was part of an important patchset from 2013 that strove to improve the performance of perf. In my case, I ran my program for all of 30 seconds, generating a 163M large trace, and have been waiting almost an hour for the events to process... and it is only a third of the way done; what I see it doing is spawning, over and over and over again, addr2line, which it wouldn't do if linked against libbfd. https://lore.kernel.org/patchwork/patch/413455/ Is it possible to link perf statically against libbfd, in order to let it use the in-process implementation of addr2line? That is the solution that I've understood for other packages, such as oprofile in bug 426614 and bug 588033. Doing a quick grep of the code of perf for HAVE_LIBBFD_SUPPORT, it seems like bpf disassembly support is also dependent on libbfd (and so while it is great that Ubuntu's build of perf has been compiled against libbpf, it seems like that functionality is being hampered by the lack of linking libbfd). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899527] Re: bluetooth remains off even the switch is on from settings
*** This bug is a duplicate of bug 1857787 *** https://bugs.launchpad.net/bugs/1857787 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1857787, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1857787 Bluetooth cannot be turned on once turned off -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1899527 Title: bluetooth remains off even the switch is on from settings Status in bluez package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: sometimes my bluetooth is just turned of and not able to turn it on even if I click the button in settings->bluetooth ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 23:45:43 2020 InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera Bus 001 Device 002: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 7, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 7, If 0, Class=Video, Driver=uvcvideo, 480M MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=05f0328a-3146-4fe8-94ad-3fee253ebdaf ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN58WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN58WW:bd06/18/2020:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO hciconfig: syslog: Oct 12 23:38:39 pankaj-pc NetworkManager[860]: [1602526119.6673] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-bluetooth.so) Oct 12 23:38:51 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 12 23:39:28 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 12 23:42:00 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1899527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899527] Re: bluetooth remains off even the switch is on from settings
*** This bug is a duplicate of bug 1857787 *** https://bugs.launchpad.net/bugs/1857787 ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1899527 Title: bluetooth remains off even the switch is on from settings Status in bluez package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: sometimes my bluetooth is just turned of and not able to turn it on even if I click the button in settings->bluetooth ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 23:45:43 2020 InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera Bus 001 Device 002: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 7, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 7, If 0, Class=Video, Driver=uvcvideo, 480M MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=05f0328a-3146-4fe8-94ad-3fee253ebdaf ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN58WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN58WW:bd06/18/2020:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO hciconfig: syslog: Oct 12 23:38:39 pankaj-pc NetworkManager[860]: [1602526119.6673] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-bluetooth.so) Oct 12 23:38:51 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 12 23:39:28 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 12 23:42:00 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1899527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
yours is the same as mine. Did you trigger the issue after the fresh installation? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 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 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894407] Re: linux-tools: can perf be linked against libbfd, maybe statically?
I too would very much like to see this fixed. As it stands `perf report` is unusable on large binaries on Ubuntu. Seth, I think Jay's arguments are compelling. Do you agree? If I prepared a patch, would that be helpful? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894407 Title: linux-tools: can perf be linked against libbfd, maybe statically? Status in linux package in Ubuntu: Won't Fix Bug description: The perf tool has an optional dependency on libbfd. Per Debian policy, and due to some situation involving parallel installations of this library, no packages should link dynamically against libbfd. In the past, bugs have been filed to link perf statically against libbfd in bug 783660 (from 2011) and then to just not link against it at all in bug 1748922 (from 2018) and bug 1828234 (from 2019). The argument was made that perf does not need this dependency, as perf can use libiberty as an alternative to demangle C++ names. However, that is not the only thing perf is using libbfd for: the other is to implement an inlined version of addr2line. This was part of an important patchset from 2013 that strove to improve the performance of perf. In my case, I ran my program for all of 30 seconds, generating a 163M large trace, and have been waiting almost an hour for the events to process... and it is only a third of the way done; what I see it doing is spawning, over and over and over again, addr2line, which it wouldn't do if linked against libbfd. https://lore.kernel.org/patchwork/patch/413455/ Is it possible to link perf statically against libbfd, in order to let it use the in-process implementation of addr2line? That is the solution that I've understood for other packages, such as oprofile in bug 426614 and bug 588033. Doing a quick grep of the code of perf for HAVE_LIBBFD_SUPPORT, it seems like bpf disassembly support is also dependent on libbfd (and so while it is great that Ubuntu's build of perf has been compiled against libbpf, it seems like that functionality is being hampered by the lack of linking libbfd). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893655] Re: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list
** Tags added: groovy -- 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/1893655 Title: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: When I switch on my Sony WH-1000XM3 headphones, they reconnect to my laptop at Bluetooth level, but don't appear as an audio device. I have to remove them in the Ubuntu Bluetooth settings, and then re-pair them, every time. This is rather inconvenient. This started happening after upgrading to Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Uname: Linux 5.6.0-1021-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Aug 31 14:48:53 2020 InstallationDate: Installed on 2020-07-14 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20U9CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET19W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9CTO1WW dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:AC:65:6D:04:AB ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1274806 acl:246 sco:0 events:180845 errors:0 TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1893655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899397] Re: [Lenovo IdeaPad 3 14IIL05] No fan detected
Not sure but maybe 60-80 degrees... I personally would only be concerned about the fan being off if the temperature was in that range. If an operating system doesn't support fan control then the fan will always be on maximum. So it being off suggests it is supported. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899397 Title: [Lenovo IdeaPad 3 14IIL05] No fan detected Status in linux package in Ubuntu: Invalid Bug description: No fan detected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 11 23:33:39 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3fb5] InstallationDate: Installed on 2020-09-24 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:5a08 IMC Networks Integrated Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=98af080a-ee1a-4302-b335-e6462548d523 ro i842.nopnp=1 pci=nocrs quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WD:pvrIdeaPad314IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrIdeaPad314IIL05: dmi.product.family: IdeaPad 3 14IIL05 dmi.product.name: 81WD dmi.product.sku: LENOVO_MT_81WD_BU_idea_FM_IdeaPad 3 14IIL05 dmi.product.version: IdeaPad 3 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
I started to have same problem when upgraded today to Ubuntu 20.04 LTS on my docking station with VGA port. HP EliteBook 930p laptop Samsung SyncMaster 2043" Port: VGA "lspci" output: 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) It worked on 18.04.1 Occasionaly I managed to get it work with "xrandr" setting mode to 1680x1050. VGA-1 connected primary 1680x1050+0+0 (normal left inverted right x axis y axis) 459mm x 296mm 1680x1050 59.88*+ 1280x1024 75.0260.02 1280x960 60.00 1152x864 75.00 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 640x480 75.0072.8166.6759.94 720x400 70.08 1680x1050_56.00 55.96 But when I reboot, again it does not work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this
[Kernel-packages] [Bug 1899527] Re: bluetooth remains off even the switch is on from settings
** Package changed: ubuntu => bluez (Ubuntu) -- 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/1899527 Title: bluetooth remains off even the switch is on from settings Status in bluez package in Ubuntu: New Bug description: sometimes my bluetooth is just turned of and not able to turn it on even if I click the button in settings->bluetooth ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 23:45:43 2020 InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera Bus 001 Device 002: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 7, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 7, If 0, Class=Video, Driver=uvcvideo, 480M MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=05f0328a-3146-4fe8-94ad-3fee253ebdaf ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN58WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN58WW:bd06/18/2020:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO hciconfig: syslog: Oct 12 23:38:39 pankaj-pc NetworkManager[860]: [1602526119.6673] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-bluetooth.so) Oct 12 23:38:51 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 12 23:39:28 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 12 23:42:00 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1899527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899527] [NEW] bluetooth remains off even the switch is on from settings
You have been subscribed to a public bug: sometimes my bluetooth is just turned of and not able to turn it on even if I click the button in settings->bluetooth ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 12 23:45:43 2020 InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera Bus 001 Device 002: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 7, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 7, If 0, Class=Video, Driver=uvcvideo, 480M MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=05f0328a-3146-4fe8-94ad-3fee253ebdaf ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN58WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN58WW:bd06/18/2020:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO hciconfig: syslog: Oct 12 23:38:39 pankaj-pc NetworkManager[860]: [1602526119.6673] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-bluetooth.so) Oct 12 23:38:51 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 12 23:39:28 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. Oct 12 23:42:00 pankaj-pc systemd[1]: Condition check resulted in Bluetooth service being skipped. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- bluetooth remains off even the switch is on from settings https://bugs.launchpad.net/bugs/1899527 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez 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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Ok, all these devices have intel wireless and use btintel together with btusb. And i am also pretty sure it has something to do with the firmware not loading. Also this bug has been reported on April the 9th this year and i don't see anyone working on this. And we already have a point release. Why is this not getting any attention? At least give us a status update. Many people work at home now and use bluetooth headphones for Slack or Skype etc. We bought company laptops with 20.04 LTS preinstalled and we all had to downgrade them to make them usable for working at home. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899397] Re: [Lenovo IdeaPad 3 14IIL05] No fan detected
At what temperature should the fan be turned on? I tested with s-tui in stress mode and reached 52 degrees without noticing that the fan turned on. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899397 Title: [Lenovo IdeaPad 3 14IIL05] No fan detected Status in linux package in Ubuntu: Invalid Bug description: No fan detected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 11 23:33:39 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3fb5] InstallationDate: Installed on 2020-09-24 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:5a08 IMC Networks Integrated Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=98af080a-ee1a-4302-b335-e6462548d523 ro i842.nopnp=1 pci=nocrs quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WD:pvrIdeaPad314IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrIdeaPad314IIL05: dmi.product.family: IdeaPad 3 14IIL05 dmi.product.name: 81WD dmi.product.sku: LENOVO_MT_81WD_BU_idea_FM_IdeaPad 3 14IIL05 dmi.product.version: IdeaPad 3 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899515] Re: ZFS Modules Missing
yep it works on 20.10 on kernel 5.8.0-18-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899515 Title: ZFS Modules Missing Status in linux package in Ubuntu: Incomplete Bug description: Hello! tried to manually update to kernel 5.9 using these packages: https://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/amd64/ but dkms did not load the zfs modules so i got stuck with an angry message in busybox, no zfs modules loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899519] Re: booting armhf kernel under qemu results in relocations out of range, and thus no modules are loaded
-M virt,highmem=off still shows relocation 28 out of range upon trying to load any kernel modules. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899519 Title: booting armhf kernel under qemu results in relocations out of range, and thus no modules are loaded Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: qemu-system-arm -M virt -m 4096 -smp 2,sockets=2,cores=1,threads=1 -drive file=./groovy-server-cloudimg-armhf.img,if=virtio -kernel ./vmlinuz-5.8.0-21-generic-lpae -initrd ./initrd.img-5.8.0-21-generic- lpae -append 'root=LABEL=cloudimg-rootfs break=bottom' -nographic [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 5.8.0-21-generic-lpae (buildd@bos02-arm64-041) (gcc (Ubuntu 10.2.0-11ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #22-Ubuntu SMP Fri Oct 2 12:30:15 UTC 2020 (Ubuntu 5.8.0-21.22-generic-lpae 5.8.13) [0.00] CPU: ARMv7 Processor [412fc0f1] revision 1 (ARMv7), cr=30c5387d Starting version 246.6-1ubuntu1 [ 16.753306] gpio_keys: section 4 reloc 29 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf00f23c -> 0xc10a90ec) Begin: Loading essential drivers ... [ 22.799409] linear: section 4 reloc 43 sym '__stack_chk_fail': relocation 28 out of range (0xbf0195e8 -> 0xc10a1dd8) [ 23.000670] multipath: section 4 reloc 31 sym '__stack_chk_fail': relocation 28 out of range (0xbf021268 -> 0xc10a1dd8) [ 23.227437] raid0: section 4 reloc 53 sym '__stack_chk_fail': relocation 28 out of range (0xbf02a548 -> 0xc10a1dd8) [ 23.460764] raid1: section 4 reloc 18 sym '_cond_resched': relocation 28 out of range (0xbf035390 -> 0xc10a3b4c) [ 28.311563] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 31.866657] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.632259] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.852163] raid10: section 4 reloc 21 sym '__stack_chk_fail': relocation 28 out of range (0xbf00b404 -> 0xc10a1dd8) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 41.265330] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) (initramfs) cat /proc/modules (initramfs) modprobe virtio_blk [ 121.814904] virtio_blk: section 4 reloc 3 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf003050 -> 0xc10a90ec) (initramfs) cat /proc/modules (initramfs) Are we miss-building the kernel and/or modules? Or am I miss-launching the VM? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899515] Re: ZFS Modules Missing
Tried that in a Focal VM, got: Loading new zfs-0.8.3 DKMS files... Building for 5.4.0-48-generic 5.9.0-050900daily20201012-generic [...] Building initial module for 5.9.0-050900daily20201012-generic ERROR (dkms apport): kernel package linux-headers-5.9.0-050900daily20201012-generic is not supported Error! Bad return status for module build on kernel: 5.9.0-050900daily20201012-generic (x86_64) Consult /var/lib/dkms/zfs/0.8.3/build/make.log for more information The log file only contains: DKMS make.log for zfs-0.8.3 for kernel 5.9.0-050900daily20201012-generic (x86_64) Mon Oct 12 17:35:06 UTC 2020 make: *** No targets specified and no makefile found. Stop. Trying the zfs packages updated to 0.8.4-1ubuntu11 led to the same result: Building initial module for 5.9.0-050900daily20201012-generic configure: error: *** None of the expected "global page state" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-0.8.4-1ubuntu11 *** Compatible Kernels: 2.6.32 - 5.6 Both versions worked with kernel 5.4.0-48. It claims the compatible kernels range is 2.6.32 - 5.6, but I think this is a red herring, since Groovy kernel is 5.8, correct? Thanks, Guilherme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899515 Title: ZFS Modules Missing Status in linux package in Ubuntu: Incomplete Bug description: Hello! tried to manually update to kernel 5.9 using these packages: https://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/amd64/ but dkms did not load the zfs modules so i got stuck with an angry message in busybox, no zfs modules loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899519] Re: booting armhf kernel under qemu results in relocations out of range, and thus no modules are loaded
I wonder if this is because -M virt defaults to highmem=on, I will try again with highmem=off -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899519 Title: booting armhf kernel under qemu results in relocations out of range, and thus no modules are loaded Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: qemu-system-arm -M virt -m 4096 -smp 2,sockets=2,cores=1,threads=1 -drive file=./groovy-server-cloudimg-armhf.img,if=virtio -kernel ./vmlinuz-5.8.0-21-generic-lpae -initrd ./initrd.img-5.8.0-21-generic- lpae -append 'root=LABEL=cloudimg-rootfs break=bottom' -nographic [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 5.8.0-21-generic-lpae (buildd@bos02-arm64-041) (gcc (Ubuntu 10.2.0-11ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #22-Ubuntu SMP Fri Oct 2 12:30:15 UTC 2020 (Ubuntu 5.8.0-21.22-generic-lpae 5.8.13) [0.00] CPU: ARMv7 Processor [412fc0f1] revision 1 (ARMv7), cr=30c5387d Starting version 246.6-1ubuntu1 [ 16.753306] gpio_keys: section 4 reloc 29 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf00f23c -> 0xc10a90ec) Begin: Loading essential drivers ... [ 22.799409] linear: section 4 reloc 43 sym '__stack_chk_fail': relocation 28 out of range (0xbf0195e8 -> 0xc10a1dd8) [ 23.000670] multipath: section 4 reloc 31 sym '__stack_chk_fail': relocation 28 out of range (0xbf021268 -> 0xc10a1dd8) [ 23.227437] raid0: section 4 reloc 53 sym '__stack_chk_fail': relocation 28 out of range (0xbf02a548 -> 0xc10a1dd8) [ 23.460764] raid1: section 4 reloc 18 sym '_cond_resched': relocation 28 out of range (0xbf035390 -> 0xc10a3b4c) [ 28.311563] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 31.866657] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.632259] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.852163] raid10: section 4 reloc 21 sym '__stack_chk_fail': relocation 28 out of range (0xbf00b404 -> 0xc10a1dd8) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 41.265330] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) (initramfs) cat /proc/modules (initramfs) modprobe virtio_blk [ 121.814904] virtio_blk: section 4 reloc 3 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf003050 -> 0xc10a90ec) (initramfs) cat /proc/modules (initramfs) Are we miss-building the kernel and/or modules? Or am I miss-launching the VM? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899522] [NEW] package libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2 failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.8
Public bug reported: During sudo apt-get upgrade, there was an error while this package was installing. On restarting my computer, the resolution was set to 800*600 and my gpu (nvidia 1060 6gb) wasn't recognized. Uninstalling the driver and reverting to the nouveu drivers fixed the resolution issue and reinstalling the nvidia-450 drivers via software & updates allowed for everything to go back to normal. Steps to reproduce: On a machine with an nvidia 1060 6gb, run sudo apt- get update followed by sudo apt-get upgrade, this should result in an error during dpkg. Restart the computer to see the driver issue with display resolution and gpu not labelled correctly. Steps to resolve for the time being: Uninstall and reinstall nvidia-450 via software & updates, restart computer. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 12 18:12:58 2020 Dependencies: DuplicateSignature: package:libnvidia-common-450-server:450.51.06-0ubuntu0.20.04.2 Unpacking libnvidia-common-450-server (450.80.02-0ubuntu0.20.04.3) over (450.51.06-0ubuntu0.20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-OfgM3I/33-libnvidia-common-450-server_450.80.02-0ubuntu0.20.04.3_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2 ErrorMessage: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2 InstallationDate: Installed on 2020-10-01 (11 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-450-server Title: package libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2 failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-450-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-conflict -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450-server in Ubuntu. https://bugs.launchpad.net/bugs/1899522 Title: package libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2 failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia- application-profiles-450.80.02-key-documentation', which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2 Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Bug description: During sudo apt-get upgrade, there was an error while this package was installing. On restarting my computer, the resolution was set to 800*600 and my gpu (nvidia 1060 6gb) wasn't recognized. Uninstalling the driver and reverting to the nouveu drivers fixed the resolution issue and reinstalling the nvidia-450 drivers via software & updates allowed for everything to go back to normal. Steps to reproduce: On a machine with an nvidia 1060 6gb, run sudo apt-get update followed by sudo apt-get upgrade, this should result in an error during dpkg. Restart the computer to see the driver issue with display resolution and gpu not labelled correctly. Steps to resolve for the time being: Uninstall and reinstall nvidia-450 via software & updates, restart computer. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 12 18:12:58 2020 Dependencies: DuplicateSignature: package:libnvidia-common-450-server:450.51.06-0ubuntu0.20.04.2 Unpacking libnvidia-common-450-server (450.80.02-0ubuntu0.20.04.3) over (450.51.06-0ubuntu0.20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-OfgM3I/33-libnvidia-common-450-server_450.80.02-0ubuntu0.20.04.3_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2
[Kernel-packages] [Bug 1899519] 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 1899519 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/1899519 Title: booting armhf kernel under qemu results in relocations out of range, and thus no modules are loaded Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: qemu-system-arm -M virt -m 4096 -smp 2,sockets=2,cores=1,threads=1 -drive file=./groovy-server-cloudimg-armhf.img,if=virtio -kernel ./vmlinuz-5.8.0-21-generic-lpae -initrd ./initrd.img-5.8.0-21-generic- lpae -append 'root=LABEL=cloudimg-rootfs break=bottom' -nographic [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 5.8.0-21-generic-lpae (buildd@bos02-arm64-041) (gcc (Ubuntu 10.2.0-11ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #22-Ubuntu SMP Fri Oct 2 12:30:15 UTC 2020 (Ubuntu 5.8.0-21.22-generic-lpae 5.8.13) [0.00] CPU: ARMv7 Processor [412fc0f1] revision 1 (ARMv7), cr=30c5387d Starting version 246.6-1ubuntu1 [ 16.753306] gpio_keys: section 4 reloc 29 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf00f23c -> 0xc10a90ec) Begin: Loading essential drivers ... [ 22.799409] linear: section 4 reloc 43 sym '__stack_chk_fail': relocation 28 out of range (0xbf0195e8 -> 0xc10a1dd8) [ 23.000670] multipath: section 4 reloc 31 sym '__stack_chk_fail': relocation 28 out of range (0xbf021268 -> 0xc10a1dd8) [ 23.227437] raid0: section 4 reloc 53 sym '__stack_chk_fail': relocation 28 out of range (0xbf02a548 -> 0xc10a1dd8) [ 23.460764] raid1: section 4 reloc 18 sym '_cond_resched': relocation 28 out of range (0xbf035390 -> 0xc10a3b4c) [ 28.311563] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 31.866657] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.632259] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.852163] raid10: section 4 reloc 21 sym '__stack_chk_fail': relocation 28 out of range (0xbf00b404 -> 0xc10a1dd8) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 41.265330] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) (initramfs) cat /proc/modules (initramfs) modprobe virtio_blk [ 121.814904] virtio_blk: section 4 reloc 3 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf003050 -> 0xc10a90ec) (initramfs) cat /proc/modules (initramfs) Are we miss-building the kernel and/or modules? Or am I miss-launching the VM? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899519] [NEW] booting armhf kernel under qemu results in relocations out of range, and thus no modules are loaded
Public bug reported: qemu-system-arm -M virt -m 4096 -smp 2,sockets=2,cores=1,threads=1 -drive file=./groovy-server-cloudimg-armhf.img,if=virtio -kernel ./vmlinuz-5.8.0-21-generic-lpae -initrd ./initrd.img-5.8.0-21-generic- lpae -append 'root=LABEL=cloudimg-rootfs break=bottom' -nographic [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 5.8.0-21-generic-lpae (buildd@bos02-arm64-041) (gcc (Ubuntu 10.2.0-11ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #22-Ubuntu SMP Fri Oct 2 12:30:15 UTC 2020 (Ubuntu 5.8.0-21.22-generic-lpae 5.8.13) [0.00] CPU: ARMv7 Processor [412fc0f1] revision 1 (ARMv7), cr=30c5387d Starting version 246.6-1ubuntu1 [ 16.753306] gpio_keys: section 4 reloc 29 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf00f23c -> 0xc10a90ec) Begin: Loading essential drivers ... [ 22.799409] linear: section 4 reloc 43 sym '__stack_chk_fail': relocation 28 out of range (0xbf0195e8 -> 0xc10a1dd8) [ 23.000670] multipath: section 4 reloc 31 sym '__stack_chk_fail': relocation 28 out of range (0xbf021268 -> 0xc10a1dd8) [ 23.227437] raid0: section 4 reloc 53 sym '__stack_chk_fail': relocation 28 out of range (0xbf02a548 -> 0xc10a1dd8) [ 23.460764] raid1: section 4 reloc 18 sym '_cond_resched': relocation 28 out of range (0xbf035390 -> 0xc10a3b4c) [ 28.311563] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 31.866657] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.632259] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.852163] raid10: section 4 reloc 21 sym '__stack_chk_fail': relocation 28 out of range (0xbf00b404 -> 0xc10a1dd8) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 41.265330] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) (initramfs) cat /proc/modules (initramfs) modprobe virtio_blk [ 121.814904] virtio_blk: section 4 reloc 3 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf003050 -> 0xc10a90ec) (initramfs) cat /proc/modules (initramfs) Are we miss-building the kernel and/or modules? Or am I miss-launching the VM? ** Affects: ubuntu-release-notes Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: armhf groovy ** Tags added: armhf groovy ** Also affects: ubuntu-release-notes Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Milestone: None => ubuntu-20.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899519 Title: booting armhf kernel under qemu results in relocations out of range, and thus no modules are loaded Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: qemu-system-arm -M virt -m 4096 -smp 2,sockets=2,cores=1,threads=1 -drive file=./groovy-server-cloudimg-armhf.img,if=virtio -kernel ./vmlinuz-5.8.0-21-generic-lpae -initrd ./initrd.img-5.8.0-21-generic- lpae -append 'root=LABEL=cloudimg-rootfs break=bottom' -nographic [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 5.8.0-21-generic-lpae (buildd@bos02-arm64-041) (gcc (Ubuntu 10.2.0-11ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #22-Ubuntu SMP Fri Oct 2 12:30:15 UTC 2020 (Ubuntu 5.8.0-21.22-generic-lpae 5.8.13) [0.00] CPU: ARMv7 Processor [412fc0f1] revision 1 (ARMv7), cr=30c5387d Starting version 246.6-1ubuntu1 [ 16.753306] gpio_keys: section 4 reloc 29 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf00f23c -> 0xc10a90ec) Begin: Loading essential drivers ... [ 22.799409] linear: section 4 reloc 43 sym '__stack_chk_fail': relocation 28 out of range (0xbf0195e8 -> 0xc10a1dd8) [ 23.000670] multipath: section 4 reloc 31 sym '__stack_chk_fail': relocation 28 out of range (0xbf021268 -> 0xc10a1dd8) [ 23.227437] raid0: section 4 reloc 53 sym '__stack_chk_fail': relocation 28 out of range (0xbf02a548 -> 0xc10a1dd8) [ 23.460764] raid1: section 4 reloc 18 sym '_cond_resched': relocation 28 out of range (0xbf035390 -> 0xc10a3b4c) [ 28.311563] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 31.866657] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.632259] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.852163] raid10: section 4 reloc 21 sym
[Kernel-packages] [Bug 1893817] Re: aws: enable PCI write-combine for arm64
This bug was fixed in the package linux-aws - 5.8.0-1008.8 --- linux-aws (5.8.0-1008.8) groovy; urgency=medium * groovy/linux-aws: 5.8.0-1008.8 -proposed tracker (LP: #1899092) * aws: enable PCI write-combine for arm64 (LP: #1893817) - SAUCE: arm64: Enable PCI write-combine resources under sysfs * Miscellaneous Ubuntu changes - CONFIG_UBUNTU_HOST=m - [Packaging] [aws] remove python3-venv dependency [ Ubuntu: 5.8.0-22.23 ] * groovy/linux: 5.8.0-22.23 -proposed tracker (LP: #1899099) * Packaging resync (LP: #1786013) - update dkms package versions * oops in nvkm_udevice_info() [nouveau] (LP: #1898130) - drm/nouveau/device: return error for unknown chipsets * python3-venv is gone (LP: #1896801) - SAUCE: doc: remove python3-venv dependency * *-tools-common packages descriptions have typo "PGKVER" (LP: #1898903) - [Packaging] Fix typo in -tools template s/PGKVER/PKGVER/ * Enable brightness control on HP DreamColor panel (LP: #1898865) - SAUCE: drm/i915/dpcd_bl: Skip testing control capability with force DPCD quirk - SAUCE: drm/dp: HP DreamColor panel brigntness fix * Groovy update: v5.8.14 upstream stable release (LP: #1898853) - io_uring: always delete double poll wait entry on match - btrfs: fix filesystem corruption after a device replace - mmc: sdhci: Workaround broken command queuing on Intel GLK based IRBIS models - USB: gadget: f_ncm: Fix NDP16 datagram validation - Revert "usbip: Implement a match function to fix usbip" - usbcore/driver: Fix specific driver selection - usbcore/driver: Fix incorrect downcast - usbcore/driver: Accommodate usbip - gpio: siox: explicitly support only threaded irqs - gpio: mockup: fix resource leak in error path - gpio: tc35894: fix up tc35894 interrupt configuration - gpio: amd-fch: correct logic of GPIO_LINE_DIRECTION - clk: samsung: Keep top BPLL mux on Exynos542x enabled - clk: socfpga: stratix10: fix the divider for the emac_ptp_free_clk - scsi: iscsi: iscsi_tcp: Avoid holding spinlock while calling getpeername() - i2c: i801: Exclude device from suspend direct complete optimization - Input: i8042 - add nopnp quirk for Acer Aspire 5 A515 - iio: adc: qcom-spmi-adc5: fix driver name - ftrace: Move RCU is watching check after recursion check - tracing: Fix trace_find_next_entry() accounting of temp buffer size - memstick: Skip allocating card when removing host - drm/amdgpu: restore proper ref count in amdgpu_display_crtc_set_config - xen/events: don't use chip_data for legacy IRQs - clocksource/drivers/timer-gx6605s: Fixup counter reload - vboxsf: Fix the check for the old binary mount-arguments struct - mt76: mt7915: use ieee80211_free_txskb to free tx skbs - libbpf: Remove arch-specific include path in Makefile - drivers/net/wan/hdlc_fr: Add needed_headroom for PVC devices - Revert "wlcore: Adding suppoprt for IGTK key in wlcore driver" - drm/sun4i: mixer: Extend regmap max_register - hv_netvsc: Cache the current data path to avoid duplicate call and message - net: dec: de2104x: Increase receive ring size for Tulip - rndis_host: increase sleep time in the query-response loop - nvme-pci: disable the write zeros command for Intel 600P/P3100 - nvme-core: get/put ctrl and transport module in nvme_dev_open/release() - fuse: fix the ->direct_IO() treatment of iov_iter - drivers/net/wan/lapbether: Make skb->protocol consistent with the header - drivers/net/wan/hdlc: Set skb->protocol before transmitting - mac80211: Fix radiotap header channel flag for 6GHz band - mac80211: do not allow bigger VHT MPDUs than the hardware supports - tracing: Make the space reserved for the pid wider - tools/io_uring: fix compile breakage - io_uring: mark statx/files_update/epoll_ctl as non-SQPOLL - cpuidle: psci: Fix suspicious RCU usage - spi: fsl-espi: Only process interrupts for expected events - net: dsa: felix: fix some key offsets for IP4_TCP_UDP VCAP IS2 entries - nvme-pci: fix NULL req in completion handler - nvme-fc: fail new connections to a deleted host or remote port - scripts/kallsyms: skip ppc compiler stub *.long_branch.* / *.plt_branch.* - gpio: sprd: Clear interrupt when setting the type as edge - phy: ti: am654: Fix a leak in serdes_am654_probe() - pinctrl: mvebu: Fix i2c sda definition for 98DX3236 - nfs: Fix security label length not being reset - NFSv4.2: fix client's attribute cache management for copy_file_range - pNFS/flexfiles: Ensure we initialise the mirror bsizes correctly on read - clk: tegra: Always program PLL_E when enabled - clk: tegra: Fix missing prototype for tegra210_clk_register_emc() - dmaengine: dmatest: Prevent to run on misconfigured channel - clk: samsung: exynos4: mark 'chipid' clock as CLK_IGNORE_UNUSED - scsi: target: Fix lun
[Kernel-packages] [Bug 1898865] Re: Enable brightness control on HP DreamColor panel
This bug was fixed in the package linux - 5.8.0-22.23 --- linux (5.8.0-22.23) groovy; urgency=medium * groovy/linux: 5.8.0-22.23 -proposed tracker (LP: #1899099) * Packaging resync (LP: #1786013) - update dkms package versions * oops in nvkm_udevice_info() [nouveau] (LP: #1898130) - drm/nouveau/device: return error for unknown chipsets * python3-venv is gone (LP: #1896801) - SAUCE: doc: remove python3-venv dependency * *-tools-common packages descriptions have typo "PGKVER" (LP: #1898903) - [Packaging] Fix typo in -tools template s/PGKVER/PKGVER/ * Enable brightness control on HP DreamColor panel (LP: #1898865) - SAUCE: drm/i915/dpcd_bl: Skip testing control capability with force DPCD quirk - SAUCE: drm/dp: HP DreamColor panel brigntness fix * Groovy update: v5.8.14 upstream stable release (LP: #1898853) - io_uring: always delete double poll wait entry on match - btrfs: fix filesystem corruption after a device replace - mmc: sdhci: Workaround broken command queuing on Intel GLK based IRBIS models - USB: gadget: f_ncm: Fix NDP16 datagram validation - Revert "usbip: Implement a match function to fix usbip" - usbcore/driver: Fix specific driver selection - usbcore/driver: Fix incorrect downcast - usbcore/driver: Accommodate usbip - gpio: siox: explicitly support only threaded irqs - gpio: mockup: fix resource leak in error path - gpio: tc35894: fix up tc35894 interrupt configuration - gpio: amd-fch: correct logic of GPIO_LINE_DIRECTION - clk: samsung: Keep top BPLL mux on Exynos542x enabled - clk: socfpga: stratix10: fix the divider for the emac_ptp_free_clk - scsi: iscsi: iscsi_tcp: Avoid holding spinlock while calling getpeername() - i2c: i801: Exclude device from suspend direct complete optimization - Input: i8042 - add nopnp quirk for Acer Aspire 5 A515 - iio: adc: qcom-spmi-adc5: fix driver name - ftrace: Move RCU is watching check after recursion check - tracing: Fix trace_find_next_entry() accounting of temp buffer size - memstick: Skip allocating card when removing host - drm/amdgpu: restore proper ref count in amdgpu_display_crtc_set_config - xen/events: don't use chip_data for legacy IRQs - clocksource/drivers/timer-gx6605s: Fixup counter reload - vboxsf: Fix the check for the old binary mount-arguments struct - mt76: mt7915: use ieee80211_free_txskb to free tx skbs - libbpf: Remove arch-specific include path in Makefile - drivers/net/wan/hdlc_fr: Add needed_headroom for PVC devices - Revert "wlcore: Adding suppoprt for IGTK key in wlcore driver" - drm/sun4i: mixer: Extend regmap max_register - hv_netvsc: Cache the current data path to avoid duplicate call and message - net: dec: de2104x: Increase receive ring size for Tulip - rndis_host: increase sleep time in the query-response loop - nvme-pci: disable the write zeros command for Intel 600P/P3100 - nvme-core: get/put ctrl and transport module in nvme_dev_open/release() - fuse: fix the ->direct_IO() treatment of iov_iter - drivers/net/wan/lapbether: Make skb->protocol consistent with the header - drivers/net/wan/hdlc: Set skb->protocol before transmitting - mac80211: Fix radiotap header channel flag for 6GHz band - mac80211: do not allow bigger VHT MPDUs than the hardware supports - tracing: Make the space reserved for the pid wider - tools/io_uring: fix compile breakage - io_uring: mark statx/files_update/epoll_ctl as non-SQPOLL - cpuidle: psci: Fix suspicious RCU usage - spi: fsl-espi: Only process interrupts for expected events - net: dsa: felix: fix some key offsets for IP4_TCP_UDP VCAP IS2 entries - nvme-pci: fix NULL req in completion handler - nvme-fc: fail new connections to a deleted host or remote port - scripts/kallsyms: skip ppc compiler stub *.long_branch.* / *.plt_branch.* - gpio: sprd: Clear interrupt when setting the type as edge - phy: ti: am654: Fix a leak in serdes_am654_probe() - pinctrl: mvebu: Fix i2c sda definition for 98DX3236 - nfs: Fix security label length not being reset - NFSv4.2: fix client's attribute cache management for copy_file_range - pNFS/flexfiles: Ensure we initialise the mirror bsizes correctly on read - clk: tegra: Always program PLL_E when enabled - clk: tegra: Fix missing prototype for tegra210_clk_register_emc() - dmaengine: dmatest: Prevent to run on misconfigured channel - clk: samsung: exynos4: mark 'chipid' clock as CLK_IGNORE_UNUSED - scsi: target: Fix lun lookup for TARGET_SCF_LOOKUP_LUN_FROM_TAG case - iommu/exynos: add missing put_device() call in exynos_iommu_of_xlate() - gpio: pca953x: Fix uninitialized pending variable - gpio/aspeed-sgpio: enable access to all 80 input & output sgpios - gpio/aspeed-sgpio: don't enable all interrupts by default - gpio: aspeed: fix
[Kernel-packages] [Bug 1898853] Re: Groovy update: v5.8.14 upstream stable release
This bug was fixed in the package linux - 5.8.0-22.23 --- linux (5.8.0-22.23) groovy; urgency=medium * groovy/linux: 5.8.0-22.23 -proposed tracker (LP: #1899099) * Packaging resync (LP: #1786013) - update dkms package versions * oops in nvkm_udevice_info() [nouveau] (LP: #1898130) - drm/nouveau/device: return error for unknown chipsets * python3-venv is gone (LP: #1896801) - SAUCE: doc: remove python3-venv dependency * *-tools-common packages descriptions have typo "PGKVER" (LP: #1898903) - [Packaging] Fix typo in -tools template s/PGKVER/PKGVER/ * Enable brightness control on HP DreamColor panel (LP: #1898865) - SAUCE: drm/i915/dpcd_bl: Skip testing control capability with force DPCD quirk - SAUCE: drm/dp: HP DreamColor panel brigntness fix * Groovy update: v5.8.14 upstream stable release (LP: #1898853) - io_uring: always delete double poll wait entry on match - btrfs: fix filesystem corruption after a device replace - mmc: sdhci: Workaround broken command queuing on Intel GLK based IRBIS models - USB: gadget: f_ncm: Fix NDP16 datagram validation - Revert "usbip: Implement a match function to fix usbip" - usbcore/driver: Fix specific driver selection - usbcore/driver: Fix incorrect downcast - usbcore/driver: Accommodate usbip - gpio: siox: explicitly support only threaded irqs - gpio: mockup: fix resource leak in error path - gpio: tc35894: fix up tc35894 interrupt configuration - gpio: amd-fch: correct logic of GPIO_LINE_DIRECTION - clk: samsung: Keep top BPLL mux on Exynos542x enabled - clk: socfpga: stratix10: fix the divider for the emac_ptp_free_clk - scsi: iscsi: iscsi_tcp: Avoid holding spinlock while calling getpeername() - i2c: i801: Exclude device from suspend direct complete optimization - Input: i8042 - add nopnp quirk for Acer Aspire 5 A515 - iio: adc: qcom-spmi-adc5: fix driver name - ftrace: Move RCU is watching check after recursion check - tracing: Fix trace_find_next_entry() accounting of temp buffer size - memstick: Skip allocating card when removing host - drm/amdgpu: restore proper ref count in amdgpu_display_crtc_set_config - xen/events: don't use chip_data for legacy IRQs - clocksource/drivers/timer-gx6605s: Fixup counter reload - vboxsf: Fix the check for the old binary mount-arguments struct - mt76: mt7915: use ieee80211_free_txskb to free tx skbs - libbpf: Remove arch-specific include path in Makefile - drivers/net/wan/hdlc_fr: Add needed_headroom for PVC devices - Revert "wlcore: Adding suppoprt for IGTK key in wlcore driver" - drm/sun4i: mixer: Extend regmap max_register - hv_netvsc: Cache the current data path to avoid duplicate call and message - net: dec: de2104x: Increase receive ring size for Tulip - rndis_host: increase sleep time in the query-response loop - nvme-pci: disable the write zeros command for Intel 600P/P3100 - nvme-core: get/put ctrl and transport module in nvme_dev_open/release() - fuse: fix the ->direct_IO() treatment of iov_iter - drivers/net/wan/lapbether: Make skb->protocol consistent with the header - drivers/net/wan/hdlc: Set skb->protocol before transmitting - mac80211: Fix radiotap header channel flag for 6GHz band - mac80211: do not allow bigger VHT MPDUs than the hardware supports - tracing: Make the space reserved for the pid wider - tools/io_uring: fix compile breakage - io_uring: mark statx/files_update/epoll_ctl as non-SQPOLL - cpuidle: psci: Fix suspicious RCU usage - spi: fsl-espi: Only process interrupts for expected events - net: dsa: felix: fix some key offsets for IP4_TCP_UDP VCAP IS2 entries - nvme-pci: fix NULL req in completion handler - nvme-fc: fail new connections to a deleted host or remote port - scripts/kallsyms: skip ppc compiler stub *.long_branch.* / *.plt_branch.* - gpio: sprd: Clear interrupt when setting the type as edge - phy: ti: am654: Fix a leak in serdes_am654_probe() - pinctrl: mvebu: Fix i2c sda definition for 98DX3236 - nfs: Fix security label length not being reset - NFSv4.2: fix client's attribute cache management for copy_file_range - pNFS/flexfiles: Ensure we initialise the mirror bsizes correctly on read - clk: tegra: Always program PLL_E when enabled - clk: tegra: Fix missing prototype for tegra210_clk_register_emc() - dmaengine: dmatest: Prevent to run on misconfigured channel - clk: samsung: exynos4: mark 'chipid' clock as CLK_IGNORE_UNUSED - scsi: target: Fix lun lookup for TARGET_SCF_LOOKUP_LUN_FROM_TAG case - iommu/exynos: add missing put_device() call in exynos_iommu_of_xlate() - gpio: pca953x: Fix uninitialized pending variable - gpio/aspeed-sgpio: enable access to all 80 input & output sgpios - gpio/aspeed-sgpio: don't enable all interrupts by default - gpio: aspeed: fix
[Kernel-packages] [Bug 1898130] Re: oops in nvkm_udevice_info() [nouveau]
This bug was fixed in the package linux - 5.8.0-22.23 --- linux (5.8.0-22.23) groovy; urgency=medium * groovy/linux: 5.8.0-22.23 -proposed tracker (LP: #1899099) * Packaging resync (LP: #1786013) - update dkms package versions * oops in nvkm_udevice_info() [nouveau] (LP: #1898130) - drm/nouveau/device: return error for unknown chipsets * python3-venv is gone (LP: #1896801) - SAUCE: doc: remove python3-venv dependency * *-tools-common packages descriptions have typo "PGKVER" (LP: #1898903) - [Packaging] Fix typo in -tools template s/PGKVER/PKGVER/ * Enable brightness control on HP DreamColor panel (LP: #1898865) - SAUCE: drm/i915/dpcd_bl: Skip testing control capability with force DPCD quirk - SAUCE: drm/dp: HP DreamColor panel brigntness fix * Groovy update: v5.8.14 upstream stable release (LP: #1898853) - io_uring: always delete double poll wait entry on match - btrfs: fix filesystem corruption after a device replace - mmc: sdhci: Workaround broken command queuing on Intel GLK based IRBIS models - USB: gadget: f_ncm: Fix NDP16 datagram validation - Revert "usbip: Implement a match function to fix usbip" - usbcore/driver: Fix specific driver selection - usbcore/driver: Fix incorrect downcast - usbcore/driver: Accommodate usbip - gpio: siox: explicitly support only threaded irqs - gpio: mockup: fix resource leak in error path - gpio: tc35894: fix up tc35894 interrupt configuration - gpio: amd-fch: correct logic of GPIO_LINE_DIRECTION - clk: samsung: Keep top BPLL mux on Exynos542x enabled - clk: socfpga: stratix10: fix the divider for the emac_ptp_free_clk - scsi: iscsi: iscsi_tcp: Avoid holding spinlock while calling getpeername() - i2c: i801: Exclude device from suspend direct complete optimization - Input: i8042 - add nopnp quirk for Acer Aspire 5 A515 - iio: adc: qcom-spmi-adc5: fix driver name - ftrace: Move RCU is watching check after recursion check - tracing: Fix trace_find_next_entry() accounting of temp buffer size - memstick: Skip allocating card when removing host - drm/amdgpu: restore proper ref count in amdgpu_display_crtc_set_config - xen/events: don't use chip_data for legacy IRQs - clocksource/drivers/timer-gx6605s: Fixup counter reload - vboxsf: Fix the check for the old binary mount-arguments struct - mt76: mt7915: use ieee80211_free_txskb to free tx skbs - libbpf: Remove arch-specific include path in Makefile - drivers/net/wan/hdlc_fr: Add needed_headroom for PVC devices - Revert "wlcore: Adding suppoprt for IGTK key in wlcore driver" - drm/sun4i: mixer: Extend regmap max_register - hv_netvsc: Cache the current data path to avoid duplicate call and message - net: dec: de2104x: Increase receive ring size for Tulip - rndis_host: increase sleep time in the query-response loop - nvme-pci: disable the write zeros command for Intel 600P/P3100 - nvme-core: get/put ctrl and transport module in nvme_dev_open/release() - fuse: fix the ->direct_IO() treatment of iov_iter - drivers/net/wan/lapbether: Make skb->protocol consistent with the header - drivers/net/wan/hdlc: Set skb->protocol before transmitting - mac80211: Fix radiotap header channel flag for 6GHz band - mac80211: do not allow bigger VHT MPDUs than the hardware supports - tracing: Make the space reserved for the pid wider - tools/io_uring: fix compile breakage - io_uring: mark statx/files_update/epoll_ctl as non-SQPOLL - cpuidle: psci: Fix suspicious RCU usage - spi: fsl-espi: Only process interrupts for expected events - net: dsa: felix: fix some key offsets for IP4_TCP_UDP VCAP IS2 entries - nvme-pci: fix NULL req in completion handler - nvme-fc: fail new connections to a deleted host or remote port - scripts/kallsyms: skip ppc compiler stub *.long_branch.* / *.plt_branch.* - gpio: sprd: Clear interrupt when setting the type as edge - phy: ti: am654: Fix a leak in serdes_am654_probe() - pinctrl: mvebu: Fix i2c sda definition for 98DX3236 - nfs: Fix security label length not being reset - NFSv4.2: fix client's attribute cache management for copy_file_range - pNFS/flexfiles: Ensure we initialise the mirror bsizes correctly on read - clk: tegra: Always program PLL_E when enabled - clk: tegra: Fix missing prototype for tegra210_clk_register_emc() - dmaengine: dmatest: Prevent to run on misconfigured channel - clk: samsung: exynos4: mark 'chipid' clock as CLK_IGNORE_UNUSED - scsi: target: Fix lun lookup for TARGET_SCF_LOOKUP_LUN_FROM_TAG case - iommu/exynos: add missing put_device() call in exynos_iommu_of_xlate() - gpio: pca953x: Fix uninitialized pending variable - gpio/aspeed-sgpio: enable access to all 80 input & output sgpios - gpio/aspeed-sgpio: don't enable all interrupts by default - gpio: aspeed: fix
[Kernel-packages] [Bug 1896801] Re: python3-venv is gone
This bug was fixed in the package linux-aws - 5.8.0-1008.8 --- linux-aws (5.8.0-1008.8) groovy; urgency=medium * groovy/linux-aws: 5.8.0-1008.8 -proposed tracker (LP: #1899092) * aws: enable PCI write-combine for arm64 (LP: #1893817) - SAUCE: arm64: Enable PCI write-combine resources under sysfs * Miscellaneous Ubuntu changes - CONFIG_UBUNTU_HOST=m - [Packaging] [aws] remove python3-venv dependency [ Ubuntu: 5.8.0-22.23 ] * groovy/linux: 5.8.0-22.23 -proposed tracker (LP: #1899099) * Packaging resync (LP: #1786013) - update dkms package versions * oops in nvkm_udevice_info() [nouveau] (LP: #1898130) - drm/nouveau/device: return error for unknown chipsets * python3-venv is gone (LP: #1896801) - SAUCE: doc: remove python3-venv dependency * *-tools-common packages descriptions have typo "PGKVER" (LP: #1898903) - [Packaging] Fix typo in -tools template s/PGKVER/PKGVER/ * Enable brightness control on HP DreamColor panel (LP: #1898865) - SAUCE: drm/i915/dpcd_bl: Skip testing control capability with force DPCD quirk - SAUCE: drm/dp: HP DreamColor panel brigntness fix * Groovy update: v5.8.14 upstream stable release (LP: #1898853) - io_uring: always delete double poll wait entry on match - btrfs: fix filesystem corruption after a device replace - mmc: sdhci: Workaround broken command queuing on Intel GLK based IRBIS models - USB: gadget: f_ncm: Fix NDP16 datagram validation - Revert "usbip: Implement a match function to fix usbip" - usbcore/driver: Fix specific driver selection - usbcore/driver: Fix incorrect downcast - usbcore/driver: Accommodate usbip - gpio: siox: explicitly support only threaded irqs - gpio: mockup: fix resource leak in error path - gpio: tc35894: fix up tc35894 interrupt configuration - gpio: amd-fch: correct logic of GPIO_LINE_DIRECTION - clk: samsung: Keep top BPLL mux on Exynos542x enabled - clk: socfpga: stratix10: fix the divider for the emac_ptp_free_clk - scsi: iscsi: iscsi_tcp: Avoid holding spinlock while calling getpeername() - i2c: i801: Exclude device from suspend direct complete optimization - Input: i8042 - add nopnp quirk for Acer Aspire 5 A515 - iio: adc: qcom-spmi-adc5: fix driver name - ftrace: Move RCU is watching check after recursion check - tracing: Fix trace_find_next_entry() accounting of temp buffer size - memstick: Skip allocating card when removing host - drm/amdgpu: restore proper ref count in amdgpu_display_crtc_set_config - xen/events: don't use chip_data for legacy IRQs - clocksource/drivers/timer-gx6605s: Fixup counter reload - vboxsf: Fix the check for the old binary mount-arguments struct - mt76: mt7915: use ieee80211_free_txskb to free tx skbs - libbpf: Remove arch-specific include path in Makefile - drivers/net/wan/hdlc_fr: Add needed_headroom for PVC devices - Revert "wlcore: Adding suppoprt for IGTK key in wlcore driver" - drm/sun4i: mixer: Extend regmap max_register - hv_netvsc: Cache the current data path to avoid duplicate call and message - net: dec: de2104x: Increase receive ring size for Tulip - rndis_host: increase sleep time in the query-response loop - nvme-pci: disable the write zeros command for Intel 600P/P3100 - nvme-core: get/put ctrl and transport module in nvme_dev_open/release() - fuse: fix the ->direct_IO() treatment of iov_iter - drivers/net/wan/lapbether: Make skb->protocol consistent with the header - drivers/net/wan/hdlc: Set skb->protocol before transmitting - mac80211: Fix radiotap header channel flag for 6GHz band - mac80211: do not allow bigger VHT MPDUs than the hardware supports - tracing: Make the space reserved for the pid wider - tools/io_uring: fix compile breakage - io_uring: mark statx/files_update/epoll_ctl as non-SQPOLL - cpuidle: psci: Fix suspicious RCU usage - spi: fsl-espi: Only process interrupts for expected events - net: dsa: felix: fix some key offsets for IP4_TCP_UDP VCAP IS2 entries - nvme-pci: fix NULL req in completion handler - nvme-fc: fail new connections to a deleted host or remote port - scripts/kallsyms: skip ppc compiler stub *.long_branch.* / *.plt_branch.* - gpio: sprd: Clear interrupt when setting the type as edge - phy: ti: am654: Fix a leak in serdes_am654_probe() - pinctrl: mvebu: Fix i2c sda definition for 98DX3236 - nfs: Fix security label length not being reset - NFSv4.2: fix client's attribute cache management for copy_file_range - pNFS/flexfiles: Ensure we initialise the mirror bsizes correctly on read - clk: tegra: Always program PLL_E when enabled - clk: tegra: Fix missing prototype for tegra210_clk_register_emc() - dmaengine: dmatest: Prevent to run on misconfigured channel - clk: samsung: exynos4: mark 'chipid' clock as CLK_IGNORE_UNUSED - scsi: target: Fix lun
[Kernel-packages] [Bug 1898903] Re: *-tools-common packages descriptions have typo "PGKVER"
This bug was fixed in the package linux - 5.8.0-22.23 --- linux (5.8.0-22.23) groovy; urgency=medium * groovy/linux: 5.8.0-22.23 -proposed tracker (LP: #1899099) * Packaging resync (LP: #1786013) - update dkms package versions * oops in nvkm_udevice_info() [nouveau] (LP: #1898130) - drm/nouveau/device: return error for unknown chipsets * python3-venv is gone (LP: #1896801) - SAUCE: doc: remove python3-venv dependency * *-tools-common packages descriptions have typo "PGKVER" (LP: #1898903) - [Packaging] Fix typo in -tools template s/PGKVER/PKGVER/ * Enable brightness control on HP DreamColor panel (LP: #1898865) - SAUCE: drm/i915/dpcd_bl: Skip testing control capability with force DPCD quirk - SAUCE: drm/dp: HP DreamColor panel brigntness fix * Groovy update: v5.8.14 upstream stable release (LP: #1898853) - io_uring: always delete double poll wait entry on match - btrfs: fix filesystem corruption after a device replace - mmc: sdhci: Workaround broken command queuing on Intel GLK based IRBIS models - USB: gadget: f_ncm: Fix NDP16 datagram validation - Revert "usbip: Implement a match function to fix usbip" - usbcore/driver: Fix specific driver selection - usbcore/driver: Fix incorrect downcast - usbcore/driver: Accommodate usbip - gpio: siox: explicitly support only threaded irqs - gpio: mockup: fix resource leak in error path - gpio: tc35894: fix up tc35894 interrupt configuration - gpio: amd-fch: correct logic of GPIO_LINE_DIRECTION - clk: samsung: Keep top BPLL mux on Exynos542x enabled - clk: socfpga: stratix10: fix the divider for the emac_ptp_free_clk - scsi: iscsi: iscsi_tcp: Avoid holding spinlock while calling getpeername() - i2c: i801: Exclude device from suspend direct complete optimization - Input: i8042 - add nopnp quirk for Acer Aspire 5 A515 - iio: adc: qcom-spmi-adc5: fix driver name - ftrace: Move RCU is watching check after recursion check - tracing: Fix trace_find_next_entry() accounting of temp buffer size - memstick: Skip allocating card when removing host - drm/amdgpu: restore proper ref count in amdgpu_display_crtc_set_config - xen/events: don't use chip_data for legacy IRQs - clocksource/drivers/timer-gx6605s: Fixup counter reload - vboxsf: Fix the check for the old binary mount-arguments struct - mt76: mt7915: use ieee80211_free_txskb to free tx skbs - libbpf: Remove arch-specific include path in Makefile - drivers/net/wan/hdlc_fr: Add needed_headroom for PVC devices - Revert "wlcore: Adding suppoprt for IGTK key in wlcore driver" - drm/sun4i: mixer: Extend regmap max_register - hv_netvsc: Cache the current data path to avoid duplicate call and message - net: dec: de2104x: Increase receive ring size for Tulip - rndis_host: increase sleep time in the query-response loop - nvme-pci: disable the write zeros command for Intel 600P/P3100 - nvme-core: get/put ctrl and transport module in nvme_dev_open/release() - fuse: fix the ->direct_IO() treatment of iov_iter - drivers/net/wan/lapbether: Make skb->protocol consistent with the header - drivers/net/wan/hdlc: Set skb->protocol before transmitting - mac80211: Fix radiotap header channel flag for 6GHz band - mac80211: do not allow bigger VHT MPDUs than the hardware supports - tracing: Make the space reserved for the pid wider - tools/io_uring: fix compile breakage - io_uring: mark statx/files_update/epoll_ctl as non-SQPOLL - cpuidle: psci: Fix suspicious RCU usage - spi: fsl-espi: Only process interrupts for expected events - net: dsa: felix: fix some key offsets for IP4_TCP_UDP VCAP IS2 entries - nvme-pci: fix NULL req in completion handler - nvme-fc: fail new connections to a deleted host or remote port - scripts/kallsyms: skip ppc compiler stub *.long_branch.* / *.plt_branch.* - gpio: sprd: Clear interrupt when setting the type as edge - phy: ti: am654: Fix a leak in serdes_am654_probe() - pinctrl: mvebu: Fix i2c sda definition for 98DX3236 - nfs: Fix security label length not being reset - NFSv4.2: fix client's attribute cache management for copy_file_range - pNFS/flexfiles: Ensure we initialise the mirror bsizes correctly on read - clk: tegra: Always program PLL_E when enabled - clk: tegra: Fix missing prototype for tegra210_clk_register_emc() - dmaengine: dmatest: Prevent to run on misconfigured channel - clk: samsung: exynos4: mark 'chipid' clock as CLK_IGNORE_UNUSED - scsi: target: Fix lun lookup for TARGET_SCF_LOOKUP_LUN_FROM_TAG case - iommu/exynos: add missing put_device() call in exynos_iommu_of_xlate() - gpio: pca953x: Fix uninitialized pending variable - gpio/aspeed-sgpio: enable access to all 80 input & output sgpios - gpio/aspeed-sgpio: don't enable all interrupts by default - gpio: aspeed: fix
[Kernel-packages] [Bug 1896801] Re: python3-venv is gone
This bug was fixed in the package linux - 5.8.0-22.23 --- linux (5.8.0-22.23) groovy; urgency=medium * groovy/linux: 5.8.0-22.23 -proposed tracker (LP: #1899099) * Packaging resync (LP: #1786013) - update dkms package versions * oops in nvkm_udevice_info() [nouveau] (LP: #1898130) - drm/nouveau/device: return error for unknown chipsets * python3-venv is gone (LP: #1896801) - SAUCE: doc: remove python3-venv dependency * *-tools-common packages descriptions have typo "PGKVER" (LP: #1898903) - [Packaging] Fix typo in -tools template s/PGKVER/PKGVER/ * Enable brightness control on HP DreamColor panel (LP: #1898865) - SAUCE: drm/i915/dpcd_bl: Skip testing control capability with force DPCD quirk - SAUCE: drm/dp: HP DreamColor panel brigntness fix * Groovy update: v5.8.14 upstream stable release (LP: #1898853) - io_uring: always delete double poll wait entry on match - btrfs: fix filesystem corruption after a device replace - mmc: sdhci: Workaround broken command queuing on Intel GLK based IRBIS models - USB: gadget: f_ncm: Fix NDP16 datagram validation - Revert "usbip: Implement a match function to fix usbip" - usbcore/driver: Fix specific driver selection - usbcore/driver: Fix incorrect downcast - usbcore/driver: Accommodate usbip - gpio: siox: explicitly support only threaded irqs - gpio: mockup: fix resource leak in error path - gpio: tc35894: fix up tc35894 interrupt configuration - gpio: amd-fch: correct logic of GPIO_LINE_DIRECTION - clk: samsung: Keep top BPLL mux on Exynos542x enabled - clk: socfpga: stratix10: fix the divider for the emac_ptp_free_clk - scsi: iscsi: iscsi_tcp: Avoid holding spinlock while calling getpeername() - i2c: i801: Exclude device from suspend direct complete optimization - Input: i8042 - add nopnp quirk for Acer Aspire 5 A515 - iio: adc: qcom-spmi-adc5: fix driver name - ftrace: Move RCU is watching check after recursion check - tracing: Fix trace_find_next_entry() accounting of temp buffer size - memstick: Skip allocating card when removing host - drm/amdgpu: restore proper ref count in amdgpu_display_crtc_set_config - xen/events: don't use chip_data for legacy IRQs - clocksource/drivers/timer-gx6605s: Fixup counter reload - vboxsf: Fix the check for the old binary mount-arguments struct - mt76: mt7915: use ieee80211_free_txskb to free tx skbs - libbpf: Remove arch-specific include path in Makefile - drivers/net/wan/hdlc_fr: Add needed_headroom for PVC devices - Revert "wlcore: Adding suppoprt for IGTK key in wlcore driver" - drm/sun4i: mixer: Extend regmap max_register - hv_netvsc: Cache the current data path to avoid duplicate call and message - net: dec: de2104x: Increase receive ring size for Tulip - rndis_host: increase sleep time in the query-response loop - nvme-pci: disable the write zeros command for Intel 600P/P3100 - nvme-core: get/put ctrl and transport module in nvme_dev_open/release() - fuse: fix the ->direct_IO() treatment of iov_iter - drivers/net/wan/lapbether: Make skb->protocol consistent with the header - drivers/net/wan/hdlc: Set skb->protocol before transmitting - mac80211: Fix radiotap header channel flag for 6GHz band - mac80211: do not allow bigger VHT MPDUs than the hardware supports - tracing: Make the space reserved for the pid wider - tools/io_uring: fix compile breakage - io_uring: mark statx/files_update/epoll_ctl as non-SQPOLL - cpuidle: psci: Fix suspicious RCU usage - spi: fsl-espi: Only process interrupts for expected events - net: dsa: felix: fix some key offsets for IP4_TCP_UDP VCAP IS2 entries - nvme-pci: fix NULL req in completion handler - nvme-fc: fail new connections to a deleted host or remote port - scripts/kallsyms: skip ppc compiler stub *.long_branch.* / *.plt_branch.* - gpio: sprd: Clear interrupt when setting the type as edge - phy: ti: am654: Fix a leak in serdes_am654_probe() - pinctrl: mvebu: Fix i2c sda definition for 98DX3236 - nfs: Fix security label length not being reset - NFSv4.2: fix client's attribute cache management for copy_file_range - pNFS/flexfiles: Ensure we initialise the mirror bsizes correctly on read - clk: tegra: Always program PLL_E when enabled - clk: tegra: Fix missing prototype for tegra210_clk_register_emc() - dmaengine: dmatest: Prevent to run on misconfigured channel - clk: samsung: exynos4: mark 'chipid' clock as CLK_IGNORE_UNUSED - scsi: target: Fix lun lookup for TARGET_SCF_LOOKUP_LUN_FROM_TAG case - iommu/exynos: add missing put_device() call in exynos_iommu_of_xlate() - gpio: pca953x: Fix uninitialized pending variable - gpio/aspeed-sgpio: enable access to all 80 input & output sgpios - gpio/aspeed-sgpio: don't enable all interrupts by default - gpio: aspeed: fix
[Kernel-packages] [Bug 1899514] Re: Dependency update needed
Running "sudo apt install linux-modules-nvidia-450-generic-hwe-20.04" is a better way of observing the problem -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1899514 Title: Dependency update needed Status in linux-restricted-modules package in Ubuntu: New Bug description: Fresh install of Ubuntu 20.04.1 here. Upon executing "sudo ubuntu-drivers install", I get the following output: linux-modules-nvidia-450-generic-hwe-20.04 : Depends: nvidia-kernel- common-450 (<= 450.66-1) but 450.80.02-0ubuntu0.20.04.2 is to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1899514/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899249] Re: OpenZFS writing stalls, under load
Thanks. I was able to archive, and delete 400GB of data, without problems, earlier on, today, which reduced the "REFER" of my data set, a little - however, it looks like I probably need to focus on archiving, and removing some of the older snapshots, if I want to trim down the memory utilisation of my pool. When I arrived home, from work, "dmesg" didn't have anything interesting to say, in terms of panics, or errors - which seems promising, but it's still early days, yet. Seems a little like a "luxury problem", that I find myself with more storage space, and data, than available RAM, given that usually, the opposite situation is true... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1899249 Title: OpenZFS writing stalls, under load Status in zfs-linux package in Ubuntu: Incomplete Bug description: Using a QNAP 4-drive USB enclosure, with a set of SSDs, on a Raspberry Pi 8GB. ZFS deduplication, and LZJB compression is enabled. This issue seems to occur, intermittently, after some time (happens with both SMB access, via Samba, and when interacting with the system, via SSH), and never previously occurred, until a few months ago, and I sometimes have to force a reboot of the system (at the cost of some data loss), in order to use it again. The "dmesg" log reports: [25375.911590] z_wr_iss_h D0 2161 2 0x0028 [25375.911606] Call trace: [25375.911627] __switch_to+0x104/0x170 [25375.911639] __schedule+0x30c/0x7c0 [25375.911647] schedule+0x3c/0xb8 [25375.911655] io_schedule+0x20/0x58 [25375.911668] rq_qos_wait+0x100/0x178 [25375.911677] wbt_wait+0xb4/0xf0 [25375.911687] __rq_qos_throttle+0x38/0x50 [25375.911700] blk_mq_make_request+0x128/0x610 [25375.911712] generic_make_request+0xb4/0x2d8 [25375.911722] submit_bio+0x48/0x218 [25375.911960] vdev_disk_io_start+0x670/0x9f8 [zfs] [25375.912181] zio_vdev_io_start+0xdc/0x2b8 [zfs] [25375.912400] zio_nowait+0xd4/0x170 [zfs] [25375.912617] vdev_mirror_io_start+0xa8/0x1b0 [zfs] [25375.912839] zio_vdev_io_start+0x248/0x2b8 [zfs] [25375.913057] zio_execute+0xac/0x110 [zfs] [25375.913096] taskq_thread+0x2f8/0x570 [spl] [25375.913108] kthread+0xfc/0x128 [25375.913119] ret_from_fork+0x10/0x1c [25375.913149] INFO: task txg_sync:2333 blocked for more than 120 seconds. [25375.919916] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [25375.926848] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25375.934835] txg_syncD0 2333 2 0x0028 [25375.934850] Call trace: [25375.934869] __switch_to+0x104/0x170 [25375.934879] __schedule+0x30c/0x7c0 [25375.934887] schedule+0x3c/0xb8 [25375.934899] schedule_timeout+0x9c/0x190 [25375.934908] io_schedule_timeout+0x28/0x48 [25375.934946] __cv_timedwait_common+0x1a8/0x1f8 [spl] [25375.934982] __cv_timedwait_io+0x3c/0x50 [spl] [25375.935205] zio_wait+0x130/0x2a0 [zfs] [25375.935423] dsl_pool_sync+0x3fc/0x498 [zfs] [25375.935650] spa_sync+0x538/0xe68 [zfs] [25375.935867] txg_sync_thread+0x2c0/0x468 [zfs] [25375.935911] thread_generic_wrapper+0x74/0xa0 [spl] [25375.935924] kthread+0xfc/0x128 [25375.935935] ret_from_fork+0x10/0x1c [25375.936017] INFO: task zbackup:75339 blocked for more than 120 seconds. [25375.942780] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [25375.949710] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25375.957702] zbackup D0 75339 5499 0x [25375.957716] Call trace: [25375.957732] __switch_to+0x104/0x170 [25375.957742] __schedule+0x30c/0x7c0 [25375.957750] schedule+0x3c/0xb8 [25375.957789] cv_wait_common+0x188/0x1b0 [spl] [25375.957823] __cv_wait+0x30/0x40 [spl] [25375.958045] zil_commit_impl+0x234/0xd30 [zfs] [25375.958263] zil_commit+0x48/0x70 [zfs] [25375.958481] zfs_create+0x544/0x7d0 [zfs] [25375.958698] zpl_create+0xb8/0x178 [zfs] [25375.958711] lookup_open+0x4ec/0x6a8 [25375.958721] do_last+0x260/0x8c0 [25375.958730] path_openat+0x84/0x258 [25375.958739] do_filp_open+0x84/0x108 [25375.958752] do_sys_open+0x180/0x2b0 [25375.958763] __arm64_sys_openat+0x2c/0x38 [25375.958773] el0_svc_common.constprop.0+0x80/0x218 [25375.958781] el0_svc_handler+0x34/0xa0 [25375.958791] el0_svc+0x10/0x2cc [25375.958801] INFO: task zbackup:95187 blocked for more than 120 seconds. [25375.965564] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [25375.972492] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25375.980479] zbackup D0 95187 5499 0x [25375.980493] Call trace: [25375.980514] __switch_to+0x104/0x170 [25375.980525] __schedule+0x30c/0x7c0 [25375.980536] schedule+0x3c/0xb8 [25375.980578]
[Kernel-packages] [Bug 1899515] 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 1899515 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/1899515 Title: ZFS Modules Missing Status in linux package in Ubuntu: Incomplete Bug description: Hello! tried to manually update to kernel 5.9 using these packages: https://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/amd64/ but dkms did not load the zfs modules so i got stuck with an angry message in busybox, no zfs modules loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899515] [NEW] ZFS Modules Missing
Public bug reported: Hello! tried to manually update to kernel 5.9 using these packages: https://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/amd64/ but dkms did not load the zfs modules so i got stuck with an angry message in busybox, no zfs modules loaded ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1899515 Title: ZFS Modules Missing Status in linux package in Ubuntu: Incomplete Bug description: Hello! tried to manually update to kernel 5.9 using these packages: https://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/amd64/ but dkms did not load the zfs modules so i got stuck with an angry message in busybox, no zfs modules loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899514] [NEW] Dependency update needed
Public bug reported: Fresh install of Ubuntu 20.04.1 here. Upon executing "sudo ubuntu-drivers install", I get the following output: linux-modules-nvidia-450-generic-hwe-20.04 : Depends: nvidia-kernel- common-450 (<= 450.66-1) but 450.80.02-0ubuntu0.20.04.2 is to be installed ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1899514 Title: Dependency update needed Status in linux-restricted-modules package in Ubuntu: New Bug description: Fresh install of Ubuntu 20.04.1 here. Upon executing "sudo ubuntu-drivers install", I get the following output: linux-modules-nvidia-450-generic-hwe-20.04 : Depends: nvidia-kernel- common-450 (<= 450.66-1) but 450.80.02-0ubuntu0.20.04.2 is to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1899514/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891100] Re: hp notebook 15-da0001nk sound mute led not working
@kaihengfeng This is the cat /proc/cmdline output after I run sudo update-grub and reboot BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=a4fd6950-d770-40a6-9863-f35146cfaf67 ro quiet splash snd_hda_intel.model=hp-mute-led-mic3 vt.handoff=7 A full dmesg is also attached. ** Attachment added: "dmesg2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891100/+attachment/5421360/+files/dmesg2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891100 Title: hp notebook 15-da0001nk sound mute led not working Status in linux package in Ubuntu: Incomplete Bug description: I install Ubuntu 20.04 with kernel 5.4 on my new HP Notebook - 15-da0001nk , the system run flawlessly except the Sound Mute LED on the F6 key. I try many solution after a humble search on the net but without success. The output of pactl list sinks/lscpi is attached. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: djalel 2167 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 MachineType: HP HP Laptop 15-da0xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=a4fd6950-d770-40a6-9863-f35146cfaf67 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/02/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd06/02/2020:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.47:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 4BY81EA#BH4 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899511] [NEW] Focal update: v5.4.68 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.68 upstream stable release from git://git.kernel.org/ af_key: pfkey_dump needs parameter validation ibmvnic fix NULL tx_pools and rx_tools issue at do_reset ibmvnic: add missing parenthesis in do_reset() kprobes: fix kill kprobe which has been marked as gone mm/thp: fix __split_huge_pmd_locked() for migration PMD act_ife: load meta modules before tcf_idr_check_alloc() bnxt_en: Avoid sending firmware messages when AER error is detected. bnxt_en: Fix NULL ptr dereference crash in bnxt_fw_reset_task() cxgb4: fix memory leak during module unload cxgb4: Fix offset when clearing filter byte counters geneve: add transport ports in route lookup for geneve hdlc_ppp: add range checks in ppp_cp_parse_cr() ip: fix tos reflection in ack and reset packets ipv4: Initialize flowi4_multipath_hash in data path ipv4: Update exception handling for multipath routes via same device ipv6: avoid lockdep issue in fib6_del() net: bridge: br_vlan_get_pvid_rcu() should dereference the VLAN group under RCU net: DCB: Validate DCB_ATTR_DCB_BUFFER argument net: dsa: rtl8366: Properly clear member config net: Fix bridge enslavement failure net: ipv6: fix kconfig dependency warning for IPV6_SEG6_HMAC net/mlx5: Fix FTE cleanup net: sch_generic: aviod concurrent reset and enqueue op for lockless qdisc net: sctp: Fix IPv6 ancestor_size calc in sctp_copy_descendant nfp: use correct define to return NONE fec taprio: Fix allowing too small intervals tipc: Fix memory leak in tipc_group_create_member() tipc: fix shutdown() of connection oriented socket tipc: use skb_unshare() instead in tipc_buf_append() net/mlx5e: Enable adding peer miss rules only if merged eswitch is supported net/mlx5e: TLS, Do not expose FPGA TLS counter if not supported bnxt_en: return proper error codes in bnxt_show_temp bnxt_en: Protect bnxt_set_eee() and bnxt_set_pauseparam() with mutex. net: lantiq: Wake TX queue again net: lantiq: use netif_tx_napi_add() for TX NAPI net: lantiq: Use napi_complete_done() net: lantiq: Disable IRQs only if NAPI gets scheduled net: phy: Avoid NPD upon phy_detach() when driver is unbound net: phy: Do not warn in phy_stop() on PHY_DOWN net: qrtr: check skb_put_padto() return value net: add __must_check to skb_put_padto() mm: memcg: fix memcg reclaim soft lockup iommu/amd: Use cmpxchg_double() when updating 128-bit IRTE Linux 5.4.68 UBUNTU: upstream stable to v5.4.68 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.68 upstream stable release + from git://git.kernel.org/ -v5.4.68 upstream stable release -from git://git.kernel.org/ + af_key: pfkey_dump needs parameter validation + ibmvnic fix NULL tx_pools and rx_tools issue at do_reset + ibmvnic: add missing parenthesis in do_reset() + kprobes: fix kill kprobe which has been marked as gone + mm/thp: fix __split_huge_pmd_locked() for migration PMD + act_ife: load meta modules before tcf_idr_check_alloc() + bnxt_en: Avoid sending firmware messages when AER error is detected. + bnxt_en: Fix NULL ptr dereference crash in bnxt_fw_reset_task() + cxgb4: fix memory leak during module unload + cxgb4: Fix offset when clearing filter byte counters + geneve:
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
I have the issue as well and the 5.4.0-48-generic kernel does NOT fix it for me. - Ubuntu 20.04.1 LTS (just upgraded from 18.04 where it worked) - Dell XPS 13 7390 Developer Edition - SteelSeries Arctis Pro Wireless -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
See attachment, everything is up to date according to fwupdmgr. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 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 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
** Attachment added: "current_firmware.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+attachment/5421352/+files/current_firmware.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 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 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899506] [NEW] Xenial update: v4.4.238 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v4.4.238 upstream stable release from git://git.kernel.org/ af_key: pfkey_dump needs parameter validation KVM: fix memory leak in kvm_io_bus_unregister_dev() kprobes: fix kill kprobe which has been marked as gone ftrace: Setup correct FTRACE_FL_REGS flags for module RDMA/ucma: ucma_context reference leak in error path mtd: Fix comparison in map_word_andequal() hdlc_ppp: add range checks in ppp_cp_parse_cr() tipc: use skb_unshare() instead in tipc_buf_append() net: add __must_check to skb_put_padto() ip: fix tos reflection in ack and reset packets serial: 8250: Avoid error message on reprobe scsi: aacraid: fix illegal IO beyond last LBA m68k: q40: Fix info-leak in rtc_ioctl gma/gma500: fix a memory disclosure bug due to uninitialized bytes ASoC: kirkwood: fix IRQ error handling PM / devfreq: tegra30: Fix integer overflow on CPU's freq max out mtd: cfi_cmdset_0002: don't free cfi->cfiq in error path of cfi_amdstd_setup() mfd: mfd-core: Protect against NULL call-back function pointer tracing: Adding NULL checks for trace_array descriptor pointer bcache: fix a lost wake-up problem caused by mca_cannibalize_lock xfs: fix attr leaf header freemap.size underflow kernel/sys.c: avoid copying possible padding bytes in copy_to_user neigh_stat_seq_next() should increase position index rt_cpu_seq_next should increase position index seqlock: Require WRITE_ONCE surrounding raw_seqcount_barrier ACPI: EC: Reference count query handlers under lock tracing: Set kernel_stack's caller size properly ar5523: Add USB ID of SMCWUSBT-G2 wireless adapter Bluetooth: Fix refcount use-after-free issue mm: pagewalk: fix termination condition in walk_pte_range() Bluetooth: prefetch channel before killing sock skbuff: fix a data race in skb_queue_len() audit: CONFIG_CHANGE don't log internal bookkeeping as an event selinux: sel_avc_get_stat_idx should increase position index scsi: lpfc: Fix RQ buffer leakage when no IOCBs available drm/omap: fix possible object reference leak dmaengine: tegra-apb: Prevent race conditions on channel's freeing media: go7007: Fix URB type for interrupt handling Bluetooth: guard against controllers sending zero'd events drm/amdgpu: increase atombios cmd timeout Bluetooth: L2CAP: handle l2cap config request during open state media: tda10071: fix unsigned sign extension overflow tpm: ibmvtpm: Wait for buffer to be set before proceeding tracing: Use address-of operator on section symbols serial: 8250_omap: Fix sleeping function called from invalid context during probe SUNRPC: Fix a potential buffer overflow in 'svc_print_xprts()' ubifs: Fix out-of-bounds memory access caused by abnormal value of node_len ALSA: usb-audio: Fix case when USB MIDI interface has more than one extra endpoint descriptor mm/filemap.c: clear page error before actual read mm/mmap.c: initialize align_offset explicitly for vm_unmapped_area KVM: Remove CREATE_IRQCHIP/SET_PIT2 race bdev: Reduce time holding bd_mutex in sync in blkdev_close() drivers: char: tlclk.c: Avoid data race between init and interrupt handler dt-bindings: sound: wm8994: Correct required supplies based on actual implementaion atm: fix a memory leak of vcc->user_back phy: samsung: s5pv210-usb2: Add delay after reset Bluetooth: Handle Inquiry Cancel error after Inquiry Complete USB: EHCI: ehci-mv: fix error handling in mv_ehci_probe() tty: serial: samsung: Correct clock selection logic ALSA: hda: Fix potential race in unsol event handler fuse: don't check refcount after stealing page USB: EHCI: ehci-mv: fix less than zero comparison of an unsigned int e1000: Do not perform reset in reset_task if we are already down printk: handle blank console arguments passed in. vfio/pci: fix memory leaks of eventfd ctx perf kcore_copy: Fix module map when there are no modules loaded mtd: rawnand: omap_elm: Fix runtime PM imbalance on error ceph: fix potential race in ceph_check_caps mtd: parser: cmdline: Support MTD names containing one or more colons x86/speculation/mds: Mark mds_user_clear_cpu_buffers() __always_inline vfio/pci: Clear error and request eventfd ctx after releasing vfio/pci: fix racy on error and request eventfd ctx s390/init: add missing __init annotations batman-adv: bla: fix type misuse for backbone_gw hash indexing atm: eni: fix the missed pci_disable_device() for eni_init_one() batman-adv: mcast/TT: fix wrongly dropped or rerouted packets ALSA: asihpi: fix iounmap in error handler MIPS: Add the missing 'CPU_1074K' into __get_cpu_type() tty: vt, consw->con_scrolldelta cleanup kprobes:
[Kernel-packages] [Bug 1899508] [NEW] alsa/hda/realtek - The front Mic on a HP machine doesn't work
Public bug reported: This fix is only for oem-5.6 kernel, other kernels will merge this patch with stable update. Our oem project needs this patch to be merged ASAP. [Impact] When using a HP machine, after plugging the headset at front jack, there is no any input device shows. [Fix] The codec of the HP ZCentrol is alc671 and it needs to override the pin configuration to enable the headset mic. This patch is going to be merged by upstream, now backport it to oem-5.6 kernel. [Test Case] Boot the system, plug a headset and check the gnome-control-center, the Mic is active in the UI, and record the sound, it could record the sound. [Regression Risk] Low, this patch is to add a platform specific quirk to override pin configuration and already tested in this HP machine. ** Affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1899508 Title: alsa/hda/realtek - The front Mic on a HP machine doesn't work Status in linux-oem-5.6 package in Ubuntu: New Bug description: This fix is only for oem-5.6 kernel, other kernels will merge this patch with stable update. Our oem project needs this patch to be merged ASAP. [Impact] When using a HP machine, after plugging the headset at front jack, there is no any input device shows. [Fix] The codec of the HP ZCentrol is alc671 and it needs to override the pin configuration to enable the headset mic. This patch is going to be merged by upstream, now backport it to oem-5.6 kernel. [Test Case] Boot the system, plug a headset and check the gnome-control-center, the Mic is active in the UI, and record the sound, it could record the sound. [Regression Risk] Low, this patch is to add a platform specific quirk to override pin configuration and already tested in this HP machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.6/+bug/1899508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
On Sun, Oct 11, 2020 at 07:07:37PM -, Paulinski wrote: >Is there any chance that his patch will be part of the official kernel >build soon? I have yet to submit the patch of fixing the root cause. But I've submitted a patch of adding polling mode to the i2c-hid module to https://www.spinics.net/lists/linux-input/msg69458.html last Friday. After the patch reaches end users like you, you can add i2c-hid.polling_mode=1 to the kernel boot parameters to make the touchpad work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5
[Kernel-packages] [Bug 1899503] Re: blk_update_request: operation not supported error (WRITE_ZEROES) on Sandisk Skyhawk nvme SSD
No logs missing. Relevant log entries, lspci, and Nvme info is embedded in issue text. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899503 Title: blk_update_request: operation not supported error (WRITE_ZEROES) on Sandisk Skyhawk nvme SSD Status in linux package in Ubuntu: Confirmed Bug description: Similar to https://bugs.launchpad.net/oem-priority/+bug/1872383 OS: Ubuntu 20.04 Kernel Affected: 5.4.0-48-generic and mainline/5.8.12-050812-generic Device: Sandisk Skyhawk NVME SSD FileSystem: Ext4 Eerror (Caused by newly formatted and mounted Ext4 partition. Can confirm the errors are thrown by the ext4lazyInit kernel thread) - [ 6305.633884] print_req_error: 20 callbacks suppressed [ 6305.633887] blk_update_request: operation not supported error, dev nvme0n1, sector 340812032 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0 [ 6305.639529] blk_update_request: operation not supported error, dev nvme0n1, sector 340812289 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0 Sandisk Skyhawk nvme firmware version/info Node SN Model Namespace Usage Format FW Rev /dev/nvme0n1 A04506C0 SDLC2CLR-016T-3NA1 1 1.60 TB / 1.60 TB 512 B + 0 B N00A /dev/nvme1n1 A04507FB SDLC2CLR-016T-3NA1 1 1.60 TB / 1.60 TB 512 B + 0 B N00A Both identical drives have same issue so not related to a single defective drive. lspci output 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480] 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481] 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:08.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 [1022:1440] 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 [1022:1441] 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 [1022:1442] 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 [1022:1443] 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 [1022:1444] 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 [1022:1445] 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 [1022:1446] 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7 [1022:1447] 01:00.0 Non-Volatile memory controller [0108]: Sandisk Corp Skyhawk Series NVME SSD [15b7:2001] (rev 01) 03:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:43d0] (rev 01) 03:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller [1022:43c8] (rev 01) 03:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge [1022:43c6] (rev 01) 20:00.0 PCI
[Kernel-packages] [Bug 1892626] Re: [radeon] Random system freeze
Unsure why, but this seems to have resolved itself - now suffering from far less (pretty much no) freezes. I must have updated some software that was causing the problem and a fix has been put in place. Appreciate the help on this forum, thank you. ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892626 Title: [radeon] Random system freeze Status in linux package in Ubuntu: Fix Released Bug description: Ubuntu 20.04.1 LTS x86_64 randomly freezing. Often when using browser (Firefox or Vivaldi) or email client (Thunderbird). Have to reboot to restart. Can occur several times a day. Didn't have problem with 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Sun Aug 23 14:08:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710] InstallationDate: Installed on 2020-06-14 (69 days ago) InstallationMedia: Regolith 20.04.0 1.4.1 LTS amd64 (20200511) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgregolith-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0903 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0903:bd10/25/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899503] 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 1899503 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899503 Title: blk_update_request: operation not supported error (WRITE_ZEROES) on Sandisk Skyhawk nvme SSD Status in linux package in Ubuntu: Incomplete Bug description: Similar to https://bugs.launchpad.net/oem-priority/+bug/1872383 OS: Ubuntu 20.04 Kernel Affected: 5.4.0-48-generic and mainline/5.8.12-050812-generic Device: Sandisk Skyhawk NVME SSD FileSystem: Ext4 Eerror (Caused by newly formatted and mounted Ext4 partition. Can confirm the errors are thrown by the ext4lazyInit kernel thread) - [ 6305.633884] print_req_error: 20 callbacks suppressed [ 6305.633887] blk_update_request: operation not supported error, dev nvme0n1, sector 340812032 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0 [ 6305.639529] blk_update_request: operation not supported error, dev nvme0n1, sector 340812289 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0 Sandisk Skyhawk nvme firmware version/info Node SN Model Namespace Usage Format FW Rev /dev/nvme0n1 A04506C0 SDLC2CLR-016T-3NA1 1 1.60 TB / 1.60 TB 512 B + 0 B N00A /dev/nvme1n1 A04507FB SDLC2CLR-016T-3NA1 1 1.60 TB / 1.60 TB 512 B + 0 B N00A Both identical drives have same issue so not related to a single defective drive. lspci output 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480] 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481] 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:08.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 [1022:1440] 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 [1022:1441] 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 [1022:1442] 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 [1022:1443] 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 [1022:1444] 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 [1022:1445] 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 [1022:1446] 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7
[Kernel-packages] [Bug 1899503] [NEW] blk_update_request: operation not supported error (WRITE_ZEROES) on Sandisk Skyhawk nvme SSD
Public bug reported: Similar to https://bugs.launchpad.net/oem-priority/+bug/1872383 OS: Ubuntu 20.04 Kernel Affected: 5.4.0-48-generic and mainline/5.8.12-050812-generic Device: Sandisk Skyhawk NVME SSD FileSystem: Ext4 Eerror (Caused by newly formatted and mounted Ext4 partition. Can confirm the errors are thrown by the ext4lazyInit kernel thread) - [ 6305.633884] print_req_error: 20 callbacks suppressed [ 6305.633887] blk_update_request: operation not supported error, dev nvme0n1, sector 340812032 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0 [ 6305.639529] blk_update_request: operation not supported error, dev nvme0n1, sector 340812289 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0 Sandisk Skyhawk nvme firmware version/info Node SN Model Namespace Usage Format FW Rev /dev/nvme0n1 A04506C0 SDLC2CLR-016T-3NA1 1 1.60 TB / 1.60 TB 512 B + 0 B N00A /dev/nvme1n1 A04507FB SDLC2CLR-016T-3NA1 1 1.60 TB / 1.60 TB 512 B + 0 B N00A Both identical drives have same issue so not related to a single defective drive. lspci output 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480] 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU [1022:1481] 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:08.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 [1022:1440] 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 [1022:1441] 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 [1022:1442] 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 [1022:1443] 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 [1022:1444] 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 [1022:1445] 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 [1022:1446] 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7 [1022:1447] 01:00.0 Non-Volatile memory controller [0108]: Sandisk Corp Skyhawk Series NVME SSD [15b7:2001] (rev 01) 03:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:43d0] (rev 01) 03:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller [1022:43c8] (rev 01) 03:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge [1022:43c6] (rev 01) 20:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01) 20:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01) 20:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01) 20:03.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01) 20:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01) 20:08.0 PCI
[Kernel-packages] [Bug 1875459] Re: System hangs when loading google maps on chrome with navi AMD GPU
Hi! I managed to fix this bug only by installing a new kernel. I installed the latter and the freezes has been stopped. You can check solution on https://linuxhint.com/update_ubuntu_kernel_20_04/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875459 Title: System hangs when loading google maps on chrome with navi AMD GPU Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 20.04 from 19.10 I can reliably hang my system by loading Google Maps in Chrome and zooming in and out. After turning on DRM debugging: echo 0x1ff | sudo tee /sys/module/drm/parameters/debug I can see the following message in the kernel log: [16333.092468] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=2542114, emitted seq=2542116 [16333.092537] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 [16333.092540] [drm] GPU recovery disabled. It seems to be this upstream bug: https://gitlab.freedesktop.org/drm/amd/issues/892 I have two workarounds: * Running Chrome with AMD_DEBUG=nongg fixes the issue on 5.4.0-26 * With the latest upstream kernel, 5.6.7-050607, Chrome can load google maps with no issues. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nicholas 5696 F pulseaudio /dev/snd/controlC0: nicholas 5696 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 18:36:12 2020 InstallationDate: Installed on 2019-11-04 (174 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_e02uh9@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_e02uh9 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago) dmi.bios.date: 07/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: X570 Phantom Gaming 4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd07/12/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
** Changed in: libvirt (Ubuntu) Status: Incomplete => In Progress ** Changed in: libvirt (Ubuntu Focal) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: In Progress Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Triaged Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Fix Released Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to be careful of the fix done for bug 1892826. It has to be checked if the linking is fine after the rebuild. The workload still works in groovy despite 2.32 being present (I'd ahve expected it doesn't), so we will keep the revert as-is for now. To be sure that adds two tests that shall be done: - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL Was pointing to glibc, does it still and if so does it work (see below)? - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic $ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-focal,accel=kvm -nographic [Regression Potential] * This adds new CPU types to the list of known CPUs defining their name and features. Generally the changes are contained to those new types and only active when selected - and usually only selectable on such new machines. Therefore not a lot should change for other users. One thing thou, if a user selected an unversioned type (which in this case only can be "EPYC") by default it will pick the
[Kernel-packages] [Bug 1881159] Re: BUG: soft lockup on return from recover to run mode on rpi3a+
** Changed in: linux-raspi (Ubuntu) Status: New => Fix Released -- 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/1881159 Title: BUG: soft lockup on return from recover to run mode on rpi3a+ Status in snapd: Invalid Status in linux-raspi package in Ubuntu: Fix Released Bug description: Image: core20 beta 20200527.5 (arm64) Device RPI3A+ === Steps to reproduce === 1. sudo snap install http 2. switch to recovery mode using: sudo http --pretty=format POST snapd:///v2/systems/$(ls /run/mnt/ubuntu-seed/systems/) action=do mode=recover 3. Once in recover mode, sudo snap install http 4. switch back to run mode: sudo http --pretty=format POST snapd:///v2/systems/$(ls /run/mnt/ubuntu-seed/systems/) action=do mode=run When I did this, the system never seems to fully return to run mode. I get errors about a soft lockup (see below) on the serial console after it reboots. However, if I pull the power at that point, and plug it back in, it does get back into run mode ## Info: input data size = 2 = 0x2 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 4638 bytes read in 3 ms (1.5 MiB/s) ## Executing script at 0240 4096 bytes read in 5 ms (799.8 KiB/s) 4096 bytes read in 3 ms (1.3 MiB/s) 8378005 bytes read in 369 ms (21.7 MiB/s) Total of 1 halfword(s) were the same Decompressing kernel... Uncompressed size: 25905664 = 0x18B4A00 18758066 bytes read in 819 ms (21.8 MiB/s) Booting Ubuntu (with booti) from mmc 0:... ## Flattened Device Tree blob at 0260 Booting using the fdt blob at 0x260 Using Device Tree in place at 0260, end 0260a065 Starting kernel ... [2.359758] spi-bcm2835 3f204000.spi: could not get clk: -517 [ 220.013319] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [systemd-udevd:533] [ 248.013307] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [systemd-udevd:533] [ 276.013308] watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-udevd:533] [ 304.013307] watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-udevd:533] [ 332.013307] watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-udevd:533] [ 360.013307] watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-udevd:533] [ 388.013314] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [systemd-udevd:533] [ 416.013308] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [systemd-udevd:533] [ 444.013309] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [systemd-udevd:533] To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872383] Re: blk_update_request error when mount nvme partition
Kai, I have added a new bug report with a little more info. https://bugs.launchpad.net/oem-priority/+bug/1899484 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1872383 Title: blk_update_request error when mount nvme partition Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [Impact] Got below error message after upgraded Focal kernel(v5.4) [ 576.793852] blk_update_request: operation not supported error, dev nvme1n1, sector 4218887 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0 This issue was introduced by below commit which added write zeros command 6e02318eaea5 nvme: add support for the Write Zeroes command SK hynix firmware has a bug that it treats NLB as max value instead of a range, so the NLB passed isn't a valid value to the firmware. [Fix] Add a quirk to disable write zeros support [Test] Verified on the machine with SK hynix PC400 nvme machine. [Regression Potential] Low, it's a quirk to a specific PCI ID. == Can't install on this nvme with a focal server installer. As mount a nvme partition with kernel with focal 5.4.0-21-generic kernel endless blk_update_request error will exists in kernel dmesg. the nvme module: PC400 NVMe SK hynix 512GB While mount nvme module: PC SN720 NVMe WDC 256GB, there is no such issue. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (11 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06c4:c401 Bizlink International Corp. DisplayPort ALT mode device Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M MachineType: Dell Inc. Precision 3930 Rack Package: linux-generic 5.4.0.21.25 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=2b73a661-f0a8-453a-ac0d-b93c5eb97f8d ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/05/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3930Rack:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: Precision dmi.product.name: Precision 3930 Rack dmi.product.sku: 0873 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1872383/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1897501] Re: HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
Verified linux-oem-5.6 version 5.6.0-1030.30 in focal-proposed.
** 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.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1897501
Title:
HP Zbook Studio G7 boots into corrupted screen with PSR featured panel
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Released
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
Sreen divided into half after installing Focal 5.4.0-48-generic under
Power Saving/Hybrid Graphics Mode. Normal as switched to Discrete
Graphics Mode. Screenshot attached as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897501/+attachment/5414860/+files/20200928_135412.jpg
.
With some more investigatin, https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?id=d246a6cfe782
("UBUNTU: SAUCE: drm/i915: Disable PSR by default on all platforms")
for bug 1849947 is the root cause. This was landed to all Ubuntu
kernels and Ubuntu only for kernel versions 5.0 and up till v5.9
unstable currently.
It seems this panel must have PSR enabled.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-48-generic 5.4.0-48.52
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm 964 F pulseaudio
CasperMD5CheckResult: skip
Date: Mon Sep 28 01:50:54 2020
InstallationDate: Installed on 2020-09-22 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200218)
MachineType: HP HP ZBook Studio G7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=ac48cfe8-5fa7-410c-ad1b-53d1e2683841 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.4.0-48-generic N/A
linux-backports-modules-5.4.0-48-generic N/A
linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2020
dmi.bios.vendor: HP
dmi.bios.version: S91 Ver. 85.28.01
dmi.board.name: 8736
dmi.board.vendor: HP
dmi.board.version: KBC Version 14.32.03
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrS91Ver.85.28.01:bd09/18/2020:svnHP:pnHPZBookStudioG7:pvr:rvnHP:rn8736:rvrKBCVersion14.32.03:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Studio G7
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1897501/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899258] Re: touchpad not work
I was just writing you a message to tell you the problem is solved. It worked with the second option : "pci=nocrs" The touchpad is now perfectly working. Thank you very much. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899258 Title: touchpad not work Status in linux package in Ubuntu: Confirmed Bug description: Laptop model: Lenovo IdeaPad 3 15IIL05-0205 When the symptom first appeared: after install Ubuntu 20.04.1 LTS the touchpad not work at all. the special keys activated by fn of the keyboard do not work either. after cat /proc/bus/input/devices not apear the touchpad ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leila 1260 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 10 14:33:38 2020 InstallationDate: Installed on 2020-10-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse] Bus 001 Device 002: ID 174f:118d Syntek Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=7dcaf7eb-d74c-49c5-94ac-df08929d97f6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897910] Re: Update the 450 and 450-server NVIDIA drivers
This bug was fixed in the package nvidia-graphics-drivers-450 - 450.80.02-0ubuntu0.20.04.2 --- nvidia-graphics-drivers-450 (450.80.02-0ubuntu0.20.04.2) focal; urgency=medium * debian/templates/control.in: - Add missing comma to fix FTBS. nvidia-graphics-drivers-450 (450.80.02-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1897910): - Improvements: o Added a new system-level interface using nvidia-capabilities via /dev for Multi-Instance GPU (MIG) on NVIDIA A100. For more information on these new device node capabilities, refer to the MIG user guide. o Added support for CUDA compatibility for CUDA 11.1, where CUDA 11.1 applications will work on supported GPUs when used with drivers >= 450.80.00 on Linux. Refer to CUDA Compatibility for more information. - Fixed Issues: o Various security issues were addressed. For additional details on the med-high severity issues, review the NVIDIA Security Bulletin 5075. o Fixed an issue where, when NVLink training encounters a fatal error, link training is still considered successful resulting in broken nodes assigned to clients. An escape case in the NVLink link state reporting caused the driver to report the links as "Active" and functional even though the link had received a fatal error. This fatal error does not allow traffic to be sent over the link, and thus would cause P2P apps to fail. This is a reporting issue, but not a functionality issue. The lacking reporting case was addressed, so the failing link state is properly reported. o Fixed a software race condition that caused link training failure (CUDA_ERROR_LAUNCH_FAILED). A race condition within the driver polling code caused a false failure in some of the link training steps. This causes the driver to not continue link training even though training actually was successful up to that point. The fix corrects these sequences so that these false failures no longer happen. * debian/templates/control: - Provide cuda 11.0-1 and 11.0-1. -- Alberto Milone Mon, 05 Oct 2020 11:19:24 +0200 ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450-server in Ubuntu. https://bugs.launchpad.net/bugs/1897910 Title: Update the 450 and 450-server NVIDIA drivers Status in nvidia-graphics-drivers-450 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-450-server package in Ubuntu: Invalid Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1897910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899258] Re: touchpad not work
interrupt the boot from grub, press e to edit the grub menu, find the line of "linux /boot/xxx", add pci=... then press ctrl+x or F10 to boot. Or edit /etc/default/grub, add pci=... before quiet splash, save the file and run sudo update-grub;reboot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899258 Title: touchpad not work Status in linux package in Ubuntu: Confirmed Bug description: Laptop model: Lenovo IdeaPad 3 15IIL05-0205 When the symptom first appeared: after install Ubuntu 20.04.1 LTS the touchpad not work at all. the special keys activated by fn of the keyboard do not work either. after cat /proc/bus/input/devices not apear the touchpad ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leila 1260 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 10 14:33:38 2020 InstallationDate: Installed on 2020-10-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse] Bus 001 Device 002: ID 174f:118d Syntek Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=7dcaf7eb-d74c-49c5-94ac-df08929d97f6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897910] Re: Update the 450 and 450-server NVIDIA drivers
This bug was fixed in the package nvidia-graphics-drivers-450-server - 450.80.02-0ubuntu0.18.04.3 --- nvidia-graphics-drivers-450-server (450.80.02-0ubuntu0.18.04.3) bionic; urgency=medium * debian/templates/dkms_nvidia.conf.in: - Drop buildfix_kernel_5.8.patch * debian/templates/dkms_nvidia.conf.in, debian/templates/nvidia-dkms-flavour.install.in, debian/templates/nvidia-dkms-flavour.postinst.in, debian/templates/nvidia-dkms-flavour.prerm.in, debian/templates/nvidia-kernel-source-flavour.install.in: - Change DKMS directory and name adding "-srv". This should fix kernel builds now that the 450 and the 450-server drivers share the same version. nvidia-graphics-drivers-450-server (450.80.02-0ubuntu0.18.04.2) bionic; urgency=medium * debian/templates/control.in: - Add missing comma in cuda provides (LP: #1897910). nvidia-graphics-drivers-450-server (450.80.02-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream release (LP: #1897910): - Improvements: o Added a new system-level interface using nvidia-capabilities via /dev for Multi-Instance GPU (MIG) on NVIDIA A100. For more information on these new device node capabilities, refer to the MIG user guide. o Added support for CUDA compatibility for CUDA 11.1, where CUDA 11.1 applications will work on supported GPUs when used with drivers >= 450.80.00 on Linux. Refer to CUDA Compatibility for more information. - Fixed Issues: o Various security issues were addressed. For additional details on the med-high severity issues, review the NVIDIA Security Bulletin 5075. o Fixed an issue where, when NVLink training encounters a fatal error, link training is still considered successful resulting in broken nodes assigned to clients. An escape case in the NVLink link state reporting caused the driver to report the links as "Active" and functional even though the link had received a fatal error. This fatal error does not allow traffic to be sent over the link, and thus would cause P2P apps to fail. This is a reporting issue, but not a functionality issue. The lacking reporting case was addressed, so the failing link state is properly reported. o Fixed a software race condition that caused link training failure (CUDA_ERROR_LAUNCH_FAILED). A race condition within the driver polling code caused a false failure in some of the link training steps. This causes the driver to not continue link training even though training actually was successful up to that point. The fix corrects these sequences so that these false failures no longer happen. * debian/templates/control: - Provide cuda 11.0-1 and 11.0-1. -- Alberto Milone Fri, 02 Oct 2020 18:58:37 +0200 ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450-server in Ubuntu. https://bugs.launchpad.net/bugs/1897910 Title: Update the 450 and 450-server NVIDIA drivers Status in nvidia-graphics-drivers-450 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-450-server package in Ubuntu: Invalid Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1897910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1862791] Re: ALC3234 - Popping sounds at the start and at the end of playback
Lenovo P51 ALC298 same problem. Poping sound and quite annoying one. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862791 Title: ALC3234 - Popping sounds at the start and at the end of playback Status in linux package in Ubuntu: Confirmed Bug description: I have bought the Canonical certified DELL Inspiron 15 3585 and i have an issue with audio playback. It only happens when using built-in speakers, it doesn't happen on playback through the 3.5 mm jack output or HDMI output. I already tried disabling power save $ cat /sys/module/snd_hda_intel/parameters/power_save 0 $ cat /sys/module/snd_hda_intel/parameters/power_save_controller N i also tried tsched=0 and using aplay /dev/zero, nothing helped thus far additional info: $ lspci | grep Audio 04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller 04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller $ dmesg | grep -i error [1.065246] tpm_crb: probe of MSFT0101:00 failed with error -16 [1.119343] RAS: Correctable Errors collector initialized. [8.980071] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro [9.769684] pcieport :00:01.7: AER: Multiple Corrected error received: :00:01.0 [9.769697] pcieport :00:01.7: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) [9.769702] pcieport :00:01.7: AER: device [1022:15d3] error status/mask=0040/6000 [ 11.691398] pcieport :00:01.7: AER: Multiple Corrected error received: :00:01.0 [ 11.691419] pcieport :00:01.7: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) [ 11.691425] pcieport :00:01.7: AER: device [1022:15d3] error status/mask=0040/6000 [ 11.727149] pcieport :00:01.7: AER: Corrected error received: :00:01.0 [ 11.727159] pcieport :00:01.7: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) [ 11.727164] pcieport :00:01.7: AER: device [1022:15d3] error status/mask=0040/6000 $ dmesg | grep -i audio [0.565377] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [9.843973] snd_hda_intel :04:00.1: Handle vga_switcheroo audio client [9.855036] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci:00/:00:08.1/:04:00.1/sound/card0/input16 [9.905946] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC3234: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [9.905950] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [9.905952] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [9.905954] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0 [9.905955] snd_hda_codec_realtek hdaudioC1D0:inputs: [9.905958] snd_hda_codec_realtek hdaudioC1D0: Headset Mic=0x19 [9.905960] snd_hda_codec_realtek hdaudioC1D0: Headphone Mic=0x1a [9.905961] snd_hda_codec_realtek hdaudioC1D0: Internal Mic=0x12 [9.963314] input: HD-Audio Generic Headphone Mic as /devices/pci:00/:00:08.1/:04:00.6/sound/card1/input18 OS: Kubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Feb 11 16:49:19 2020 InstallationDate: Installed on 2020-01-17 (24 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=pl PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jan1699 F pulseaudio /dev/snd/controlC0: jan1699 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-17 (31 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 3585 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
Qemu landed in Focal \o/ An update for Libvirt: Groovy: - MP approved - no FFe needed (as it is an SRU even) - and uploaded to groovy. - Being so close to the groovy release it might be a zero day SRU or a sooner fix before Groovy-release - we will see. Focal: - After groovy is fixed we can consider Focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Fix Released Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to be careful of the fix done for bug 1892826. It has to be checked if the linking is fine after the rebuild. The workload still works in groovy despite 2.32 being present (I'd ahve expected it doesn't), so we will keep the revert as-is for now. To be sure that adds two tests that shall be done: - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL Was pointing to glibc, does it still and if so does it work (see below)? - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic $ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-focal,accel=kvm -nographic [Regression Potential] * This adds new CPU types to the list of known CPUs defining their name and features. Generally the changes are contained to those new types and only active when selected - and usually only selectable on such new machines. Therefore not
[Kernel-packages] [Bug 1897910] Re: Update the 450 and 450-server NVIDIA drivers
This bug was fixed in the package nvidia-graphics-drivers-450-server - 450.80.02-0ubuntu0.20.04.3 --- nvidia-graphics-drivers-450-server (450.80.02-0ubuntu0.20.04.3) focal; urgency=medium * debian/templates/dkms_nvidia.conf.in: - Drop buildfix_kernel_5.8.patch * debian/templates/dkms_nvidia.conf.in, debian/templates/nvidia-dkms-flavour.install.in, debian/templates/nvidia-dkms-flavour.postinst.in, debian/templates/nvidia-dkms-flavour.prerm.in, debian/templates/nvidia-kernel-source-flavour.install.in: - Change DKMS directory and name adding "-srv". This should fix kernel builds now that the 450 and the 450-server drivers share the same version. nvidia-graphics-drivers-450-server (450.80.02-0ubuntu0.20.04.2) focal; urgency=medium * debian/templates/control.in: - Add missing comma in cuda provides (LP: #1897910). nvidia-graphics-drivers-450-server (450.80.02-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1897910): - Improvements: o Added a new system-level interface using nvidia-capabilities via /dev for Multi-Instance GPU (MIG) on NVIDIA A100. For more information on these new device node capabilities, refer to the MIG user guide. o Added support for CUDA compatibility for CUDA 11.1, where CUDA 11.1 applications will work on supported GPUs when used with drivers >= 450.80.00 on Linux. Refer to CUDA Compatibility for more information. - Fixed Issues: o Various security issues were addressed. For additional details on the med-high severity issues, review the NVIDIA Security Bulletin 5075. o Fixed an issue where, when NVLink training encounters a fatal error, link training is still considered successful resulting in broken nodes assigned to clients. An escape case in the NVLink link state reporting caused the driver to report the links as "Active" and functional even though the link had received a fatal error. This fatal error does not allow traffic to be sent over the link, and thus would cause P2P apps to fail. This is a reporting issue, but not a functionality issue. The lacking reporting case was addressed, so the failing link state is properly reported. o Fixed a software race condition that caused link training failure (CUDA_ERROR_LAUNCH_FAILED). A race condition within the driver polling code caused a false failure in some of the link training steps. This causes the driver to not continue link training even though training actually was successful up to that point. The fix corrects these sequences so that these false failures no longer happen. * debian/templates/control: - Provide cuda 11.0-1 and 11.0-1. -- Alberto Milone Fri, 02 Oct 2020 18:53:01 +0200 ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450-server in Ubuntu. https://bugs.launchpad.net/bugs/1897910 Title: Update the 450 and 450-server NVIDIA drivers Status in nvidia-graphics-drivers-450 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-450-server package in Ubuntu: Invalid Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1897910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
The attachment "Add-EPYC-ROME-x86-CPU-model.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: 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/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Fix Released Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to be careful of the fix done for bug 1892826. It has to be checked if the linking is fine after the rebuild. The workload still works in groovy despite 2.32 being present (I'd ahve expected it doesn't), so we will keep the revert as-is for now. To be sure that adds two tests that shall be done: - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL Was pointing to glibc, does it still and if so does it work (see below)? - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic $ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-focal,accel=kvm -nographic [Regression Potential] * This adds new CPU types to the list of known CPUs defining their name and features. Generally the changes are contained to those new types and only active when selected - and
[Kernel-packages] [Bug 1893655] Re: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list
This is still happening after upgrading to Ubuntu 20.10. -- 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/1893655 Title: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: When I switch on my Sony WH-1000XM3 headphones, they reconnect to my laptop at Bluetooth level, but don't appear as an audio device. I have to remove them in the Ubuntu Bluetooth settings, and then re-pair them, every time. This is rather inconvenient. This started happening after upgrading to Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Uname: Linux 5.6.0-1021-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Aug 31 14:48:53 2020 InstallationDate: Installed on 2020-07-14 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20U9CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET19W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9CTO1WW dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:AC:65:6D:04:AB ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1274806 acl:246 sco:0 events:180845 errors:0 TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1893655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893663] Re: touchpad not detected
@kaihengfeng: It wasn't blacklisted but wasn't loaded either. Blacklisting the module did not make a difference. Could you elaborate a bit on your last comment wrt this ACPI string? The problem still persists using the 5.9 kernel by the way. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893663 Title: touchpad not detected Status in linux package in Ubuntu: Incomplete Bug description: Fujitsu Lifebook U7410 core7 10th generation (Model: 7U14A1) S26391-K502-V100 no information on the touchpad fresh install ubuntu 20.04LTS * touchpad is not detected * sudo lspci -vnvn > lspci-vnvn.log more lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b61] (rev 0c) Subsystem: Fujitsu Client Computing Limited Device [1e26:003f] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Client Computing Limited UHD Graphics [1e26:004a] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, NROPrPrP-, LTR- 10BitTagComp-, 10BitTagReq-, OBFF Not Supported, ExtFmt-, EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 cat /proc/version_signature > version.log more version.log Ubuntu 5.4.0-42.46-generic 5.4.44 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmadmin2348 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 31 16:22:12 2020 InstallationDate: Installed on 2020-08-31 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7410 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=4dadb030-fc54-4457-a7cd-6934b85d602c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2020 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2D4 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2
[Kernel-packages] [Bug 1898338] Re: keyboard layout unstable after LTS upgrade to 20.04
https://wiki.archlinux.org/index.php/Linux_console/Keyboard_configuration
(any yes, I know archlinux is not ubuntu!) says:
--
A persistent keymap can be set in /etc/vconsole.conf, which is read by systemd
on start-up. The KEYMAP variable is used for specifying the keymap. If the
variable is empty or not set, the us keymap is used as default value. See
vconsole.conf(5) for all options. For example:
/etc/vconsole.conf
KEYMAP=uk
...
For convenience, localectl may be used to set console keymap. It will
change the KEYMAP variable in /etc/vconsole.conf and also set the keymap
for current session:
$ localectl set-keymap --no-convert keymap
--
and the Ubuntu manpage for localectl basically agrees with tht.
So I ran 'sudo localectl set-keymap --no-convert gb'
and /etc/vconsole.conf was (a) created, and (b) populated with
KEYMAP=gb
This had no effect whatsoever on a shutdown and fresh reboot. The kbmap
continues to be set as the unwanted default "us".
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1898338
Title:
keyboard layout unstable after LTS upgrade to 20.04
Status in linux package in Ubuntu:
Confirmed
Bug description:
After the upgrade the keyboard, set as 'English (UK)' appeared to be using a
US layout, with double-quote(") and 'at' sign(@) transposed, and key left of
'z' giving "<"/">" instead of "\"/"|" - and pound sign (GBP: £) not (yet) found.
Corrected by adding Estonian layout, then selecting English (UK) (now correct
in Preview), then deleting Estonian layout.
The layout reverted after some sudo operations, and was corrected in
the same manner.
After bootup today, the keyboard was again showing the same problems.
The same fix was again effective (though I don't suppose Estonian has
anything much to do with it!).
This behaviour is dangerous in the shell, when a pipe sign is replaced by a
redirection sign.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mbm1431 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2017-03-09 (1303 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: Dell Inc. Inspiron 5767
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=beba05d5-5ee1-4288-a1c2-c425658b569f ro quiet splash pcie_aspm=off
vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
RelatedPackageVersions:
linux-restricted-modules-5.4.0-48-generic N/A
linux-backports-modules-5.4.0-48-generic N/A
linux-firmware1.187.3
Tags: focal
Uname: Linux 5.4.0-48-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-09-30 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/30/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.9
dmi.board.name: 0PH0G6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5767:pvr:rvnDellInc.:rn0PH0G6:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5767
dmi.product.sku: 077E
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898338/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899258] Re: touchpad not work
Hello' i am affected by this bug too, can you tell me how to add that in the bootargs ? Sorry i am a newbie -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899258 Title: touchpad not work Status in linux package in Ubuntu: Confirmed Bug description: Laptop model: Lenovo IdeaPad 3 15IIL05-0205 When the symptom first appeared: after install Ubuntu 20.04.1 LTS the touchpad not work at all. the special keys activated by fn of the keyboard do not work either. after cat /proc/bus/input/devices not apear the touchpad ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leila 1260 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 10 14:33:38 2020 InstallationDate: Installed on 2020-10-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse] Bus 001 Device 002: ID 174f:118d Syntek Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=7dcaf7eb-d74c-49c5-94ac-df08929d97f6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837348] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels
Still visible on F-kvm But passed with gkeop-5.4.0-1002.2 ** Summary changed: - test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with D-KVM / E-KVM + test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1837348 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Disco: Won't Fix Status in linux-kvm source package in Eoan: Won't Fix Bug description: Issue found on a AMD64 KVM node with Disco KVM kernel. selftests: net: test_vxlan_under_vrf.sh Error: Unknown device type. Cannot remove namespace file "/var/run/netns/hv-2": No such file or directory Cannot remove namespace file "/var/run/netns/vm-1": No such file or directory Cannot remove namespace file "/var/run/netns/vm-2": No such file or directory not ok 1..24 selftests: net: test_vxlan_under_vrf.sh [FAIL] ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1010-kvm 5.0.0-1010.11 ProcVersionSignature: User Name 5.0.0-1010.11-kvm 5.0.8 Uname: Linux 5.0.0-1010-kvm x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Jul 22 05:04:42 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898808] Re: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut Status in linux package in Ubuntu: Confirmed Bug description: 1. maas:2.4.2 (7034-g2f5deb8b8-0ubuntu1) 2. 18.04(bionic) is good to deploy on the same sut/env. 3. deployment failed on SUT pxe boot stage w/ error below, "Booting under MAAS direction... error: timeout reading 'ubuntu/amd64/ga-20.04/focal/daily/boot-initrd'. press any key to continue..." 4.cross check for 'boot-initrd' file had been found on MAAS sever(ref attachment) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To
[Kernel-packages] [Bug 1898786] Re: Issue with bcache bch_mca_scan causing huge IO wait
Thanks Matthew, we'll try this kernel tomorrow. I tested it on an openstack instance, the only downside is that it uninstalls the official 4.15.0-118-generic one. Regards, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898786 Title: Issue with bcache bch_mca_scan causing huge IO wait Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: Hello, In short, we faced an issue with a huge IO wait on a bionic Ubuntu 4.15.0-118.119-generic kernel. This is the full list of process and the kernel function they were stuck in [0]. The main issue can probably be summarized by this perf reports * first identify that the cpu are stuck in idle because of something[1] * second, see what kernel function seems to stuck the process kswapd0 and kswapd1 [2]. We could see that this seems to be the mutex_lock in the bch_mca_scan function [3]. After running the command: | sudo bash -c "echo 1 > /sys/fs/bcache/f1a1e8cb-3e6b-40ea-852e- 583c48d0c2b8/internal/btree_shrinker_disabled" The server started to respond normally and the IO wait dropped significantly Here is a trace of the bcache event related lock in the kernel obtained with some bpfcc-tools [4]. klockstat-bpfcc -c bch_ -i 5 -s 3 The trace has been run in parallel with the following command line echo "Shrinker disabled: $(date)"; sleep 60; echo "Enabling shrinker: $(date)"; echo 0 | sudo tee /sys/block/bcache0/bcache/cache/internal/btree_shrinker_disabled ; sleep 60; echo "Disabling shrinker: $(date)"; echo 1 | sudo tee /sys/block/bcache0/bcache/cache/internal/btree_shrinker_disabled; sleep 60; echo "End of test: $(date)" Trying to dig more, we reduced by 20 GB the memory allocated to a VM on the server. * The bcache btree size fluctuation seems "normal" [5] * I noticed that, when the shrinker was enabled,a lot of time was spent in the locks during "bch_btree_insert_node". [6] I decided to check if one of the function called during bch_btree_insert_node was taking longer than usual when the shrinker was enabled. I finally found the "funclatency" tool and tried do have the same approach I had with the klockstat [7]. However, that was inconclusive. I could see there that the bch_btree_insert_node was barely called during the whole duration of the test. Which made me think it's amount of time spent in lock is more due to another process acquiring the lock. I'm going to try to have another go with some perf/klockstat/funclatency focused on bch_mca_scan and the function called there. Also, here are some memory related metrics [8]. Now another perf stacktrace with the command used [9]. Strangely this one doesn't show any bch_mca_scan at all. I enabled the shrinker again, hoping to get more traces, but apparently the timeframe was not right. Not enough load to trigger the cliff resulting in a 1sec IOwait plateau. Which is interesting because that means that without the maximal workload, the kernel can cope with the shrinker. [0]: https://pastebin.ubuntu.com/p/QYXPdsMCWC/ [1]: https://pastebin.ubuntu.com/p/BFsvF7H54r/ [2]: https://pastebin.ubuntu.com/p/35qdsHYHf5/ [3]: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/drivers/md/bcache/btree.c?h=Ubuntu-4.15.0-118.119#n674 [4]: https://pastebin.ubuntu.com/p/qhyqP35fCw/ [5]: https://pastebin.ubuntu.com/p/McjxxqTVjn/ [6]: https://pastebin.ubuntu.com/p/KmrnW4Ng8F/ [7]: https://pastebin.ubuntu.com/p/fSX4c7tTFV/ [8]: https://pastebin.ubuntu.com/p/CZgXkgKhmJ/ [9]: https://pastebin.ubuntu.com/p/DzKCP8NGdf/ $ cat /proc/version_signature Ubuntu 4.15.0-118.119-generic 4.15.18 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-118-generic 4.15.0-118.119 ProcVersionSignature: User Name 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 10:04 seq crw-rw 1 root audio 116, 33 Sep 29 10:04 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Oct 6 20:36:18 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL380 G7 PciMultimedia: ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=c6ad1629-a506-4043-a339-6d57f0708d12 ro console=ttyS1,115200 nosplash RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A
[Kernel-packages] [Bug 1899249] Re: OpenZFS writing stalls, under load
You could shrink the DDT by making a copy of the files in place (with dedup off) and deleting the old file. That only requires enough extra space for a single file at a time. This assumes no snapshots. If you need to preserve snapshots, another option would be to send|recv a dataset at a time. If you have enough free space for a copy of the largest dataset, this would work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1899249 Title: OpenZFS writing stalls, under load Status in zfs-linux package in Ubuntu: Incomplete Bug description: Using a QNAP 4-drive USB enclosure, with a set of SSDs, on a Raspberry Pi 8GB. ZFS deduplication, and LZJB compression is enabled. This issue seems to occur, intermittently, after some time (happens with both SMB access, via Samba, and when interacting with the system, via SSH), and never previously occurred, until a few months ago, and I sometimes have to force a reboot of the system (at the cost of some data loss), in order to use it again. The "dmesg" log reports: [25375.911590] z_wr_iss_h D0 2161 2 0x0028 [25375.911606] Call trace: [25375.911627] __switch_to+0x104/0x170 [25375.911639] __schedule+0x30c/0x7c0 [25375.911647] schedule+0x3c/0xb8 [25375.911655] io_schedule+0x20/0x58 [25375.911668] rq_qos_wait+0x100/0x178 [25375.911677] wbt_wait+0xb4/0xf0 [25375.911687] __rq_qos_throttle+0x38/0x50 [25375.911700] blk_mq_make_request+0x128/0x610 [25375.911712] generic_make_request+0xb4/0x2d8 [25375.911722] submit_bio+0x48/0x218 [25375.911960] vdev_disk_io_start+0x670/0x9f8 [zfs] [25375.912181] zio_vdev_io_start+0xdc/0x2b8 [zfs] [25375.912400] zio_nowait+0xd4/0x170 [zfs] [25375.912617] vdev_mirror_io_start+0xa8/0x1b0 [zfs] [25375.912839] zio_vdev_io_start+0x248/0x2b8 [zfs] [25375.913057] zio_execute+0xac/0x110 [zfs] [25375.913096] taskq_thread+0x2f8/0x570 [spl] [25375.913108] kthread+0xfc/0x128 [25375.913119] ret_from_fork+0x10/0x1c [25375.913149] INFO: task txg_sync:2333 blocked for more than 120 seconds. [25375.919916] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [25375.926848] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25375.934835] txg_syncD0 2333 2 0x0028 [25375.934850] Call trace: [25375.934869] __switch_to+0x104/0x170 [25375.934879] __schedule+0x30c/0x7c0 [25375.934887] schedule+0x3c/0xb8 [25375.934899] schedule_timeout+0x9c/0x190 [25375.934908] io_schedule_timeout+0x28/0x48 [25375.934946] __cv_timedwait_common+0x1a8/0x1f8 [spl] [25375.934982] __cv_timedwait_io+0x3c/0x50 [spl] [25375.935205] zio_wait+0x130/0x2a0 [zfs] [25375.935423] dsl_pool_sync+0x3fc/0x498 [zfs] [25375.935650] spa_sync+0x538/0xe68 [zfs] [25375.935867] txg_sync_thread+0x2c0/0x468 [zfs] [25375.935911] thread_generic_wrapper+0x74/0xa0 [spl] [25375.935924] kthread+0xfc/0x128 [25375.935935] ret_from_fork+0x10/0x1c [25375.936017] INFO: task zbackup:75339 blocked for more than 120 seconds. [25375.942780] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [25375.949710] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25375.957702] zbackup D0 75339 5499 0x [25375.957716] Call trace: [25375.957732] __switch_to+0x104/0x170 [25375.957742] __schedule+0x30c/0x7c0 [25375.957750] schedule+0x3c/0xb8 [25375.957789] cv_wait_common+0x188/0x1b0 [spl] [25375.957823] __cv_wait+0x30/0x40 [spl] [25375.958045] zil_commit_impl+0x234/0xd30 [zfs] [25375.958263] zil_commit+0x48/0x70 [zfs] [25375.958481] zfs_create+0x544/0x7d0 [zfs] [25375.958698] zpl_create+0xb8/0x178 [zfs] [25375.958711] lookup_open+0x4ec/0x6a8 [25375.958721] do_last+0x260/0x8c0 [25375.958730] path_openat+0x84/0x258 [25375.958739] do_filp_open+0x84/0x108 [25375.958752] do_sys_open+0x180/0x2b0 [25375.958763] __arm64_sys_openat+0x2c/0x38 [25375.958773] el0_svc_common.constprop.0+0x80/0x218 [25375.958781] el0_svc_handler+0x34/0xa0 [25375.958791] el0_svc+0x10/0x2cc [25375.958801] INFO: task zbackup:95187 blocked for more than 120 seconds. [25375.965564] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [25375.972492] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25375.980479] zbackup D0 95187 5499 0x [25375.980493] Call trace: [25375.980514] __switch_to+0x104/0x170 [25375.980525] __schedule+0x30c/0x7c0 [25375.980536] schedule+0x3c/0xb8 [25375.980578] cv_wait_common+0x188/0x1b0 [spl] [25375.980612] __cv_wait+0x30/0x40 [spl] [25375.980834] zil_commit_impl+0x234/0xd30 [zfs] [25375.981052] zil_commit+0x48/0x70 [zfs] [25375.981280] zfs_write+0xa3c/0xb90 [zfs] [25375.981498] zpl_write_common_iovec+0xac/0x120 [zfs]
[Kernel-packages] [Bug 1887490] Update Released
The verification of the Stable Release Update for qemu has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Fix Released Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to be careful of the fix done for bug 1892826. It has to be checked if the linking is fine after the rebuild. The workload still works in groovy despite 2.32 being present (I'd ahve expected it doesn't), so we will keep the revert as-is for now. To be sure that adds two tests that shall be done: - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL Was pointing to glibc, does it still and if so does it work (see below)? - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic $ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-focal,accel=kvm -nographic [Regression Potential] * This adds new CPU types to the list of known CPUs defining their name and features. Generally the
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
This bug was fixed in the package qemu - 1:4.2-3ubuntu6.7 --- qemu (1:4.2-3ubuntu6.7) focal; urgency=medium * d/p/ubuntu/lp-1882774-*: add newer EPYC processor types (LP: #1887490) * d/p/u/lp-1896751-exec-rom_reset-Free-rom-data-during-inmigrate-skip.patch: fix reboot after migration (LP: #1896751) * d/p/u/lp-1849644-io-channel-websock-treat-binary-and-no-sub-protocol-.patch: fix websocket compatibility with newer versions of noVNC (LP: #1849644) -- Christian Ehrhardt Mon, 27 Jul 2020 11:45:26 +0200 ** Changed in: qemu (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Fix Released Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to be careful of the fix done for bug 1892826. It has to be checked if the linking is fine after the rebuild. The workload still works in groovy despite 2.32 being present (I'd ahve expected it doesn't), so we will keep the revert as-is for now. To be sure that adds two tests that shall be done: - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL Was pointing to glibc, does it still and if so does it work (see below)? - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic $ qemu-system-x86_64 -cpu EPYC-v3 -machine
[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 For me it is fixed since the latest kernel update, 5.4.0-48-generic. - Ubuntu 20.04.1 LTS - Dell XPS 15 7590 - Bose QuietComfort 35 II -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
For me it is fixed since the latest kernel update, 5.4.0-48-generic. - Ubuntu 20.04.1 LTS - Dell XPS 15 7590 - Bose QuietComfort 35 II -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895281] Re: ioctl_sg01 from ubuntu_ltp_syscalls time out on X-4.15 Oracle with BM.Standard2.52
Can be found on X-fips P8 as well. ** Tags added: 4.4 ppc64el -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895281 Title: ioctl_sg01 from ubuntu_ltp_syscalls time out on X-4.15 Oracle with BM.Standard2.52 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Oracle instance BM.Standard2.52 only (passed with VM.DenseIO2.8 and VM.Standard2.1), with 4.15.0-1054.58~16.04.1-oracle Test failed with: startup='Fri Sep 11 07:00:00 2020' tst_test.c:1250: INFO: Timeout per run is 0h 05m 00s ioctl_sg01.c:81: INFO: Found SCSI device /dev/sg1 Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! tst_test.c:1295: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1296: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tag=ioctl_sg01 stime=1599807600 dur=312 exit=exited stat=2 core=no cu=8033 cs=23149 Need to see if bumping timeout helps or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1895281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895281] Re: ioctl_sg01 from ubuntu_ltp_syscalls time out on X-4.15 Oracle with BM.Standard2.52
Hmm, the error on x-fips p8 looks different, I will file a new one for it. ** Tags removed: 4.4 ppc64el -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895281 Title: ioctl_sg01 from ubuntu_ltp_syscalls time out on X-4.15 Oracle with BM.Standard2.52 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Oracle instance BM.Standard2.52 only (passed with VM.DenseIO2.8 and VM.Standard2.1), with 4.15.0-1054.58~16.04.1-oracle Test failed with: startup='Fri Sep 11 07:00:00 2020' tst_test.c:1250: INFO: Timeout per run is 0h 05m 00s ioctl_sg01.c:81: INFO: Found SCSI device /dev/sg1 Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! tst_test.c:1295: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1296: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tag=ioctl_sg01 stime=1599807600 dur=312 exit=exited stat=2 core=no cu=8033 cs=23149 Need to see if bumping timeout helps or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1895281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Same here (Ubuntu 20.04) -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1316518] Re: [900X3G, Realtek ALC282, Mic, Internal] inverted mic not working
Still exist in 20.04 ** Attachment added: "status-s900x-2020-10-12=09-30.bash" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1316518/+attachment/5421161/+files/status-s900x-2020-10-12%3D09-30.bash -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1316518 Title: [900X3G, Realtek ALC282, Mic, Internal] inverted mic not working Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Internal Mic of Samsung Ativ book 9 (NP900X3G) is not supported properly. Stereo recording in audacity records sound from mic in L channel and only loud noise in R channel (phase inverted?) Muting R channel, and setting L channel to around 16%, in pavucontrol allows to record audio, but in poor quality. alsa-info.sh output: http://www.alsa- project.org/db/?f=064f0b536a1b068efd30d58c2641b5ec2348f059 Ubuntu Gnome 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sarah 2014 F pulseaudio sarah 8509 F alsamixer /dev/snd/controlC0: sarah 2014 F pulseaudio CurrentDesktop: GNOME Date: Tue May 6 11:55:36 2014 InstallationDate: Installed on 2014-04-29 (6 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Internes Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: None of the above Title: [900X3G, Realtek ALC282, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04ADU.023.140414.PS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP900X3G-K02DE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04ADU.023.140414.PS:bd04/14/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3G:pvrP04ADU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3G-K02DE:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 900X3G dmi.product.version: P04ADU dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sarah 2004 F pulseaudio /dev/snd/controlC1: sarah 2004 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=b4bd3914-d1c4-40f0-ba32-fb19aa9af13c InstallationDate: Installed on 2014-04-29 (27 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3G Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=92ac4966-692f-4e06-a1dd-da069008e861 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 StagingDrivers: rts5139 Tags: trusty trusty staging Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/14/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04ADU.023.140414.PS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP900X3G-K02DE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias:
[Kernel-packages] [Bug 1742865] Re: Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742865 Title: Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found Status in linux package in Ubuntu: Fix Released Bug description: Browsed and tried solutions over the past 2 years, nothing worked... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98 Uname: Linux 4.4.0-108-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jan 12 06:43:48 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:3828] Subsystem: Lenovo GM108M [GeForce 940M] [17aa:3829] InstallationDate: Installed on 2016-07-07 (553 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:208d Elan Microelectronics Corp. Bus 001 Device 003: ID 174f:14e6 Syntek Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80R6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic.efi.signed root=UUID=8fa7aafa-77cc-4651-b87f-4565439e7577 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2015 dmi.bios.vendor: LENOVO dmi.bios.version: D3CN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-15ISK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-15ISK dmi.modalias: dmi:bvnLENOVO:bvrD3CN27WW:bd10/28/2015:svnLENOVO:pn80R6:pvrLenovoYoga500-15ISK:rvnLENOVO:rnLenovoYoga500-15ISK:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYoga500-15ISK: dmi.product.name: 80R6 dmi.product.version: Lenovo Yoga 500-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jan 12 06:14:57 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14162 vendor SDC xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742865] Re: Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found
since I migrated to 18.04 Fn keys all work, Flip screen and Touch keyboard work Ubuntu 20.04 gives directly the Drivers for the extra Nvidia videocard -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742865 Title: Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found Status in linux package in Ubuntu: Fix Released Bug description: Browsed and tried solutions over the past 2 years, nothing worked... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98 Uname: Linux 4.4.0-108-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jan 12 06:43:48 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:3828] Subsystem: Lenovo GM108M [GeForce 940M] [17aa:3829] InstallationDate: Installed on 2016-07-07 (553 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:208d Elan Microelectronics Corp. Bus 001 Device 003: ID 174f:14e6 Syntek Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80R6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic.efi.signed root=UUID=8fa7aafa-77cc-4651-b87f-4565439e7577 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2015 dmi.bios.vendor: LENOVO dmi.bios.version: D3CN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-15ISK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-15ISK dmi.modalias: dmi:bvnLENOVO:bvrD3CN27WW:bd10/28/2015:svnLENOVO:pn80R6:pvrLenovoYoga500-15ISK:rvnLENOVO:rnLenovoYoga500-15ISK:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYoga500-15ISK: dmi.product.name: 80R6 dmi.product.version: Lenovo Yoga 500-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jan 12 06:14:57 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14162 vendor SDC xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1742865] Re: Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found
Hello Daniel, since I migrated to 18.04 Fn keys all work, Flip screen and Touch keyboard work Ubuntu 20.04 gives directly the Drivers for the extra Nvidia videocard So I am good :) Thank you for you inquiry /Marc Op 12.10.20 om 09:14 schreef Daniel van Vugt: > This is two separate issues: > > 1. Please tell us if you still have a problem with Fn keys not working > in a more recent Ubuntu release. > > 2. The nvidia card is detected according to your Lspci.txt, but it > appears there's just no driver installed for it. > > ** Summary changed: > > - Fn Keys do not work, nvidia card not found > + Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found > > ** Package changed: xorg (Ubuntu) => linux (Ubuntu) > > ** Changed in: linux (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742865 Title: Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found Status in linux package in Ubuntu: Incomplete Bug description: Browsed and tried solutions over the past 2 years, nothing worked... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98 Uname: Linux 4.4.0-108-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jan 12 06:43:48 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:3828] Subsystem: Lenovo GM108M [GeForce 940M] [17aa:3829] InstallationDate: Installed on 2016-07-07 (553 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:208d Elan Microelectronics Corp. Bus 001 Device 003: ID 174f:14e6 Syntek Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80R6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic.efi.signed root=UUID=8fa7aafa-77cc-4651-b87f-4565439e7577 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2015 dmi.bios.vendor: LENOVO dmi.bios.version: D3CN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-15ISK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-15ISK dmi.modalias: dmi:bvnLENOVO:bvrD3CN27WW:bd10/28/2015:svnLENOVO:pn80R6:pvrLenovoYoga500-15ISK:rvnLENOVO:rnLenovoYoga500-15ISK:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYoga500-15ISK: dmi.product.name: 80R6 dmi.product.version: Lenovo Yoga 500-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jan 12 06:14:57 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14162 vendor SDC xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742865] Re: Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found
This is two separate issues: 1. Please tell us if you still have a problem with Fn keys not working in a more recent Ubuntu release. 2. The nvidia card is detected according to your Lspci.txt, but it appears there's just no driver installed for it. ** Summary changed: - Fn Keys do not work, nvidia card not found + Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742865 Title: Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found Status in linux package in Ubuntu: Incomplete Bug description: Browsed and tried solutions over the past 2 years, nothing worked... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98 Uname: Linux 4.4.0-108-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jan 12 06:43:48 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:3828] Subsystem: Lenovo GM108M [GeForce 940M] [17aa:3829] InstallationDate: Installed on 2016-07-07 (553 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:208d Elan Microelectronics Corp. Bus 001 Device 003: ID 174f:14e6 Syntek Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80R6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic.efi.signed root=UUID=8fa7aafa-77cc-4651-b87f-4565439e7577 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2015 dmi.bios.vendor: LENOVO dmi.bios.version: D3CN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-15ISK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-15ISK dmi.modalias: dmi:bvnLENOVO:bvrD3CN27WW:bd10/28/2015:svnLENOVO:pn80R6:pvrLenovoYoga500-15ISK:rvnLENOVO:rnLenovoYoga500-15ISK:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYoga500-15ISK: dmi.product.name: 80R6 dmi.product.version: Lenovo Yoga 500-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jan 12 06:14:57 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14162 vendor SDC xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899249] Re: OpenZFS writing stalls, under load
Unfortunately, I haven't got a storage device large enough, to contain all of the data from the pool, and much of it cannot be recreated, or restored, from another source, so I won't be able to nuke the pool, and rebuild it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1899249 Title: OpenZFS writing stalls, under load Status in zfs-linux package in Ubuntu: Incomplete Bug description: Using a QNAP 4-drive USB enclosure, with a set of SSDs, on a Raspberry Pi 8GB. ZFS deduplication, and LZJB compression is enabled. This issue seems to occur, intermittently, after some time (happens with both SMB access, via Samba, and when interacting with the system, via SSH), and never previously occurred, until a few months ago, and I sometimes have to force a reboot of the system (at the cost of some data loss), in order to use it again. The "dmesg" log reports: [25375.911590] z_wr_iss_h D0 2161 2 0x0028 [25375.911606] Call trace: [25375.911627] __switch_to+0x104/0x170 [25375.911639] __schedule+0x30c/0x7c0 [25375.911647] schedule+0x3c/0xb8 [25375.911655] io_schedule+0x20/0x58 [25375.911668] rq_qos_wait+0x100/0x178 [25375.911677] wbt_wait+0xb4/0xf0 [25375.911687] __rq_qos_throttle+0x38/0x50 [25375.911700] blk_mq_make_request+0x128/0x610 [25375.911712] generic_make_request+0xb4/0x2d8 [25375.911722] submit_bio+0x48/0x218 [25375.911960] vdev_disk_io_start+0x670/0x9f8 [zfs] [25375.912181] zio_vdev_io_start+0xdc/0x2b8 [zfs] [25375.912400] zio_nowait+0xd4/0x170 [zfs] [25375.912617] vdev_mirror_io_start+0xa8/0x1b0 [zfs] [25375.912839] zio_vdev_io_start+0x248/0x2b8 [zfs] [25375.913057] zio_execute+0xac/0x110 [zfs] [25375.913096] taskq_thread+0x2f8/0x570 [spl] [25375.913108] kthread+0xfc/0x128 [25375.913119] ret_from_fork+0x10/0x1c [25375.913149] INFO: task txg_sync:2333 blocked for more than 120 seconds. [25375.919916] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [25375.926848] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25375.934835] txg_syncD0 2333 2 0x0028 [25375.934850] Call trace: [25375.934869] __switch_to+0x104/0x170 [25375.934879] __schedule+0x30c/0x7c0 [25375.934887] schedule+0x3c/0xb8 [25375.934899] schedule_timeout+0x9c/0x190 [25375.934908] io_schedule_timeout+0x28/0x48 [25375.934946] __cv_timedwait_common+0x1a8/0x1f8 [spl] [25375.934982] __cv_timedwait_io+0x3c/0x50 [spl] [25375.935205] zio_wait+0x130/0x2a0 [zfs] [25375.935423] dsl_pool_sync+0x3fc/0x498 [zfs] [25375.935650] spa_sync+0x538/0xe68 [zfs] [25375.935867] txg_sync_thread+0x2c0/0x468 [zfs] [25375.935911] thread_generic_wrapper+0x74/0xa0 [spl] [25375.935924] kthread+0xfc/0x128 [25375.935935] ret_from_fork+0x10/0x1c [25375.936017] INFO: task zbackup:75339 blocked for more than 120 seconds. [25375.942780] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [25375.949710] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25375.957702] zbackup D0 75339 5499 0x [25375.957716] Call trace: [25375.957732] __switch_to+0x104/0x170 [25375.957742] __schedule+0x30c/0x7c0 [25375.957750] schedule+0x3c/0xb8 [25375.957789] cv_wait_common+0x188/0x1b0 [spl] [25375.957823] __cv_wait+0x30/0x40 [spl] [25375.958045] zil_commit_impl+0x234/0xd30 [zfs] [25375.958263] zil_commit+0x48/0x70 [zfs] [25375.958481] zfs_create+0x544/0x7d0 [zfs] [25375.958698] zpl_create+0xb8/0x178 [zfs] [25375.958711] lookup_open+0x4ec/0x6a8 [25375.958721] do_last+0x260/0x8c0 [25375.958730] path_openat+0x84/0x258 [25375.958739] do_filp_open+0x84/0x108 [25375.958752] do_sys_open+0x180/0x2b0 [25375.958763] __arm64_sys_openat+0x2c/0x38 [25375.958773] el0_svc_common.constprop.0+0x80/0x218 [25375.958781] el0_svc_handler+0x34/0xa0 [25375.958791] el0_svc+0x10/0x2cc [25375.958801] INFO: task zbackup:95187 blocked for more than 120 seconds. [25375.965564] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [25375.972492] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25375.980479] zbackup D0 95187 5499 0x [25375.980493] Call trace: [25375.980514] __switch_to+0x104/0x170 [25375.980525] __schedule+0x30c/0x7c0 [25375.980536] schedule+0x3c/0xb8 [25375.980578] cv_wait_common+0x188/0x1b0 [spl] [25375.980612] __cv_wait+0x30/0x40 [spl] [25375.980834] zil_commit_impl+0x234/0xd30 [zfs] [25375.981052] zil_commit+0x48/0x70 [zfs] [25375.981280] zfs_write+0xa3c/0xb90 [zfs] [25375.981498] zpl_write_common_iovec+0xac/0x120 [zfs] [25375.981726] zpl_iter_write+0xe4/0x150 [zfs] [25375.981766] new_sync_write+0x100/0x1a8 [25375.981776] __vfs_write+0x74/0x90 [25375.981784]
[Kernel-packages] [Bug 1742865] [NEW] Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found
You have been subscribed to a public bug: Browsed and tried solutions over the past 2 years, nothing worked... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98 Uname: Linux 4.4.0-108-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jan 12 06:43:48 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:3828] Subsystem: Lenovo GM108M [GeForce 940M] [17aa:3829] InstallationDate: Installed on 2016-07-07 (553 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:208d Elan Microelectronics Corp. Bus 001 Device 003: ID 174f:14e6 Syntek Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80R6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic.efi.signed root=UUID=8fa7aafa-77cc-4651-b87f-4565439e7577 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2015 dmi.bios.vendor: LENOVO dmi.bios.version: D3CN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-15ISK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-15ISK dmi.modalias: dmi:bvnLENOVO:bvrD3CN27WW:bd10/28/2015:svnLENOVO:pn80R6:pvrLenovoYoga500-15ISK:rvnLENOVO:rnLenovoYoga500-15ISK:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYoga500-15ISK: dmi.product.name: 80R6 dmi.product.version: Lenovo Yoga 500-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jan 12 06:14:57 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14162 vendor SDC xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- Lenovo Yoga 500-15ISK Fn Keys do not work, nvidia card not found https://bugs.launchpad.net/bugs/1742865 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 1899249] Re: OpenZFS writing stalls, under load
Did you destroy and recreate the pool after disabling dedup? Otherwise you still have the same dedup table and haven’t really accomplished much. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1899249 Title: OpenZFS writing stalls, under load Status in zfs-linux package in Ubuntu: Incomplete Bug description: Using a QNAP 4-drive USB enclosure, with a set of SSDs, on a Raspberry Pi 8GB. ZFS deduplication, and LZJB compression is enabled. This issue seems to occur, intermittently, after some time (happens with both SMB access, via Samba, and when interacting with the system, via SSH), and never previously occurred, until a few months ago, and I sometimes have to force a reboot of the system (at the cost of some data loss), in order to use it again. The "dmesg" log reports: [25375.911590] z_wr_iss_h D0 2161 2 0x0028 [25375.911606] Call trace: [25375.911627] __switch_to+0x104/0x170 [25375.911639] __schedule+0x30c/0x7c0 [25375.911647] schedule+0x3c/0xb8 [25375.911655] io_schedule+0x20/0x58 [25375.911668] rq_qos_wait+0x100/0x178 [25375.911677] wbt_wait+0xb4/0xf0 [25375.911687] __rq_qos_throttle+0x38/0x50 [25375.911700] blk_mq_make_request+0x128/0x610 [25375.911712] generic_make_request+0xb4/0x2d8 [25375.911722] submit_bio+0x48/0x218 [25375.911960] vdev_disk_io_start+0x670/0x9f8 [zfs] [25375.912181] zio_vdev_io_start+0xdc/0x2b8 [zfs] [25375.912400] zio_nowait+0xd4/0x170 [zfs] [25375.912617] vdev_mirror_io_start+0xa8/0x1b0 [zfs] [25375.912839] zio_vdev_io_start+0x248/0x2b8 [zfs] [25375.913057] zio_execute+0xac/0x110 [zfs] [25375.913096] taskq_thread+0x2f8/0x570 [spl] [25375.913108] kthread+0xfc/0x128 [25375.913119] ret_from_fork+0x10/0x1c [25375.913149] INFO: task txg_sync:2333 blocked for more than 120 seconds. [25375.919916] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [25375.926848] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25375.934835] txg_syncD0 2333 2 0x0028 [25375.934850] Call trace: [25375.934869] __switch_to+0x104/0x170 [25375.934879] __schedule+0x30c/0x7c0 [25375.934887] schedule+0x3c/0xb8 [25375.934899] schedule_timeout+0x9c/0x190 [25375.934908] io_schedule_timeout+0x28/0x48 [25375.934946] __cv_timedwait_common+0x1a8/0x1f8 [spl] [25375.934982] __cv_timedwait_io+0x3c/0x50 [spl] [25375.935205] zio_wait+0x130/0x2a0 [zfs] [25375.935423] dsl_pool_sync+0x3fc/0x498 [zfs] [25375.935650] spa_sync+0x538/0xe68 [zfs] [25375.935867] txg_sync_thread+0x2c0/0x468 [zfs] [25375.935911] thread_generic_wrapper+0x74/0xa0 [spl] [25375.935924] kthread+0xfc/0x128 [25375.935935] ret_from_fork+0x10/0x1c [25375.936017] INFO: task zbackup:75339 blocked for more than 120 seconds. [25375.942780] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [25375.949710] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25375.957702] zbackup D0 75339 5499 0x [25375.957716] Call trace: [25375.957732] __switch_to+0x104/0x170 [25375.957742] __schedule+0x30c/0x7c0 [25375.957750] schedule+0x3c/0xb8 [25375.957789] cv_wait_common+0x188/0x1b0 [spl] [25375.957823] __cv_wait+0x30/0x40 [spl] [25375.958045] zil_commit_impl+0x234/0xd30 [zfs] [25375.958263] zil_commit+0x48/0x70 [zfs] [25375.958481] zfs_create+0x544/0x7d0 [zfs] [25375.958698] zpl_create+0xb8/0x178 [zfs] [25375.958711] lookup_open+0x4ec/0x6a8 [25375.958721] do_last+0x260/0x8c0 [25375.958730] path_openat+0x84/0x258 [25375.958739] do_filp_open+0x84/0x108 [25375.958752] do_sys_open+0x180/0x2b0 [25375.958763] __arm64_sys_openat+0x2c/0x38 [25375.958773] el0_svc_common.constprop.0+0x80/0x218 [25375.958781] el0_svc_handler+0x34/0xa0 [25375.958791] el0_svc+0x10/0x2cc [25375.958801] INFO: task zbackup:95187 blocked for more than 120 seconds. [25375.965564] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [25375.972492] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25375.980479] zbackup D0 95187 5499 0x [25375.980493] Call trace: [25375.980514] __switch_to+0x104/0x170 [25375.980525] __schedule+0x30c/0x7c0 [25375.980536] schedule+0x3c/0xb8 [25375.980578] cv_wait_common+0x188/0x1b0 [spl] [25375.980612] __cv_wait+0x30/0x40 [spl] [25375.980834] zil_commit_impl+0x234/0xd30 [zfs] [25375.981052] zil_commit+0x48/0x70 [zfs] [25375.981280] zfs_write+0xa3c/0xb90 [zfs] [25375.981498] zpl_write_common_iovec+0xac/0x120 [zfs] [25375.981726] zpl_iter_write+0xe4/0x150 [zfs] [25375.981766] new_sync_write+0x100/0x1a8 [25375.981776] __vfs_write+0x74/0x90 [25375.981784] vfs_write+0xe4/0x1c8 [25375.981794] ksys_write+0x78/0x100 [25375.981803]
[Kernel-packages] [Bug 1899249] Re: OpenZFS writing stalls, under load
Also receive this, when trying to archive a large directory: [ 2055.147509] INFO: task z_wr_iss_h:2169 blocked for more than 120 seconds. [ 2055.154450] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [ 2055.161401] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.169403] z_wr_iss_h D0 2169 2 0x0028 [ 2055.169420] Call trace: [ 2055.169441] __switch_to+0x104/0x170 [ 2055.169453] __schedule+0x30c/0x7c0 [ 2055.169462] schedule+0x3c/0xb8 [ 2055.169470] io_schedule+0x20/0x58 [ 2055.169483] rq_qos_wait+0x100/0x178 [ 2055.169492] wbt_wait+0xb4/0xf0 [ 2055.169502] __rq_qos_throttle+0x38/0x50 [ 2055.169514] blk_mq_make_request+0x128/0x610 [ 2055.169526] generic_make_request+0xb4/0x2d8 [ 2055.169537] submit_bio+0x48/0x218 [ 2055.169779] vdev_disk_io_start+0x670/0x9f8 [zfs] [ 2055.170005] zio_vdev_io_start+0xdc/0x2b8 [zfs] [ 2055.170229] zio_nowait+0xd4/0x170 [zfs] [ 2055.170451] vdev_mirror_io_start+0xa8/0x1b0 [zfs] [ 2055.170673] zio_vdev_io_start+0x248/0x2b8 [zfs] [ 2055.170896] zio_execute+0xac/0x110 [zfs] [ 2055.170937] taskq_thread+0x2f8/0x570 [spl] [ 2055.170950] kthread+0xfc/0x128 [ 2055.170960] ret_from_fork+0x10/0x1c [ 2055.170990] INFO: task txg_quiesce:2380 blocked for more than 120 seconds. [ 2055.178025] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [ 2055.184958] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.192949] txg_quiesce D0 2380 2 0x0028 [ 2055.192963] Call trace: [ 2055.192984] __switch_to+0x104/0x170 [ 2055.192995] __schedule+0x30c/0x7c0 [ 2055.193003] schedule+0x3c/0xb8 [ 2055.193046] cv_wait_common+0x188/0x1b0 [spl] [ 2055.193082] __cv_wait+0x30/0x40 [spl] [ 2055.193310] txg_quiesce_thread+0x27c/0x380 [zfs] [ 2055.193349] thread_generic_wrapper+0x74/0xa0 [spl] [ 2055.193370] kthread+0xfc/0x128 [ 2055.193381] ret_from_fork+0x10/0x1c [ 2055.193438] INFO: task smbd:3662 blocked for more than 120 seconds. [ 2055.199853] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [ 2055.206784] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.214772] smbdD0 3662 3498 0x [ 2055.214786] Call trace: [ 2055.214800] __switch_to+0x104/0x170 [ 2055.214810] __schedule+0x30c/0x7c0 [ 2055.214818] schedule+0x3c/0xb8 [ 2055.214856] cv_wait_common+0x188/0x1b0 [spl] [ 2055.214892] __cv_wait+0x30/0x40 [spl] [ 2055.215121] zil_commit_impl+0x234/0xd30 [zfs] [ 2055.215344] zil_commit+0x48/0x70 [zfs] [ 2055.215567] zfs_read+0x2f8/0x418 [zfs] [ 2055.215831] zpl_read_common_iovec+0xa8/0x110 [zfs] [ 2055.216065] zpl_read_common+0x4c/0x70 [zfs] [ 2055.216288] zpl_xattr_get_dir+0x10c/0x128 [zfs] [ 2055.216519] zpl_xattr_get+0xcc/0x1a8 [zfs] [ 2055.216742] zpl_xattr_user_get+0x68/0x90 [zfs] [ 2055.216764] __vfs_getxattr+0x60/0x80 [ 2055.216774] vfs_getxattr+0x140/0x160 [ 2055.216784] getxattr+0x9c/0x2c0 [ 2055.216794] path_getxattr+0x7c/0xd0 [ 2055.216805] __arm64_sys_getxattr+0x28/0x38 [ 2055.216815] el0_svc_common.constprop.0+0x80/0x218 [ 2055.216823] el0_svc_handler+0x34/0xa0 [ 2055.216833] el0_svc+0x10/0x2cc [ 2055.216858] INFO: task borg:5639 blocked for more than 120 seconds. [ 2055.223265] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [ 2055.230193] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.238179] borgD0 5639 4001 0x [ 2055.238193] Call trace: [ 2055.238208] __switch_to+0x104/0x170 [ 2055.238218] __schedule+0x30c/0x7c0 [ 2055.238226] schedule+0x3c/0xb8 [ 2055.238267] cv_wait_common+0x188/0x1b0 [spl] [ 2055.238303] __cv_wait+0x30/0x40 [spl] [ 2055.238530] zil_commit_impl+0x234/0xd30 [zfs] [ 2055.238752] zil_commit+0x48/0x70 [zfs] [ 2055.238975] zfs_write+0xa3c/0xb90 [zfs] [ 2055.239197] zpl_write_common_iovec+0xac/0x120 [zfs] [ 2055.239419] zpl_iter_write+0xe4/0x150 [zfs] [ 2055.239471] new_sync_write+0x100/0x1a8 [ 2055.239480] __vfs_write+0x74/0x90 [ 2055.239489] vfs_write+0xe4/0x1c8 [ 2055.239505] ksys_write+0x78/0x100 [ 2055.239514] __arm64_sys_write+0x24/0x30 [ 2055.239524] el0_svc_common.constprop.0+0x80/0x218 [ 2055.239532] el0_svc_handler+0x34/0xa0 [ 2055.239541] el0_svc+0x10/0x2cc [ 2055.239555] INFO: task kworker/u8:3:35327 blocked for more than 120 seconds. [ 2055.246754] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu [ 2055.253681] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.261670] kworker/u8:3D0 35327 2 0x0028 [ 2055.261715] Workqueue: writeback wb_workfn (flush-zfs-1) [ 2055.261728] Call trace: [ 2055.261740] __switch_to+0x104/0x170 [ 2055.261750] __schedule+0x30c/0x7c0 [ 2055.261758] schedule+0x3c/0xb8 [ 2055.261798] cv_wait_common+0x188/0x1b0 [spl] [ 2055.261834] __cv_wait+0x30/0x40 [spl] [ 2055.262059] zil_commit_impl+0x234/0xd30 [zfs] [ 2055.262284] zil_commit+0x48/0x70 [zfs]
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
@rhpot1991, could you check the firmware version of wd19tb!? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 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 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
** Tags added: oem-priority originate-from-1896145 sutton ** Changed in: oem-priority Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899304] Re: Linux 5.4.0-48 causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues
I reproduce the bug with the 5.4.0-49-generic kernel from `proposed` when running the Radeon X1950 PRO. Note: I previously joined a dmesg log file about GPU lockup, such lockup is not always logged but the GNOME Shell session is stuck anytime it is started. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899304 Title: Linux 5.4.0-48 causes GPU lockup, huge performance drop, makes GNOME desktop fail to start and games going from 70fps to 7fps, slow file loading, audio issues Status in linux package in Ubuntu: Confirmed Bug description: This system runs Ubuntu 20.04, freshly installed 3~4 months ago (July 2020). There is two kernels available on this system: - 5.4.0-47-generic - 5.4.0-48-generic With kernel 5.4.0-47-generic: - GNOME shell loads properly on Radeon X1950 PRO, - Unvanquished game runs on ATI Radeon X1950 PRO at 70 fps on 1280×720 resolution, - Unvanquished game runs on ATI Radeon 9500 at 40 fps on 640×480 resolution. Everything looks consistent with the limits and the age of the hardware. With kernel 5.4.0-48-generic: - GNOME Shell never finish to load on Radeon X1950 PRO, either a grey screen is displayed and keyboard shortcuts does not respond, or the top bar is stuck between the center and the top of the screen and the shell does not respond, or the top bar on the top of the screen but the shell does not respond, to get a desktop I run `sudo systemctl stop display-manager` then `startx /usr/bin/lxsession` from a TTY. Running GNOME Shell with startx or from a lone xterm started with startx leads to same issues. - Unvanquished game runs on ATI Radeon X1950 PRO at 7 fps on 1280×720 resolution, - Unvanquished game runs on ATI Radeon 9500 at 3 fps on 640×480 resolution. Note: for unknown reasons, GNOME Shell loads properly on the ATI Radeon 9500 but not on the Radeon X1950 PRO. Everything is slow. When the game is running, a very high load is reported by htop, which does not look like the experience seen on the 5.4.0-47-generic kernel. When the game is running cycling between windows using Alt-Tab takes a lot of second while it's immediate on 5.4.0-47-generic kernel. Also, even without the game running or on a lightweight desktop like LXDE, cycling windows is not smooth and window refreshing is slow enough to be noticeable. About the hardware, note that: - the CPU only has one core, no hyperthreading (AMD Athlon 64 FX for socket 939), - the GPUs are AGP ones using R300 and R500 technology (pre-TeraScale), - there is 3GB of DDR RAM, - there is no on-disk swap but zram-based swap in compressed ram is used, - system is stored on and boots from an USB 3.1 key plugged on an USB 2.0 port, - /tmp is a tmpfs ram disk, - CPU is set to performance profile, - the install is not really messy and not many packages are installed, this USB key is purposed for hardware/system testing and to diagnose such issues. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: illwieckz 7503 F pulseaudio CasperMD5CheckResult: skip Date: Sun Oct 11 01:47:48 2020 InstallationDate: Installed on 2020-07-09 (93 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: enp0s11 no wireless extensions. lono wireless extensions. MachineType: MSI MS-6702E ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=10314d0c-ec6b-4f7f-b926-ed8b80185331 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080011 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-6702E dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080011:bd10/12/2006:svnMSI:pnMS-6702E:pvr1.0:rvnMSI:rnMS-6702E:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By
