[Kernel-packages] [Bug 1778932] Re: rsync can trigger system crash
Hi to all. I know that is an old topic but today I faced an isue with rsync. After this command " rsync -Aavx /var/www/html/nextcloud/ /mnt/backup/nextcloudbk/nextcloud-dirbkp_`date +"%Y%m%d%t"`/ " the ubuntu server 20.04 has crashed. On every command the system response is " bash: /usr/bin/'command': No such file or directory ". Nothing works any more. Is the secont time that happens to me. Last week, it happend firs time and I don't realise that is rsync problem until I reinstalled the server and I run this command again. I even can't go in log file. Doesn't work any command. After reboot, ubuntu crashes on load. I don't think it is a repair for this. And the work begin with the reinstall of ubuntu.again. Sorry for my english. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778932 Title: rsync can trigger system crash Status in linux package in Ubuntu: Confirmed Bug description: I'm not sure how much of this is rsync or something else in my system. I can reliably trigger this using rsync to transfer files from one drive to another drive on my computer. the source is ssd and destination is mdadm raid 1 partition. will attach syslog messages. after it is triggered, the the system becomes unresponsive and requires a hard reboot. running rysnc as user, no special privileges. root@music:~# lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apt-cache policy rsync rsync: Installed: 3.1.2-2.1ubuntu1 Candidate: 3.1.2-2.1ubuntu1 Version table: *** 3.1.2-2.1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status uname -a Linux music 4.15.0-23-lowlatency #25-Ubuntu SMP PREEMPT Wed May 23 20:39:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-lowlatency 4.15.18 Uname: Linux 4.15.0-23-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 27 10:08:36 2018 InstallationDate: Installed on 2018-03-31 (87 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color LANGUAGE=en_US PATH=(custom, no user) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: papa 5200 F pulseaudio /dev/snd/controlC0: papa 5200 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ca9d6033-d98d-4fba-be24-599f112ac941 InstallationDate: Installed on 2018-03-31 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-lowlatency root=/dev/mapper/xubuntu--vg-root ro splash fsck.mode=force fsck.repair=yes vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-lowlatency N/A linux-backports-modules-4.15.0-23-lowlatency N/A linux-firmware1.173.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-23-lowlatency x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 04/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4011 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778932/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-pack
[Kernel-packages] [Bug 1898436] Re: [Toshiba SATELLITE C55-A-1M7] touchpad not working
** Summary changed: - touchpad not working + [Toshiba SATELLITE C55-A-1M7] touchpad not 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/1898436 Title: [Toshiba SATELLITE C55-A-1M7] touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input5 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input6 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04f2 Product=b3b1 Version=5716 N: Name="TOSHIBA Web Camera - HD: TOSHIB" P: Phys=usb-:00:14.0-10/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/input/input7 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input8 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input9 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input10 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input11 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input12 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input13 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input14 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input5 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/L
[Kernel-packages] [Bug 1379233] Re: [STAGING] package linux-image-3.13.0-37-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 2
I am closing this bug as Trusty has enter the ESM, please feel free to open a new one if you're still seeing any issue, thanks. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1379233 Title: [STAGING] package linux-image-3.13.0-37-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 2 Status in linux package in Ubuntu: Won't Fix Bug description: Attempting to install an update via the software updater, the kernel update failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fredo-p1830 F pulseaudio /dev/snd/seq:timidity 1288 F timidity CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Thu Oct 9 01:55:56 2014 DuplicateSignature: package:linux-image-3.13.0-37-generic:(not installed):subprocess new pre-installation script returned error exit status 2 ErrorMessage: subprocess new pre-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=ae161caf-6780-416f-891a-a390f262daf4 InstallationDate: Installed on 2013-10-26 (347 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) MachineType: TOSHIBA Satellite A135 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=36627835-8604-4d9c-a2ff-ca11c683597c ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: zram Title: [STAGING] package linux-image-3.13.0-37-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 2 UpgradeStatus: Upgraded to trusty on 2014-04-23 (168 days ago) WifiSyslog: Oct 9 01:29:25 fredop-Satellite-A135 wpa_supplicant[1126]: message repeated 14 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ] Oct 9 01:29:48 fredop-Satellite-A135 wpa_supplicant[1126]: wlan0: WPA: Group rekeying completed with 00:1b:2f:0f:1b:d0 [GTK=TKIP] Oct 9 01:31:25 fredop-Satellite-A135 wpa_supplicant[1126]: wlan0: CTRL-EVENT-SCAN-STARTED dmi.bios.date: 01/12/2009 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.90 dmi.board.name: IAKAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.90:bd01/12/2009:svnTOSHIBA:pnSatelliteA135:pvrPSAD0U-03H00P:rvnTOSHIBA:rnIAKAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite A135 dmi.product.version: PSAD0U-03H00P dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1379233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912163] [NEW] intel_vbt_decode update for parsing VBT 234+
Public bug reported: Intel deliver new VBT format for latest GPU, the driver modification is introduced by commit https://patchwork.freedesktop.org/patch/394304/?series=82482&rev=1 A upstream bug has reported for the issue: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/95 Release codename: focal ** Affects: intel-gpu-tools (Ubuntu) Importance: Undecided Status: New ** Description changed: Intel deliver new VBT format for latest GPU, the driver modification is introduced by commit https://patchwork.freedesktop.org/patch/394304/?series=82482&rev=1 A upstream bug has reported for the issue: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/95 + + Release codename: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1912163 Title: intel_vbt_decode update for parsing VBT 234+ Status in intel-gpu-tools package in Ubuntu: New Bug description: Intel deliver new VBT format for latest GPU, the driver modification is introduced by commit https://patchwork.freedesktop.org/patch/394304/?series=82482&rev=1 A upstream bug has reported for the issue: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/95 Release codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1912163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858463] Re: Desktop freezing while SSD under heavy load
This is still the case with a fully up to date Ubuntu 20.04 LTS desktop. 5.4.0-60-generic kernel. What can I do to make the bug report "complete" ? ** Changed in: linux (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858463 Title: Desktop freezing while SSD under heavy load Status in linux package in Ubuntu: Confirmed Bug description: Every time my SSD is under heavy writing load (e.g. copying large files from a USB stick, or downloading an ISO from a fast website), the entire Ubuntu (Gnome) desktop, including mouse pointer, freezes. My computer is an Asus UX410UAK with a Micron 1100 SSD. guillaume@massada:~$ sudo dmidecode | grep -i UX Version: UX410UAK.308 Product Name: UX410UAK Family: UX Product Name: UX410UAK guillaume@massada:~$ cat /proc/scsi/scsi Attached devices: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: Micron_1100_MTFD Rev: A020 Type: Direct-AccessANSI SCSI revision: 05 This is a recurring problem, and has always been with this machine (including previous kernel and Ubuntu versions, at least for the past 2 years). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 6 18:20:01 2020 InstallationDate: Installed on 2018-07-28 (526 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 1685 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam 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: ASUSTeK COMPUTER INC. UX410UAK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-25-generic N/A linux-backports-modules-5.4.0-25-generic N/A linux-firmware1.187 Tags: focal wayland-session Uname: Linux 5.4.0-25-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: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 1423 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-11 (208 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam 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: ASUST
[Kernel-packages] [Bug 1858463] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858463 Title: Desktop freezing while SSD under heavy load Status in linux package in Ubuntu: Confirmed Bug description: Every time my SSD is under heavy writing load (e.g. copying large files from a USB stick, or downloading an ISO from a fast website), the entire Ubuntu (Gnome) desktop, including mouse pointer, freezes. My computer is an Asus UX410UAK with a Micron 1100 SSD. guillaume@massada:~$ sudo dmidecode | grep -i UX Version: UX410UAK.308 Product Name: UX410UAK Family: UX Product Name: UX410UAK guillaume@massada:~$ cat /proc/scsi/scsi Attached devices: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: Micron_1100_MTFD Rev: A020 Type: Direct-AccessANSI SCSI revision: 05 This is a recurring problem, and has always been with this machine (including previous kernel and Ubuntu versions, at least for the past 2 years). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 6 18:20:01 2020 InstallationDate: Installed on 2018-07-28 (526 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 1685 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam 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: ASUSTeK COMPUTER INC. UX410UAK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-25-generic N/A linux-backports-modules-5.4.0-25-generic N/A linux-firmware1.187 Tags: focal wayland-session Uname: Linux 5.4.0-25-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: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 1423 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-11 (208 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam 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: ASUSTeK COMPUTER INC. UX410UAK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, n
[Kernel-packages] [Bug 1900391] Re: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
This is present on my system > cat /etc/os-release NAME="Ubuntu" VERSION="20.04.1 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.1 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal > uname -a Linux p9x79 5.4.0-60-generic #67-Ubuntu SMP Tue Jan 5 18:31:36 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ASUS P9X79 Pro motherboard. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1900391 Title: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled Status in linux package in Ubuntu: Confirmed Bug description: [4.589406] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled [4.589410] EDAC sbridge: Couldn't find mci handler [4.589411] EDAC sbridge: Failed to register device with error -19. but x79 doesn't have ecc ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-23-generic 5.8.0-23.24 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat2032 F pulseaudio /dev/snd/controlC0: navycat2032 F pulseaudio /dev/snd/controlC1: navycat2032 F pulseaudio CasperMD5CheckResult: skip Date: Mon Oct 19 10:19:05 2020 InstallationDate: Installed on 2020-10-07 (11 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed 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.8.0-23-generic N/A linux-backports-modules-5.8.0-23-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900391/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912033] Re: Thinkpad - add palm sensor support needed for WWAN
** Tags added: oem-priority originate-from-1911794 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912033 Title: Thinkpad - add palm sensor support needed for WWAN Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: New Bug description: [Impact] Add new palm sensor supports to Lenovo Thinkpad systems [Fix] thinkpad_acpi is updated to check palm sensor presence and its events [Test] Tested on Thinkpad systems [Where problems could occur] Low risks. Only thinkpad systems are affected. Also thinkpad systems without palm sensor and without TP_HKEY_EV_PALM_DETECTED & TP_HKEY_EV_PALM_UNDETECTED events won't be affected either. There can an issue as discussed in commit log of "thinkpad_acpi: Add palm sensor support" Note: On some platforms, because of an issue in the HW implementation, the palm sensor presence may be incorrectly advertised as always enabled even if a palm sensor is not present. The palm sensor is intended for WWAN transmission power control and should be available and correct on all WWAN enabled systems. It is not recommended to use this interface for other use cases. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1912033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902577] Re: TGL system automatically resumes from s2idle when connecting to a docking station with a monitor
** Tags added: originate-from-1912134 -- 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/1902577 Title: TGL system automatically resumes from s2idle when connecting to a docking station with a monitor Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: New Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: [Impact] TGL systems wake up automatically from s2idle when connecting to a docking station with a monitor. The wake-up events are generated when BIOS sets ALL_MONITOR_OFF for power-saving on TGL systems. [Fix] A BIOS workaround is used to skip ALL_MONITOR_OFF with an _OSI string "Linux-Dell-USB4-Wakeup". [Test] Verified on Dell's TigerLake platforms [Regression Potential] Low. This only works on platforms supporting "Linux-Dell-USB4-Wakeup". No other platforms will be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902577/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted shell textures when switching users or resuming from suspend
** Summary changed: - [nvidia] Corrupted shell textures when using multiple users + [nvidia] Corrupted shell textures when switching users or resuming from suspend ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3583 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3583 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3583 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Invalid ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged ** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: Invalid => Triaged ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: x
[Kernel-packages] [Bug 1911456] Re: Can't receive files over bluetooth unless settings dialog is open
** Package changed: gnome-control-center (Ubuntu) => gnome-user-share (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/1911456 Title: Can't receive files over bluetooth unless settings dialog is open Status in bluez package in Ubuntu: New Status in gnome-user-share package in Ubuntu: New Bug description: On 18.04 I could send files from my phone to my laptop at any time. On 20.04 I can't get files to be accepted by the laptop over bluetooth. After much frustration and experimenting, I figured out that it will work, but only if the bluetooth settings dialog is open. If the settings dialog is not open, the incoming file is rejected. If the dialog is closed after the file transfer begins, the transfer continues but the file is discarded when the transfer is complete. This is very frustrating. I need to be able to send files (mostly photos and videos) from my phone to my laptop without having to open the settings dialog on the laptop, just like I could before upgrading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1911456/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909457] Re: Support CML-S CPU + TGP PCH
** Description changed: [Impact] i915 driver gives below warnings that CML-S GPU doesn't work with TGL/RKL PCH, and the screen is blank. kernel: i915 :00:02.0: drm_WARN_ON(!IS_PLATFORM(dev_priv, INTEL_TIGERLAKE) && !IS_PLATFORM(dev_priv, INTEL_ROCKETLAKE)) [Fix] Intel provides us a new patch for this issue https://patchwork.freedesktop.org/patch/412664/ [Test] + Verified on new Dell platforms. [Where problems could occur] + The first commit reverts the patch that didn't find its way to upstream. + The second to forth commits are to enable DG1 which applied for solving conflicts. + The fifth and sixth commit splits code for EHL and JSL. + The seventh commit rename enums, no function changes. + The eighth commit is newer version of the first reverted commit. + The ninth commit adds CML CPU support on TGP PCH which fixes this issue. + According to the above explanation, + 1. the DG1 in newly enabled by commits 2 to 4, no regression could occur, + 2. the EHL and JSL commits are pretty simple and straightforward, should be safe to include, + 3. the first commit is equivalence to the eighth commit + 4. the ninth commit is pretty simple to add GEN9 into flow control, + so I think there should be no problems could occur from this patchset. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909457 Title: Support CML-S CPU + TGP PCH Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] i915 driver gives below warnings that CML-S GPU doesn't work with TGL/RKL PCH, and the screen is blank. kernel: i915 :00:02.0: drm_WARN_ON(!IS_PLATFORM(dev_priv, INTEL_TIGERLAKE) && !IS_PLATFORM(dev_priv, INTEL_ROCKETLAKE)) [Fix] Intel provides us a new patch for this issue https://patchwork.freedesktop.org/patch/412664/ [Test] Verified on new Dell platforms. [Where problems could occur] The first commit reverts the patch that didn't find its way to upstream. The second to forth commits are to enable DG1 which applied for solving conflicts. The fifth and sixth commit splits code for EHL and JSL. The seventh and eighth commits rename enums, no function changes. The ninth commit is newer version of the first reverted commit. The tenth commit adds CML CPU support on TGP PCH which fixes this issue. According to the above explanation, 1. the DG1 in newly enabled by commits 2 to 4, no regression could occur, 2. the EHL and JSL commits are pretty simple and straightforward, should be safe to include, 3. the first commit is equivalence to the ninth commit 4. the tenth commit is pretty simple to add GEN9 into flow control, so I think there should be no problems could occur from this patchset. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1909457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909457] Re: Support CML-S CPU + TGP PCH
** Description changed: [Impact] i915 driver gives below warnings that CML-S GPU doesn't work with TGL/RKL PCH, and the screen is blank. kernel: i915 :00:02.0: drm_WARN_ON(!IS_PLATFORM(dev_priv, INTEL_TIGERLAKE) && !IS_PLATFORM(dev_priv, INTEL_ROCKETLAKE)) [Fix] Intel provides us a new patch for this issue https://patchwork.freedesktop.org/patch/412664/ [Test] Verified on new Dell platforms. [Where problems could occur] The first commit reverts the patch that didn't find its way to upstream. The second to forth commits are to enable DG1 which applied for solving conflicts. The fifth and sixth commit splits code for EHL and JSL. - The seventh commit rename enums, no function changes. - The eighth commit is newer version of the first reverted commit. - The ninth commit adds CML CPU support on TGP PCH which fixes this issue. - According to the above explanation, - 1. the DG1 in newly enabled by commits 2 to 4, no regression could occur, - 2. the EHL and JSL commits are pretty simple and straightforward, should be safe to include, - 3. the first commit is equivalence to the eighth commit - 4. the ninth commit is pretty simple to add GEN9 into flow control, + The seventh and eighth commits rename enums, no function changes. + The ninth commit is newer version of the first reverted commit. + The tenth commit adds CML CPU support on TGP PCH which fixes this issue. + According to the above explanation, + 1. the DG1 in newly enabled by commits 2 to 4, no regression could occur, + 2. the EHL and JSL commits are pretty simple and straightforward, should be safe to include, + 3. the first commit is equivalence to the ninth commit + 4. the tenth commit is pretty simple to add GEN9 into flow control, so I think there should be no problems could occur from this patchset. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909457 Title: Support CML-S CPU + TGP PCH Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] i915 driver gives below warnings that CML-S GPU doesn't work with TGL/RKL PCH, and the screen is blank. kernel: i915 :00:02.0: drm_WARN_ON(!IS_PLATFORM(dev_priv, INTEL_TIGERLAKE) && !IS_PLATFORM(dev_priv, INTEL_ROCKETLAKE)) [Fix] Intel provides us a new patch for this issue https://patchwork.freedesktop.org/patch/412664/ [Test] Verified on new Dell platforms. [Where problems could occur] The first commit reverts the patch that didn't find its way to upstream. The second to forth commits are to enable DG1 which applied for solving conflicts. The fifth and sixth commit splits code for EHL and JSL. The seventh and eighth commits rename enums, no function changes. The ninth commit is newer version of the first reverted commit. The tenth commit adds CML CPU support on TGP PCH which fixes this issue. According to the above explanation, 1. the DG1 in newly enabled by commits 2 to 4, no regression could occur, 2. the EHL and JSL commits are pretty simple and straightforward, should be safe to include, 3. the first commit is equivalence to the ninth commit 4. the tenth commit is pretty simple to add GEN9 into flow control, so I think there should be no problems could occur from this patchset. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1909457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895132] Re: s390x broken with unknown syscall number on kernels < 5.8
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1895132
Title:
s390x broken with unknown syscall number on kernels < 5.8
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Bug description:
SRU Justification
Impact: On kernels prior to 5.8 when a task is in traced state (due to
audit, ptrace, or seccomp) s390x and a syscall is issued that the
kernel doesn't know about s390x will not return ENOSYS in r2 but
instead will return the syscall number. This breaks userspace all over
the place. The following program compiled on s390x will output 500
instead of -ENOSYS:
root@test:~# cat test.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
static inline int dummy_inline_asm(void)
{
register long r1 asm("r1") = 500;
register long r2 asm("r2") = -1;
register long r3 asm("r3") = -1;
register long r4 asm("r4") = -1;
register long r5 asm("r5") = -1;
register long __res_r2 asm("r2");
asm volatile(
"svc 0\n\t"
: "=d"(__res_r2)
: "d"(r1), "0"(r2), "d"(r3), "d"(r4), "d"(r5)
: "memory");
return (int) __res_r2;
}
static inline int dummy_syscall(void)
{
return syscall(500, -1, -1, -1, -1);
}
int main(int argc, char *argv[])
{
printf("Uhm: %d\n", dummy_inline_asm());
printf("Uhm: %d\n", dummy_syscall());
exit(EXIT_SUCCESS);
}
This breaks LXD on s390x currently completely as well as strace.
Fix: Backport
commit cd29fa798001075a554b978df3a64e6656c25794
Author: Sven Schnelle
Date: Fri Mar 6 13:18:31 2020 +0100
s390/ptrace: return -ENOSYS when invalid syscall is supplied
The current code returns the syscall number which an invalid
syscall number is supplied and tracing is enabled. This makes
the strace testsuite fail.
Signed-off-by: Sven Schnelle
Signed-off-by: Vasily Gorbik
which got released with 5.8. The commit missed to Cc stable and
although I've asked Sven to include it in stable I'm not sure when or
if it will show up there.
Regression Potential: Limited to s390x.
Test Case: The reproducer given above needs to output -ENOSYS instead
of 500.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895132/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] Re: No sound on Dell Latitude E6420 with Kernel 5.8.0
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Confirmed Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906384] Comment bridged from LTC Bugzilla
--- Comment From y...@cn.ibm.com 2021-01-18 04:38 EDT--- Thanks! We will try this out and see if that works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906384 Title: [UBUNTU 18.04] lvm boot failure Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Bug description: ---Problem Description--- boot failure with LVM root disk ---uname output--- 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:07:52 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = 8561 LT1 ---System Hang--- Boot failure with LVM root disk and enter emergency shell ---Debugger--- A debugger is not configured ---Steps to Reproduce--- boot the system *Additional Instructions for Chee Ye/y...@cn.ibm.com: -Attach: /proc/partitions /proc/mounts/ /etc/lvm/lvm.conf dmsetup ls dmsetup table dmsetup targets dmsetup version lvm version During boot, got below error message and then entered emergency shell. I am attaching part of the console log from HMC. "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah be" "cause device was seen first." "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah be" "cause device was seen first." "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah be" "cause device was seen first." "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 be" "cause device was seen first." "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 be" "cause device was seen first." "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 be" "cause device was seen first." "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn be" "cause device was seen first." "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn be" "cause device was seen first." "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn be" "cause device was seen first." "Cannot activate LVs in VG ISVCL1-vg while PVs appear on duplicate devices." done. "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: error opening /dev/md?*: No such file or directory" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" done. "Gave up waiting for root file system device. Common problems:" "- Boot args (cat /proc/cmdline)" "- Check rootdelay= (did the system wait long enough?)" "- Missing modules (cat /proc/modules; ls /dev)" "chvt: can't open console" "ALERT! /dev/mapper/ISVCL1--vg-root does not exist. Dropping to a shell!" "Couldn't get a file descriptor referring to the console" "/scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o" "r address" "/scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad" dress "/scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or" address "/scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad" dress "/scripts/panic/console_setup: line 1: can't create /dev/tty3: No such devi
[Kernel-packages] [Bug 1902588] Update Released
The verification of the Stable Release Update for zfs-linux 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 zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1902588 Title: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Groovy: Fix Released Status in zfs-linux source package in Hirsute: Fix Released Bug description: == SRU Justification Focal == zfs mount -a when run on a nonempty mountpoint causes a double free, memory corruption, and a segfault. == Impact == Double free and memory corruption in ZFS when run as root and attempting to mount all. While running this I observed other ZFS volumes randomly unmounting, and mount points owner being spuriously zeroed (set to root). == Fix == https://github.com/openzfs/zfs/commit/d1b84da8c1a69c084f04b504beefe804591bca07 == Test == Steps are laid out in the ZFS issue: https://github.com/openzfs/zfs/issues/9560 == Regression Potential == Limited to the behavior of zfs mount when a previous attempt to mount has failed, or is still in progress. Changes the behavior in that case to failure, instead of double-free. Example case of running into this bug, with dmesg: https://pastebin.com/YRXW8WgM $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.4 Candidate: 0.8.3-1ubuntu12.4 Version table: *** 0.8.3-1ubuntu12.4 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894329] Update Released
The verification of the Stable Release Update for zfs-linux 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 zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
Fix Released
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Fix Committed
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Fix Released
Bug description:
[Impact]
* Users can’t revert to previous snapshots when enabling the hw enablement
stack kernel on focal or using any more recent version.
* The option is available on grub and will let you with a broken system,
partially cloned.
[Test Case]
* Boot on a system, using ZFS and ZSys.
* In grub, select "History" entry
* Select one of the "Revert" option: the system should boot after being
reverted with an older version.
[Where problems could occur]
* The code is in the initramfs, where the generated id suffix for all our
ZFS datasets was empty due to new coreutils/kernels.
* We replace dd with another way (more robust and simple) for generating
this ID.
-
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912037] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Confirmed Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christerw 1637 F pipewire-media- /dev/snd/seq:christerw 1629 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Feren OS 20.04 InstallationDate: Installed on 2020-03-06 (317 days ago) InstallationMedia: Feren OS 2019.12 "Yttrium" - Release amd64 (20191225) MachineType: Dell Inc. Latitude E6420 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=a48b61f5-bd7c-4a33-a5e5-6376ece701e3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.8.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 10/18/2011 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:br4.6:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911359] Re: Boot fails: failed to validate module [nls_iso8859_1] BTF: -22
This is fixed in Ubuntu-5.11.0-4.5. We can close this for now. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911359 Title: Boot fails: failed to validate module [nls_iso8859_1] BTF: -22 Status in linux package in Ubuntu: Fix Committed Bug description: I just updated to an unstable kernel build from the kernels team Repo it´s the 5.11-2.3 package (5.11 RC3) The mount of /dev/boot fails with a message: IO charset iso8859-1 not found this is probably due to the kernel being unable to load the nls_iso8859-1 module. I see multiple messages with BPF:No data and for the nls_iso8859-1 module a message: failed to validate module [nls_iso8859_1] BTF: -22 this is probably introduced by this patch: https://lkml.org/lkml/2020/11/6/1143 I don´t undestand what BTF validation is and whether this is an issue with linux 5.11-rc3 or with how the kernel modules are packaged in Ubuntu. My machine is a Renoir (zen2) based Acer Laptop running in UEFI mode, with a fat32 /boot partition and a ext4 / root partition. The root partition gets mounted, but once the /boot should be mounted, this fails with the mentioned error.. Other modules seem to load fine, things like "amdgpu" are already loaded! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902588] Re: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty
This bug was fixed in the package zfs-linux - 0.8.4-1ubuntu11.1 --- zfs-linux (0.8.4-1ubuntu11.1) groovy; urgency=medium [ Didier Roche ] [ Jean-Baptiste Lallement ] * Generate clone uuid without dd which is flagged as having an executable stack. Thanks Usarin Heininga for the patch (LP: #1894329) [ Andrea Righi ] * fix potential user-space double free when running "zfs mount -a" (LP: #1902588) - 4702-Revert-Let-zfs-mount-all-tolerate-in-progress-mounts.patch -- Colin Ian King Mon, 30 Nov 2020 19:00:00 + ** Changed in: zfs-linux (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1902588 Title: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Groovy: Fix Released Status in zfs-linux source package in Hirsute: Fix Released Bug description: == SRU Justification Focal == zfs mount -a when run on a nonempty mountpoint causes a double free, memory corruption, and a segfault. == Impact == Double free and memory corruption in ZFS when run as root and attempting to mount all. While running this I observed other ZFS volumes randomly unmounting, and mount points owner being spuriously zeroed (set to root). == Fix == https://github.com/openzfs/zfs/commit/d1b84da8c1a69c084f04b504beefe804591bca07 == Test == Steps are laid out in the ZFS issue: https://github.com/openzfs/zfs/issues/9560 == Regression Potential == Limited to the behavior of zfs mount when a previous attempt to mount has failed, or is still in progress. Changes the behavior in that case to failure, instead of double-free. Example case of running into this bug, with dmesg: https://pastebin.com/YRXW8WgM $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.4 Candidate: 0.8.3-1ubuntu12.4 Version table: *** 0.8.3-1ubuntu12.4 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
This bug was fixed in the package zfs-linux - 0.8.4-1ubuntu11.1
---
zfs-linux (0.8.4-1ubuntu11.1) groovy; urgency=medium
[ Didier Roche ]
[ Jean-Baptiste Lallement ]
* Generate clone uuid without dd which is flagged as having an executable
stack. Thanks Usarin Heininga for the patch (LP: #1894329)
[ Andrea Righi ]
* fix potential user-space double free when running "zfs mount -a"
(LP: #1902588)
- 4702-Revert-Let-zfs-mount-all-tolerate-in-progress-mounts.patch
-- Colin Ian King Mon, 30 Nov 2020 19:00:00
+
** Changed in: zfs-linux (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
Fix Released
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Fix Committed
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Fix Released
Bug description:
[Impact]
* Users can’t revert to previous snapshots when enabling the hw enablement
stack kernel on focal or using any more recent version.
* The option is available on grub and will let you with a broken system,
partially cloned.
[Test Case]
* Boot on a system, using ZFS and ZSys.
* In grub, select "History" entry
* Select one of the "Revert" option: the system should boot after being
reverted with an older version.
[Where problems could occur]
* The code is in the initramfs, where the generated id suffix for all our
ZFS datasets was empty due to new coreutils/kernels.
* We replace dd with another way (more robust and simple) for generating
this ID.
-
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895132] Re: s390x broken with unknown syscall number on kernels < 5.8
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Status: New => Fix Committed
** Tags added: s390x
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1895132
Title:
s390x broken with unknown syscall number on kernels < 5.8
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Bug description:
SRU Justification
Impact: On kernels prior to 5.8 when a task is in traced state (due to
audit, ptrace, or seccomp) s390x and a syscall is issued that the
kernel doesn't know about s390x will not return ENOSYS in r2 but
instead will return the syscall number. This breaks userspace all over
the place. The following program compiled on s390x will output 500
instead of -ENOSYS:
root@test:~# cat test.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
static inline int dummy_inline_asm(void)
{
register long r1 asm("r1") = 500;
register long r2 asm("r2") = -1;
register long r3 asm("r3") = -1;
register long r4 asm("r4") = -1;
register long r5 asm("r5") = -1;
register long __res_r2 asm("r2");
asm volatile(
"svc 0\n\t"
: "=d"(__res_r2)
: "d"(r1), "0"(r2), "d"(r3), "d"(r4), "d"(r5)
: "memory");
return (int) __res_r2;
}
static inline int dummy_syscall(void)
{
return syscall(500, -1, -1, -1, -1);
}
int main(int argc, char *argv[])
{
printf("Uhm: %d\n", dummy_inline_asm());
printf("Uhm: %d\n", dummy_syscall());
exit(EXIT_SUCCESS);
}
This breaks LXD on s390x currently completely as well as strace.
Fix: Backport
commit cd29fa798001075a554b978df3a64e6656c25794
Author: Sven Schnelle
Date: Fri Mar 6 13:18:31 2020 +0100
s390/ptrace: return -ENOSYS when invalid syscall is supplied
The current code returns the syscall number which an invalid
syscall number is supplied and tracing is enabled. This makes
the strace testsuite fail.
Signed-off-by: Sven Schnelle
Signed-off-by: Vasily Gorbik
which got released with 5.8. The commit missed to Cc stable and
although I've asked Sven to include it in stable I'm not sure when or
if it will show up there.
Regression Potential: Limited to s390x.
Test Case: The reproducer given above needs to output -ENOSYS instead
of 500.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1895132/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912188] [NEW] Load growing continously
Public bug reported: Recently load started growing with no end. After a while random processes become zombies. 11:32:22 up 26 min, 1 user, load average: 196.16, 186.30, 138.60 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-generic 5.8.0.36.40+21.04.38 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tompos 2361 F pulseaudio CasperMD5CheckResult: skip Date: Mon Jan 18 11:30:11 2021 InstallationDate: Installed on 2020-12-31 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP EliteBook x360 1030 G3 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-36-generic root=UUID=086c6507-b389-4208-a8bc-d0b99071b5cd ro rootflags=subvol=@ 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.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.194 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-01-02 (15 days ago) dmi.bios.date: 10/22/2020 dmi.bios.release: 14.1 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.14.01 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.4E.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 20.78 dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.14.01:bd10/22/2020:br14.1:efr20.78:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.4E.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 5DT80EC#BH4 dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912188 Title: Load growing continously Status in linux package in Ubuntu: New Bug description: Recently load started growing with no end. After a while random processes become zombies. 11:32:22 up 26 min, 1 user, load average: 196.16, 186.30, 138.60 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-generic 5.8.0.36.40+21.04.38 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tompos 2361 F pulseaudio CasperMD5CheckResult: skip Date: Mon Jan 18 11:30:11 2021 InstallationDate: Installed on 2020-12-31 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP EliteBook x360 1030 G3 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-36-generic root=UUID=086c6507-b389-4208-a8bc-d0b99071b5cd ro rootflags=subvol=@ 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.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.194 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-01-02 (15 days ago) dmi.bios.date: 10/22/2020 dmi.bios.release: 14.1 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.14.01 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.4E.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 20.78 dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.14.01:bd10/22/2020:br14.1:efr20.78:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.4E.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 5DT80EC#BH4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873325] Re: update-initramfs complains of missing amdgpu firmware files
I have this on Ubuntu 20.10, still. Kernel: 5.8.0-25-generic linux-firmware: 1.190.3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873325 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: amdgpu references firmware files in modinfo which have not been supplied to linux-firmware. This causes update-initramfs to generate "Possible missing firmware" warnings. Fix: Since the firmware is not available, all we can do is remove the files from modinfo. Test Case: Confirm that update-initramfs no longer produces the warnings. Regression Potential: Low. If someone had managed to obtain these files they will no longer be added to the initramfs, potentially causing regressions for these users. This would be an atypical situation. --- Ubuntu 20.04 during initramfs update reports missing firmware files: W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module amdgpu Kernel: 5.4.0-24-generic linux-firmware: 1.187 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873325/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912188] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912188 Title: Load growing continously Status in linux package in Ubuntu: Confirmed Bug description: Recently load started growing with no end. After a while random processes become zombies. 11:32:22 up 26 min, 1 user, load average: 196.16, 186.30, 138.60 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-generic 5.8.0.36.40+21.04.38 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tompos 2361 F pulseaudio CasperMD5CheckResult: skip Date: Mon Jan 18 11:30:11 2021 InstallationDate: Installed on 2020-12-31 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP EliteBook x360 1030 G3 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-36-generic root=UUID=086c6507-b389-4208-a8bc-d0b99071b5cd ro rootflags=subvol=@ 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.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.194 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-01-02 (15 days ago) dmi.bios.date: 10/22/2020 dmi.bios.release: 14.1 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.14.01 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.4E.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 20.78 dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.14.01:bd10/22/2020:br14.1:efr20.78:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.4E.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 5DT80EC#BH4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912188] Re: Load growing continously
I don't experience the same issue with 5.8.0-33-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/1912188 Title: Load growing continously Status in linux package in Ubuntu: Confirmed Bug description: Recently load started growing with no end. After a while random processes become zombies. 11:32:22 up 26 min, 1 user, load average: 196.16, 186.30, 138.60 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-generic 5.8.0.36.40+21.04.38 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tompos 2361 F pulseaudio CasperMD5CheckResult: skip Date: Mon Jan 18 11:30:11 2021 InstallationDate: Installed on 2020-12-31 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP EliteBook x360 1030 G3 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-36-generic root=UUID=086c6507-b389-4208-a8bc-d0b99071b5cd ro rootflags=subvol=@ 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.8.0-36-generic N/A linux-backports-modules-5.8.0-36-generic N/A linux-firmware1.194 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-01-02 (15 days ago) dmi.bios.date: 10/22/2020 dmi.bios.release: 14.1 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.14.01 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.4E.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 20.78 dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.14.01:bd10/22/2020:br14.1:efr20.78:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.4E.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 5DT80EC#BH4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912194] [NEW] Hirsute update: v5.10.8 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.10.8 upstream stable release from git://git.kernel.org/ Linux 5.10.8 tools headers UAPI: Sync linux/fscrypt.h with the kernel sources drm/panfrost: Remove unused variables in panfrost_job_close() regmap: debugfs: Fix a reversed if statement in regmap_debugfs_init() net: drop bogus skb with CHECKSUM_PARTIAL and offset beyond end of trimmed packet block: fix use-after-free in disk_part_iter_next can: isotp: isotp_getname(): fix kernel information leak block/rnbd-clt: avoid module unload race with close confirmation xsk: Rollback reservation at NETDEV_TX_BUSY xsk: Fix race in SKB mode transmit with shared cq KVM: arm64: Don't access PMCR_EL0 when no PMU is available selftests: fib_nexthops: Fix wrong mausezahn invocation net: mvneta: fix error message when MTU too large for XDP drm/i915/dp: Track pm_qos per connector net: mvpp2: disable force link UP during port init procedure regulator: qcom-rpmh-regulator: correct hfsmps515 definition arm64: cpufeature: remove non-exist CONFIG_KVM_ARM_HOST wan: ds26522: select CONFIG_BITREVERSE regmap: debugfs: Fix a memory leak when calling regmap_attach_dev net/mlx5e: Fix two double free cases net/mlx5e: Fix memleak in mlx5e_create_l2_table_groups nvme-tcp: Fix possible race of io_work and direct send bpftool: Fix compilation failure for net.o with older glibc iommu/intel: Fix memleak in intel_irq_remapping_alloc iommu/vt-d: Fix misuse of ALIGN in qi_flush_piotlb() zonefs: select CONFIG_CRC32 lightnvm: select CONFIG_CRC32 block: rsxx: select CONFIG_CRC32 wil6210: select CONFIG_CRC32 phy: dp83640: select CONFIG_CRC32 qed: select CONFIG_CRC32 arm64: mm: Fix ARCH_LOW_ADDRESS_LIMIT when !CONFIG_ZONE_DMA dmaengine: xilinx_dma: fix mixed_enum_type coverity warning dmaengine: xilinx_dma: fix incompatible param warning in _child_probe() dmaengine: xilinx_dma: check dma_async_device_register return value dmaengine: milbeaut-xdmac: Fix a resource leak in the error handling path of the probe function dmaengine: mediatek: mtk-hsdma: Fix a resource leak in the error handling path of the probe function interconnect: qcom: fix rpmh link failures interconnect: imx: Add a missing of_node_put after of_device_is_available bcache: set bcache device into read-only mode for BCH_FEATURE_INCOMPAT_OBSO_LARGE_BUCKET i2c: mediatek: Fix apdma and i2c hand-shake timeout i2c: i801: Fix the i2c-mux gpiod_lookup_table not being properly terminated spi: stm32: FIFO threshold level - fix align packet size spi: spi-geni-qcom: Fix geni_spi_isr() NULL dereference in timeout case cpufreq: powernow-k8: pass policy rather than use cpufreq_cpu_get() spi: spi-geni-qcom: Fail new xfers if xfer/cancel/abort pending can: kvaser_pciefd: select CONFIG_CRC32 can: m_can: m_can_class_unregister(): remove erroneous m_can_clk_stop() can: tcan4x5x: fix bittiming const, use common bittiming from m_can driver selftests/bpf: Clarify build error if no vmlinux dmaengine: dw-edma: Fix use after free in dw_edma_alloc_chunk() i2c: sprd: use a specific timeout to avoid system hang up issue ARM: OMAP2+: omap_device: fix idling of devices during probe fanotify: Fix sys_fanotify_mark() on native x86-32 HID: wacom: Fix memory leakage caused by kfifo_alloc ionic: start queues before announcing link up scsi: lpfc: Fix variable 'vport' set but not used in lpfc_sli4_abts_err_handler() net/mlx5: Check if lag is supported before creating one net/mlx5e: In skb build skip setting mark in switchdev mode net/mlx5e: ethtool, Fix restriction of autoneg with 56G net/mlx5: Use port_num 1 instead of 0 when delete a RoCE address net: dsa: lantiq_gswip: Exclude RMII from modes that report 1 GbE s390/qeth: fix L2 header access in qeth_l3_osa_features_check() s390/qeth: fix locking for discipline setup / removal s390/qeth: fix deadlock during recovery nexthop: Bounce NHA_GATEWAY in FDB nexthop groups nexthop: Unlink nexthop group entry in error path nexthop: Fix off-by-one error in error path octeontx2-af: fix memory leak of lmac and lmac->name chtls: Fix chtls resources release sequence chtls: Added a check to avoid NULL pointer dereference chtls: Replace skb_dequeue with skb_peek chtls: Avoid unnecessary freeing of oreq pointer chtls: Fix panic when route to peer not configured chtls: Remove invalid set_tcb call chtls: Fix hardware tid leak net: ip: always refragment ip defragmented packets net: fix pmtu check in nopmtudisc mode tools: selftests: add test for changing routes with PTMU exceptions net: ipv6: fib: flush exceptions when purging route ptp: p
[Kernel-packages] [Bug 1904566] Re: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe-5.4 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Bug description: Hi, it isn't easy to describe but i will try and give you all information which seem to interfer with the bug .. Sorry, my system is running with german language output. First my environment : Description: Ubuntu 18.04.5 LTS Release: 18.04 Kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa: $ apt list --installed|grep -i alsa alsa-base/bionic,bionic,now 1.0.25+dfsg-0ubuntu5 all [installiert] alsa-utils/bionic,now 1.1.3-1ubuntu1 amd64 [installiert] libsox-fmt-alsa/bionic-updates,bionic-security,now 14.4.2-3ubuntu0.18.04.1 amd64 [Installiert,automatisch] libzita-alsa-pcmi0/bionic,now 0.2.0-4ubuntu2 amd64 [Installiert,automatisch] jackd: apt list --installed|grep -i jackd jackd/bionic,bionic,now 5 all [Installiert,automatisch] jackd2/bionic,now 1.9.12~dfsg-2 amd64 [Installiert,automatisch] libjack-jackd2-0/bionic,now 1.9.12~dfsg-2 amd64 [Installiert,automatisch] libjack-jackd2-dev/bionic,now 1.9.12~dfsg-2 amd64 [installiert] My interface (Omega) : $ aplay -l Liste der Hardware-Geräte (PLAYBACK) Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC887-VD Analog [ALC887-VD Analog] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 1: ALC887-VD Digital [ALC887-VD Digital] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 3: HDMI 0 [HDMI 0] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 7: HDMI 1 [HDMI 1] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: Omega [Lexicon Omega], Gerät 0: USB Audio [USB Audio] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: Omega [Lexicon Omega], Gerät 1: USB Audio [USB Audio #1] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 The problem: I try to record some audio, using the usb-audio-interface Lexicon Omega. This interface has 4 capture channels, but all efforts to get them working/configured failed. Here is the commandline wich is working (but only two capture-channels !) $ /usr/bin/jackd -T -ndefault -dalsa -r4800 -p256 -n3 H -D -d hw:Omega -i2 -o2 jackdmp 1.9.12 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2016 Grame. Copyright 2016-2017 Filipe Coelho. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" audio_reservation_init Acquire audio card Audio1 creating alsa driver ... hw:Omega|hw:Omega|256|3|4800|2|2|nomon|swmeter|-|32bit configuring for 4800Hz, period = 256 frames (53.3 ms), buffer = 3 periods ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format ALSA: use 3 periods for capture ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format ALSA: use 3 periods for playback The same with 4 capture-channels fails: $ /usr/bin/jackd -T -ndefault -dalsa -r4800 -p256 -n3 H -D -d hw:Omega -i4 -o2 jackdmp 1.9.12 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2016 Grame. Copyright 2016-2017 Filipe Coelho. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" audio_reservation_init Acquire audio card Audio1 creating alsa driver ... hw:Omega|hw:Omega|256|3|4800|4|2|nomon|swmeter|-|32bit configuring for 4800Hz, period = 256 frames (53.3 ms), buffer = 3 periods ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format ALSA: cannot set channel count to 4 for capture ALSA: cannot configure capture channel JackTemporaryException : now quits... Released audio card Audio1 audio_reservation_finish Cannot initialize driver JackServer::Open failed with -1 Failed to open server So, one could say the interface is broken, but i tested on an older system (Ubuntustudio 16.04): $ uname -a 4.10.0-42-lowlatency #46~16.04.1-Ubuntu SMP PREEMPT Mon Dec 4 17:13:40 UTC 2017 x86_64 x86_64 x86_64 GNU/
[Kernel-packages] [Bug 1912193] [NEW] Hirsute update: v5.10.7 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.10.7 upstream stable release
from git://git.kernel.org/
Linux 5.10.7
scsi: target: Fix XCOPY NAA identifier lookup
rtlwifi: rise completion at the last step of firmware callback
xsk: Fix memory leak for failed bind
KVM: x86: fix shift out of bounds reported by UBSAN
x86/mtrr: Correct the range check before performing MTRR type lookups
dmaengine: idxd: off by one in cleanup code
netfilter: nft_dynset: report EOPNOTSUPP on missing set feature
netfilter: xt_RATEEST: reject non-null terminated string from userspace
netfilter: ipset: fix shift-out-of-bounds in htable_bits()
netfilter: x_tables: Update remaining dereference to RCU
ARM: dts: OMAP3: disable AES on N950/N9
net/mlx5e: Fix SWP offsets when vlan inserted by driver
bcache: introduce BCH_FEATURE_INCOMPAT_LOG_LARGE_BUCKET_SIZE for large bucket
bcache: check unsupported feature sets for bcache register
bcache: fix typo from SUUP to SUPP in features.h
drm/i915: clear the gpu reloc batch
drm/i915: clear the shadow batch
arm64: link with -z norelro for LLD or aarch64-elf
dmabuf: fix use-after-free of dmabuf's file->f_inode
Revert "device property: Keep secondary firmware node secondary by type"
btrfs: send: fix wrong file path when there is an inode with a pending rmdir
btrfs: qgroup: don't try to wait flushing if we're already holding a transaction
iommu/vt-d: Move intel_iommu info from struct intel_svm to struct intel_svm_dev
ALSA: hda/realtek: Add two "Intel Reference board" SSID in the ALC256.
ALSA: hda/realtek: Enable mute and micmute LED on HP EliteBook 850 G7
ALSA: hda/realtek: Add mute LED quirk for more HP laptops
ALSA: hda/realtek - Fix speaker volume control on Lenovo C940
ALSA: hda/conexant: add a new hda codec CX11970
ALSA: hda/via: Fix runtime PM for Clevo W35xSS
blk-iocost: fix NULL iocg deref from racing against initialization
x86/resctrl: Don't move a task to the same resource group
x86/resctrl: Use an IPI instead of task_work_add() to update PQR_ASSOC MSR
KVM: x86/mmu: Ensure TDP MMU roots are freed after yield
kvm: check tlbs_dirty directly
KVM: x86/mmu: Get root level from walkers when retrieving MMIO SPTE
KVM: x86/mmu: Use -1 to flag an undefined spte in get_mmio_spte()
x86/mm: Fix leak of pmd ptlock
mm: make wait_on_page_writeback() wait for multiple pending writebacks
hwmon: (amd_energy) fix allocation of hwmon_channel_info config
USB: serial: keyspan_pda: remove unused variable
usb: gadget: configfs: Fix use-after-free issue with udc_name
usb: gadget: configfs: Preserve function ordering after bind failure
usb: gadget: Fix spinlock lockup on usb_function_deactivate
USB: gadget: legacy: fix return error code in acm_ms_bind()
usb: gadget: u_ether: Fix MTU size mismatch with RX packet size
usb: gadget: function: printer: Fix a memory leak for interface descriptor
usb: gadget: f_uac2: reset wMaxPacketSize
USB: Gadget: dummy-hcd: Fix shift-out-of-bounds bug
usb: gadget: select CONFIG_CRC32
ALSA: usb-audio: Fix UBSAN warnings for MIDI jacks
USB: usblp: fix DMA to stack
USB: yurex: fix control-URB timeout handling
USB: serial: option: add Quectel EM160R-GL
USB: serial: option: add LongSung M5710 module support
USB: serial: iuu_phoenix: fix DMA from stack
usb: uas: Add PNY USB Portable SSD to unusual_uas
usb: usbip: vhci_hcd: protect shift size
USB: xhci: fix U1/U2 handling for hardware with XHCI_INTEL_HOST quirk set
usb: chipidea: ci_hdrc_imx: add missing put_device() call in
usbmisc_get_init_data()
usb: dwc3: ulpi: Fix USB2.0 HS/FS/LS PHY suspend regression
usb: dwc3: ulpi: Replace CPU-based busyloop with Protocol-based one
usb: dwc3: ulpi: Use VStsDone to detect PHY regs access completion
usb: dwc3: gadget: Clear wait flag on dequeue
usb: dwc3: gadget: Restart DWC3 gadget when enabling pullup
usb: dwc3: meson-g12a: disable clk on error handling path in probe
usb: typec: intel_pmc_mux: Configure HPD first for HPD+IRQ request
USB: cdc-wdm: Fix use after free in service_outstanding_interrupt().
USB: cdc-acm: blacklist another IR Droid device
usb: gadget: enable super speed plus
staging: mt7621-dma: Fix a resource leak in an error handling path
Staging: comedi: Return -EFAULT if copy_to_user() fails
powerpc: Handle .text.{hot,unlikely}.* in linker script
crypto: asym_tpm: correct zero out potential secrets
crypto: ecdh - avoid buffer overflow in ecdh_set_secret()
scsi: block: Do not accept any requests while suspended
scsi: block: Remove RQF_PREEMPT and BLK_MQ_REQ_PREEMPT
Bluetooth: revert: hci_h5: close serdev device and free hu in h5_close
kbuil
[Kernel-packages] [Bug 1904566] Re: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture)
Hello This bug affect me too regrettable that this interface work like a charm until ubuntu 18.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/1904566 Title: jackd/alsa: only 2 channels of 4 found on usb-interface Lexicon Omega (ALSA: cannot set channel count to 4 for capture) Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Bug description: Hi, it isn't easy to describe but i will try and give you all information which seem to interfer with the bug .. Sorry, my system is running with german language output. First my environment : Description: Ubuntu 18.04.5 LTS Release: 18.04 Kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa: $ apt list --installed|grep -i alsa alsa-base/bionic,bionic,now 1.0.25+dfsg-0ubuntu5 all [installiert] alsa-utils/bionic,now 1.1.3-1ubuntu1 amd64 [installiert] libsox-fmt-alsa/bionic-updates,bionic-security,now 14.4.2-3ubuntu0.18.04.1 amd64 [Installiert,automatisch] libzita-alsa-pcmi0/bionic,now 0.2.0-4ubuntu2 amd64 [Installiert,automatisch] jackd: apt list --installed|grep -i jackd jackd/bionic,bionic,now 5 all [Installiert,automatisch] jackd2/bionic,now 1.9.12~dfsg-2 amd64 [Installiert,automatisch] libjack-jackd2-0/bionic,now 1.9.12~dfsg-2 amd64 [Installiert,automatisch] libjack-jackd2-dev/bionic,now 1.9.12~dfsg-2 amd64 [installiert] My interface (Omega) : $ aplay -l Liste der Hardware-Geräte (PLAYBACK) Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC887-VD Analog [ALC887-VD Analog] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 1: ALC887-VD Digital [ALC887-VD Digital] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 3: HDMI 0 [HDMI 0] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: PCH [HDA Intel PCH], Gerät 7: HDMI 1 [HDMI 1] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: Omega [Lexicon Omega], Gerät 0: USB Audio [USB Audio] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: Omega [Lexicon Omega], Gerät 1: USB Audio [USB Audio #1] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 The problem: I try to record some audio, using the usb-audio-interface Lexicon Omega. This interface has 4 capture channels, but all efforts to get them working/configured failed. Here is the commandline wich is working (but only two capture-channels !) $ /usr/bin/jackd -T -ndefault -dalsa -r4800 -p256 -n3 H -D -d hw:Omega -i2 -o2 jackdmp 1.9.12 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2016 Grame. Copyright 2016-2017 Filipe Coelho. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" audio_reservation_init Acquire audio card Audio1 creating alsa driver ... hw:Omega|hw:Omega|256|3|4800|2|2|nomon|swmeter|-|32bit configuring for 4800Hz, period = 256 frames (53.3 ms), buffer = 3 periods ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format ALSA: use 3 periods for capture ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format ALSA: use 3 periods for playback The same with 4 capture-channels fails: $ /usr/bin/jackd -T -ndefault -dalsa -r4800 -p256 -n3 H -D -d hw:Omega -i4 -o2 jackdmp 1.9.12 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2016 Grame. Copyright 2016-2017 Filipe Coelho. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" audio_reservation_init Acquire audio card Audio1 creating alsa driver ... hw:Omega|hw:Omega|256|3|4800|4|2|nomon|swmeter|-|32bit configuring for 4800Hz, period = 256 frames (53.3 ms), buffer = 3 periods ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format ALSA: cannot set channel count to 4 for capture ALSA: cannot configure capture channel JackTemporaryException : now quits... Released audio card Audio1 audio_reservation_finish Cannot initialize driver JackServer::Open failed with -1 Failed to open server So, one could say the interface is broken, but i tested on an older system (Ubuntustudio 16.04): $ uname -a 4.10.0-42-lowlatency #46~16.04.1-Ubuntu SMP PREEMPT Mon Dec 4 17:13:40 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ apt list --installed|grep -i a
[Kernel-packages] [Bug 1912198] [NEW] package linux-firmware 1.187.8 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: ~$ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 ~$ uname -a Linux x 5.8.0-38-generic #43~20.04.1-Ubuntu SMP Tue Jan 12 16:39:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ~$ sudo apt-cache policy linux-firmware linux-firmware: Installed: 1.187.8 Candidate: 1.187.8 Version table: *** 1.187.8 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages BELOW ARE THE COPY OF WHAT EXACTLY HAPPENED WHEN I RAN APT UPGRADE. === ~$ sudo apt list --upgradable Listing... Done libnetplan0/focal-updates 0.101-0ubuntu3~20.04.2 amd64 [upgradable from: 0.100-0ubuntu4~20.04.3] libnss-systemd/focal-updates 245.4-4ubuntu3.4 amd64 [upgradable from: 245.4-4ubuntu3.3] libpam-systemd/focal-updates 245.4-4ubuntu3.4 amd64 [upgradable from: 245.4-4ubuntu3.3] libsystemd0/focal-updates 245.4-4ubuntu3.4 amd64 [upgradable from: 245.4-4ubuntu3.3] libudev1/focal-updates 245.4-4ubuntu3.4 amd64 [upgradable from: 245.4-4ubuntu3.3] linux-firmware/focal-updates,focal-updates 1.187.8 all [upgradable from: 1.187.7] netplan.io/focal-updates 0.101-0ubuntu3~20.04.2 amd64 [upgradable from: 0.100-0ubuntu4~20.04.3] systemd-sysv/focal-updates 245.4-4ubuntu3.4 amd64 [upgradable from: 245.4-4ubuntu3.3] systemd-timesyncd/focal-updates 245.4-4ubuntu3.4 amd64 [upgradable from: 245.4-4ubuntu3.3] systemd/focal-updates 245.4-4ubuntu3.4 amd64 [upgradable from: 245.4-4ubuntu3.3] udev/focal-updates 245.4-4ubuntu3.4 amd64 [upgradable from: 245.4-4ubuntu3.3] ~$ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: libnetplan0 libnss-systemd libpam-systemd libsystemd0 libudev1 linux-firmware netplan.io systemd systemd-sysv systemd-timesyncd udev 11 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 108 MB of archives. After this operation, 72.7 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libnss-systemd amd64 245.4-4ubuntu3.4 [95.9 kB] Get:2 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 udev amd64 245.4-4ubuntu3.4 [1,365 kB] Get:3 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libudev1 amd64 245.4-4ubuntu3.4 [80.3 kB] Get:4 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 systemd-sysv amd64 245.4-4ubuntu3.4 [10.3 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 systemd-timesyncd amd64 245.4-4ubuntu3.4 [28.1 kB] Get:6 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libpam-systemd amd64 245.4-4ubuntu3.4 [186 kB] Get:7 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 systemd amd64 245.4-4ubuntu3.4 [3,805 kB] Get:8 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libsystemd0 amd64 245.4-4ubuntu3.4 [273 kB] Get:9 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libnetplan0 amd64 0.101-0ubuntu3~20.04.2 [28.5 kB] Get:10 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 netplan.io amd64 0.101-0ubuntu3~20.04.2 [94.2 kB] Get:11 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-firmware all 1.187.8 [102 MB] Fetched 108 MB in 1min 10s (1,552 kB/s) (Reading database ... 239087 files and directories currently installed.) Preparing to unpack .../libnss-systemd_245.4-4ubuntu3.4_amd64.deb ... Unpacking libnss-systemd:amd64 (245.4-4ubuntu3.4) over (245.4-4ubuntu3.3) ... Preparing to unpack .../udev_245.4-4ubuntu3.4_amd64.deb ... Unpacking udev (245.4-4ubuntu3.4) over (245.4-4ubuntu3.3) ... Preparing to unpack .../libudev1_245.4-4ubuntu3.4_amd64.deb ... Unpacking libudev1:amd64 (245.4-4ubuntu3.4) over (245.4-4ubuntu3.3) ... Setting up libudev1:amd64 (245.4-4ubuntu3.4) ... (Reading database ... 239087 files and directories currently installed.) Preparing to unpack .../systemd-sysv_245.4-4ubuntu3.4_amd64.deb ... Unpacking systemd-sysv (245.4-4ubuntu3.4) over (245.4-4ubuntu3.3) ... Preparing to unpack .../systemd-timesyncd_245.4-4ubuntu3.4_amd64.deb ... Unpack
[Kernel-packages] [Bug 1912198] Re: package linux-firmware 1.187.8 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => Low ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1912198 Title: package linux-firmware 1.187.8 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: Invalid Bug description: ~$ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ~$ uname -a Linux x 5.8.0-38-generic #43~20.04.1-Ubuntu SMP Tue Jan 12 16:39:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ~$ sudo apt-cache policy linux-firmware linux-firmware: Installed: 1.187.8 Candidate: 1.187.8 Version table: *** 1.187.8 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages BELOW ARE THE COPY OF WHAT EXACTLY HAPPENED WHEN I RAN APT UPGRADE. === ~$ sudo apt list --upgradable Listing... Done libnetplan0/focal-updates 0.101-0ubuntu3~20.04.2 amd64 [upgradable from: 0.100-0ubuntu4~20.04.3] libnss-systemd/focal-updates 245.4-4ubuntu3.4 amd64 [upgradable from: 245.4-4ubuntu3.3] libpam-systemd/focal-updates 245.4-4ubuntu3.4 amd64 [upgradable from: 245.4-4ubuntu3.3] libsystemd0/focal-updates 245.4-4ubuntu3.4 amd64 [upgradable from: 245.4-4ubuntu3.3] libudev1/focal-updates 245.4-4ubuntu3.4 amd64 [upgradable from: 245.4-4ubuntu3.3] linux-firmware/focal-updates,focal-updates 1.187.8 all [upgradable from: 1.187.7] netplan.io/focal-updates 0.101-0ubuntu3~20.04.2 amd64 [upgradable from: 0.100-0ubuntu4~20.04.3] systemd-sysv/focal-updates 245.4-4ubuntu3.4 amd64 [upgradable from: 245.4-4ubuntu3.3] systemd-timesyncd/focal-updates 245.4-4ubuntu3.4 amd64 [upgradable from: 245.4-4ubuntu3.3] systemd/focal-updates 245.4-4ubuntu3.4 amd64 [upgradable from: 245.4-4ubuntu3.3] udev/focal-updates 245.4-4ubuntu3.4 amd64 [upgradable from: 245.4-4ubuntu3.3] ~$ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: libnetplan0 libnss-systemd libpam-systemd libsystemd0 libudev1 linux-firmware netplan.io systemd systemd-sysv systemd-timesyncd udev 11 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 108 MB of archives. After this operation, 72.7 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libnss-systemd amd64 245.4-4ubuntu3.4 [95.9 kB] Get:2 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 udev amd64 245.4-4ubuntu3.4 [1,365 kB] Get:3 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libudev1 amd64 245.4-4ubuntu3.4 [80.3 kB] Get:4 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 systemd-sysv amd64 245.4-4ubuntu3.4 [10.3 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 systemd-timesyncd amd64 245.4-4ubuntu3.4 [28.1 kB] Get:6 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libpam-systemd amd64 245.4-4ubuntu3.4 [186 kB] Get:7 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 systemd amd64 245.4-4ubuntu3.4 [3,805 kB] Get:8 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libsystemd0 amd64 245.4-4ubuntu3.4 [273 kB] Get:9 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libnetplan0 amd64 0.101-0ubuntu3~20.04.2 [28.5 kB] Get:10 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 netplan.io amd64 0.101-0ubuntu3~20.04.2 [94.2 kB]
[Kernel-packages] [Bug 1912208] [NEW] package linux-firmware 1.187.7 failed to install/upgrade: unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/
Public bug reported: Just hit ok on ubuntu's software updater, and got notified of this problem ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guido 1627 F pulseaudio /dev/snd/controlC1: guido 1627 F pulseaudio CasperMD5CheckResult: skip Date: Mon Jan 18 09:44:13 2021 Dependencies: DpkgTerminalLog: Preparing to unpack .../linux-firmware_1.187.8_all.deb ... Unpacking linux-firmware (1.187.8) over (1.187.7) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.187.8_all.deb (--unpack): unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BCM-0bb4-0306.hcd'): Operation not permitted DuplicateSignature: package:linux-firmware:1.187.7 Unpacking linux-firmware (1.187.8) over (1.187.7) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.187.8_all.deb (--unpack): unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BCM-0bb4-0306.hcd'): Operation not permitted ErrorMessage: unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BCM-0bb4-0306.hcd'): Operation not permitted InstallationDate: Installed on 2021-01-10 (8 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 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd USB2.0 VGA UVC WebCam Bus 001 Device 004: ID 0458:0186 KYE Systems Corp. (Mouse Systems) Genius DX-120 Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X455LF PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=db228316-62a1-46bb-acf8-70710cb27e13 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. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 SourcePackage: linux-firmware Title: package linux-firmware 1.187.7 failed to install/upgrade: unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BCM-0bb4-0306.hcd'): Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X455LF.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X455LF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX455LF.205:bd08/03/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnX455LF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX455LF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X455LF dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1912208 Title: package linux-firmware 1.187.7 failed to install/upgrade: unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BCM-0bb4-0306.hcd'): Operation not permitted Status in linux-firmware package in Ubuntu: New Bug description: Just hit ok on ubuntu's software updater, and got notified of this problem ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guido 1627 F pulseaudio /dev/snd/controlC1: guido 1627 F pulseaudio CasperMD5CheckResult: skip Date: Mon Jan 18 09:44:13 2021 Dependencies: DpkgTerminalLog: Preparing to
[Kernel-packages] [Bug 1912208] Re: package linux-firmware 1.187.7 failed to install/upgrade: unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BC
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1912208 Title: package linux-firmware 1.187.7 failed to install/upgrade: unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BCM-0bb4-0306.hcd'): Operation not permitted Status in linux-firmware package in Ubuntu: New Bug description: Just hit ok on ubuntu's software updater, and got notified of this problem ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guido 1627 F pulseaudio /dev/snd/controlC1: guido 1627 F pulseaudio CasperMD5CheckResult: skip Date: Mon Jan 18 09:44:13 2021 Dependencies: DpkgTerminalLog: Preparing to unpack .../linux-firmware_1.187.8_all.deb ... Unpacking linux-firmware (1.187.8) over (1.187.7) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.187.8_all.deb (--unpack): unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BCM-0bb4-0306.hcd'): Operation not permitted DuplicateSignature: package:linux-firmware:1.187.7 Unpacking linux-firmware (1.187.8) over (1.187.7) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.187.8_all.deb (--unpack): unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BCM-0bb4-0306.hcd'): Operation not permitted ErrorMessage: unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BCM-0bb4-0306.hcd'): Operation not permitted InstallationDate: Installed on 2021-01-10 (8 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 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd USB2.0 VGA UVC WebCam Bus 001 Device 004: ID 0458:0186 KYE Systems Corp. (Mouse Systems) Genius DX-120 Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X455LF PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=db228316-62a1-46bb-acf8-70710cb27e13 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. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 SourcePackage: linux-firmware Title: package linux-firmware 1.187.7 failed to install/upgrade: unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BCM-0bb4-0306.hcd'): Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X455LF.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X455LF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX455LF.205:bd08/03/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnX455LF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX455LF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X455LF dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1912208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time
** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910866 Title: nvme drive fails after some time Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: In Progress Bug description: Sorry for the vague title. I thought this was a hardware issue until someone else online mentioned their nvme drive goes "read only" after some time. I tend not to reboot my system much, so have a large journal. Either way this happens once in a while. The / drive is fine, but /home is on nvme which just disappears. I reboot and everything is fine. But leave it long enough and it'll fail again. Here's the most recent snippet about the nvme drive before I restarted the system. Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset controller Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset controller Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure status: -19 Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more than 120 seconds. Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0 731 2 0x4000 Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123967, lost async page write Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): __ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading directory lblock 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123917, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123909, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 0, lost sync page write Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing superblock ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:56:28 2021 InstallationDate: Installed on 2020-08-15 (146 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel Corporation NUC8i7HVK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7 RebootRequiredPkgs: linux-image-5.8.0-36-generic linux-base RelatedPackageVersions: linux
[Kernel-packages] [Bug 1902672] Re: Support Advantech UNO-420 platform
** Description changed: [Impact] There are some drivers are required to enable Advantech UNO-420 platform. [Fix] Advantech is submitting their drivers to upstream for review, and considering that the patches are new drivers, it should be safe pull them back to ubuntu kernel. - https://lkml.org/lkml/2020/12/31/78 + https://patchwork.kernel.org/project/linux-watchdog/list/?series=416713 [Test] Verified on Advantech UNO-420 platform. - [Regression Potential] - Low, those commits create 3 new drivers, and doesn't modify any existing driver code. Should introduce no regression. + [Where problems could occur] + Those commits create 3 new drivers, and doesn't modify any existing driver code. Should introduce no regression. ** Description changed: [Impact] There are some drivers are required to enable Advantech UNO-420 platform. [Fix] Advantech is submitting their drivers to upstream for review, and considering that the patches are new drivers, it should be safe pull them back to ubuntu kernel. - https://patchwork.kernel.org/project/linux-watchdog/list/?series=416713 + https://lkml.org/lkml/2021/1/18/500 [Test] Verified on Advantech UNO-420 platform. [Where problems could occur] Those commits create 3 new drivers, and doesn't modify any existing driver code. Should introduce no regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902672 Title: Support Advantech UNO-420 platform Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: [Impact] There are some drivers are required to enable Advantech UNO-420 platform. [Fix] Advantech is submitting their drivers to upstream for review, and considering that the patches are new drivers, it should be safe pull them back to ubuntu kernel. https://lkml.org/lkml/2021/1/18/500 [Test] Verified on Advantech UNO-420 platform. [Where problems could occur] Those commits create 3 new drivers, and doesn't modify any existing driver code. Should introduce no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Committed Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Committed Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: 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. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. 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 1835660] Re: initramfs unpacking failed
Hi I have this issue when I try to boot USB installation pendrive with Ubuntu 20.04.1 live server made from ISO available from the official webpage. I downloaded ISO two times, I sha256 its content and compared to value stored in the SHA256SUMS file. I want to install Ubuntu on my PC next to Windows 10 (dual-boot). My PC is 4790k, 16GB RAM, GTX1080, multiple hard drives, system disk is SSD. How can I cope with this issue? What can I do to omit it or to resolve it? The "Initramfs unpacking failed: Decoding failed" message pops up just after the GRUB menu disappears. Please help, I would really like to run the Ubuntu server on my computer. Best 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/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Committed Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Committed Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: 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. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. 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 1870260] Re: initramfs unpacking failed: Decoding failed", message appears on boot up.
*** This bug is a duplicate of bug 1835660 *** https://bugs.launchpad.net/bugs/1835660 How to fix this bug? Anyone? I would like to use Ubuntu Server on my PC, but I even can't install it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870260 Title: initramfs unpacking failed: Decoding failed", message appears on boot up. Status in linux package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: OS : Ubuntu 20.04(20200401) Problem: "initramfs unpacking failed: Decoding failed", message appears on boot up solution: If we edit /etc/initramfs-tools/initramfs.conf and COMPRESS=lz4, to COMPRESS=gzip then the error is fixing . Expected solution: This but in there from a long time I have seen this from Ubuntu 18.04,19.04,19.10 now in 20.04 So please fix it or change it from lz4 to gzip. an early reply is highly appreciated Thank you . --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tamal 1451 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera 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: HP HP Laptop 15-da0xxx Package: ubuntu-meta ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=29f895bf-ab7b-4df8-8e9a-c277376a2685 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.43 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.23:bd11/29/2019:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 5AY34PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909474] Re: System hangs after attaching Mediatek mt76x2u based USB Wifi network adapter
I can add that kernel 5.4.0-52-generic is NOT affected so the bug was introduced between 5.4.0-53 and 5.4.0-58. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909474 Title: System hangs after attaching Mediatek mt76x2u based USB Wifi network adapter Status in linux package in Ubuntu: Confirmed Bug description: After attaching a Mediatek mt76x2u based USB Wifi network adapter the system (Ubuntu 20.04.1 LTS linux version 5.4.0-58-generic) hangs My findings after some testing: - A freshly installed Ubuntu 20.04 (for testing purposes) with an outdated kernel 5.4.0-26 is not affected as the USB Wifi network adapter works without any problems. - After updating this system to kernel version 5.4.0-58 the problem can be reproduced. - After upgrading to Ubuntu 20.10 with kernel version 5.8.0-33 the USB Wifi network adapter works without any problems. So I guess it could be a software problem (maybe linux-image oder linux-modules?). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joerg 821 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-14 (291 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: FUJITSU ESPRIMO P7936 NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=62b871bf-f08a-4cd3-90a5-d6e3d83c7e9c ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 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-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 RfKill: Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-12-27 (2 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2011 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.06.3012.A1 dmi.board.name: D3012-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3012-A1 dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU dmi.chassis.version: C$PIP1 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvr6.00R1.06.3012.A1:bd04/21/2011:svnFUJITSU:pnESPRIMOP7936:pvr:rvnFUJITSU:rnD3012-A1:rvrS26361-D3012-A1:cvnFUJITSU:ct6:cvrC$PIP1: dmi.product.name: ESPRIMO P7936 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910866 Title: nvme drive fails after some time Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Fix Committed Bug description: Sorry for the vague title. I thought this was a hardware issue until someone else online mentioned their nvme drive goes "read only" after some time. I tend not to reboot my system much, so have a large journal. Either way this happens once in a while. The / drive is fine, but /home is on nvme which just disappears. I reboot and everything is fine. But leave it long enough and it'll fail again. Here's the most recent snippet about the nvme drive before I restarted the system. Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset controller Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset controller Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure status: -19 Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more than 120 seconds. Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0 731 2 0x4000 Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123967, lost async page write Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): __ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading directory lblock 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123917, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123909, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 0, lost sync page write Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing superblock ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:56:28 2021 InstallationDate: Installed on 2020-08-15 (146 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel Corporation NUC8i7HVK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7 RebootRequiredPkgs: linux-image-5.8.0-36-generic linux-base RelatedPackageVersions: linux-restricted-modules-5.8.0-34-generic N/A linux-backports-modules-5.8.
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
The same thing happened when I try Ubuntu 20.10 live server... Let me check the 18.04 server. I currently use Ubuntu Desktop 18.04 on my laptop, maybe the server edition will 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/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Committed Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Committed Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: 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. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. 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 1896446] Re: Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker hard-freezes the computer
Same issue here when trying to execute: docker run -e ACCEPT_EULA=y microsoft/mssql-server-linux When running the docker run command directly on the shell, I can see the attached Kernel panic (Fatal exception in interrupt). This is 100% reproducable, in case you need any more information. ** Attachment added: "IMG_20210118_141842.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896446/+attachment/5454198/+files/IMG_20210118_141842.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896446 Title: Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker hard-freezes the computer Status in linux package in Ubuntu: Confirmed Bug description: Running the following docker image on Ubuntu 20.10/kernel 5.8 will hard-freeze the computer: docker run --rm -ti -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=myPASSWD123" -p 1433:1433 --name sqlserver mcr.microsoft.com/mssql/server:2017-latest- ubuntu I am unable to Alt+Sysrq+SUB to reboot the machine - the machine doesn't respond. I'm unable to see the crash since I'm in gnome-shell and everything just stops - music, mouse, keyboard, everything. The /var/log/kern.log doesn't seem to contain any information regarding the freeze/panic/crash. The bug seems to be 100% reproducible: 2 out of 2 times I tried, the machine froze reproducibly. When running on Ubuntu 20.04/kernel 5.4.x the image worked just fine. Thank you :) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-generic 5.8.0.18.22 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2344 F pulseaudio /dev/snd/pcmC2D0p: mavi 2344 F...m pulseaudio /dev/snd/controlC0: mavi 2344 F pulseaudio /dev/snd/controlC1: mavi 2344 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Mon Sep 21 11:14:52 2020 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1476 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2020 dmi.bios.release: 1.62 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET89W (1.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0005MS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrN1EET89W(1.62):bd06/18/2020:br1.62:efr1.18:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0005MS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mavi 2380 F pulseaudio /dev/snd/pcmC2D0p: mavi 2380 F...m pulseaudio /dev/snd/controlC0: mavi 2380 F pulseaudio /dev/snd/controlC1: mavi 2380 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap InstallationDate: Installed on 2016-09-05 (1476 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN0005MS Package: linux (not installed) ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 Tags: wayland-session groovy Uname: Linux 5.8.0-18-generic x86_64 UpgradeStatus: No upgrade log pres
[Kernel-packages] [Bug 1911456] Re: Can't receive files over bluetooth unless settings dialog is open
I tried "bluetoothctl". That's a neat tool that I didn't know about, but I couldn't find a command that would let me send stuff from my phone without interaction. I installed bt-obex and tried "bt-obex -s", which allowed file transfer but I still had to acknowledge each one. -- 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/1911456 Title: Can't receive files over bluetooth unless settings dialog is open Status in bluez package in Ubuntu: New Status in gnome-user-share package in Ubuntu: New Bug description: On 18.04 I could send files from my phone to my laptop at any time. On 20.04 I can't get files to be accepted by the laptop over bluetooth. After much frustration and experimenting, I figured out that it will work, but only if the bluetooth settings dialog is open. If the settings dialog is not open, the incoming file is rejected. If the dialog is closed after the file transfer begins, the transfer continues but the file is discarded when the transfer is complete. This is very frustrating. I need to be able to send files (mostly photos and videos) from my phone to my laptop without having to open the settings dialog on the laptop, just like I could before upgrading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1911456/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910920] Re: no soundcard present with linux-image-5.8.0-37-generic
Same issue exists in 5.8.0-38-generic. Same fix, install linux-modules- extra-5.8.0-38-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/1910920 Title: no soundcard present with linux-image-5.8.0-37-generic Status in linux package in Ubuntu: Confirmed Bug description: With linux-image-5.8.0-34-generic, all on-board soundcards work flawlessly. After update of kernel to linux-image-5.8.0-37-generic durign this week no soundcards are detected. I am happy to provide more information. But I will not sent automatic apport reports because it includes private local data. !!DMI Information !!--- Manufacturer: LENOVO Product Name: 20BUS23M00 Product Version: ThinkPad T450 Firmware Version: JBET54WW (1.19 ) Board Vendor: LENOVO Board Name:20BUS23M00 !!Kernel Information !!-- Kernel release:5.8.0-34-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.8.0-34-generic Library version:1.2.3.2 Utilities version: 1.2.3 !!Loaded ALSA modules !!--- snd_hda_intel snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [HDMI ]: HDA-Intel - HDA Intel HDMI HDA Intel HDMI at 0xe123 irq 51 1 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe1234000 irq 52 !!PCI Soundcards installed in the system !!-- 00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09) Subsystem: Lenovo Broadwell-U Audio Controller [17aa:5034] 00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition Audio Controller [8086:9ca0] (rev 03) Subsystem: Lenovo Wildcat Point-LP High Definition Audio Controller [17aa:5034] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908569] Re: video: hyperv_fb: Fix the cache type when mapping the VRAM
** Description changed:
+ [Impact]
+
We identified a problem that is causing slow logging to the console for
customers.
The following commit resolves this issue as well as other cache relates
issues:
325073ae3485 ("video: hyperv_fb: Fix the cache type when mapping the VRAM")
(marcelo.cerri: it's actually commit id
5f1251a48c17b54939d7477305e39679a565382c in the mainline kernel)
Patch details from it's commit message:
x86 Hyper-V used to essentially always overwrite the effective cache type
of guest memory accesses to WB. This was problematic in cases where there
is a physical device assigned to the VM, since that often requires that
the VM should have control over cache types. Thus, on newer Hyper-V since
2018, Hyper-V always honors the VM's cache type, but unexpectedly Linux VM
users start to complain that Linux VM's VRAM becomes very slow, and it
turns out that Linux VM should not map the VRAM uncacheable by ioremap().
Fix this slowness issue by using ioremap_cache().
With this change, the VRAM on new Hyper-V is as fast as regular RAM, so
it's no longer necessary to use the hacks we added to mitigate the
slowness, i.e. we no longer need to allocate physical memory and use
it to back up the VRAM in Generation-1 VM, and we also no longer need to
allocate physical memory to back up the framebuffer in a Generation-2 VM
and copy the framebuffer to the real VRAM. A further big change will
address these for v5.11.
Microsoft would like to request this patch in all supported releases.
+
+ [Test Case]
+
+ The test is very simple. When using the console in a local Hyper-V
+ instance and running a command with output with several lines (ie `ls -l
+ /`) the output delay is very noticeable and it should be instantaneous
+ with the fix.
+
+ [Where problems could occur]
+
+ The change might cause regressions in the hyperv_fb driver, affecting
+ one of the alternatives users have to debug problems.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1908569
Title:
video: hyperv_fb: Fix the cache type when mapping the VRAM
Status in linux-azure package in Ubuntu:
New
Status in linux-azure-4.15 package in Ubuntu:
New
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
New
Status in linux-azure source package in Focal:
New
Status in linux-azure-4.15 source package in Focal:
Invalid
Status in linux-azure source package in Groovy:
New
Status in linux-azure-4.15 source package in Groovy:
Invalid
Bug description:
[Impact]
We identified a problem that is causing slow logging to the console
for customers.
The following commit resolves this issue as well as other cache relates
issues:
325073ae3485 ("video: hyperv_fb: Fix the cache type when mapping the VRAM")
(marcelo.cerri: it's actually commit id
5f1251a48c17b54939d7477305e39679a565382c in the mainline kernel)
Patch details from it's commit message:
x86 Hyper-V used to essentially always overwrite the effective cache type
of guest memory accesses to WB. This was problematic in cases where there
is a physical device assigned to the VM, since that often requires that
the VM should have control over cache types. Thus, on newer Hyper-V since
2018, Hyper-V always honors the VM's cache type, but unexpectedly Linux VM
users start to complain that Linux VM's VRAM becomes very slow, and it
turns out that Linux VM should not map the VRAM uncacheable by ioremap().
Fix this slowness issue by using ioremap_cache().
With this change, the VRAM on new Hyper-V is as fast as regular RAM, so
it's no longer necessary to use the hacks we added to mitigate the
slowness, i.e. we no longer need to allocate physical memory and use
it to back up the VRAM in Generation-1 VM, and we also no longer need to
allocate physical memory to back up the framebuffer in a Generation-2 VM
and copy the framebuffer to the real VRAM. A further big change will
address these for v5.11.
Microsoft would like to request this patch in all supported releases.
[Test Case]
The test is very simple. When using the console in a local Hyper-V
instance and running a command with output with several lines (ie `ls
-l /`) the output delay is very noticeable and it should be
instantaneous with the fix.
[Where problems could occur]
The change might cause regressions in the hyperv_fb driver, affecting
one of the alternatives users have to debug problems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1908569/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908569] Re: video: hyperv_fb: Fix the cache type when mapping the VRAM
** Changed in: linux-azure (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-azure-4.15 (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Groovy)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1908569
Title:
video: hyperv_fb: Fix the cache type when mapping the VRAM
Status in linux-azure package in Ubuntu:
New
Status in linux-azure-4.15 package in Ubuntu:
New
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
In Progress
Status in linux-azure source package in Focal:
In Progress
Status in linux-azure-4.15 source package in Focal:
Invalid
Status in linux-azure source package in Groovy:
In Progress
Status in linux-azure-4.15 source package in Groovy:
Invalid
Bug description:
[Impact]
We identified a problem that is causing slow logging to the console
for customers.
The following commit resolves this issue as well as other cache relates
issues:
325073ae3485 ("video: hyperv_fb: Fix the cache type when mapping the VRAM")
(marcelo.cerri: it's actually commit id
5f1251a48c17b54939d7477305e39679a565382c in the mainline kernel)
Patch details from it's commit message:
x86 Hyper-V used to essentially always overwrite the effective cache type
of guest memory accesses to WB. This was problematic in cases where there
is a physical device assigned to the VM, since that often requires that
the VM should have control over cache types. Thus, on newer Hyper-V since
2018, Hyper-V always honors the VM's cache type, but unexpectedly Linux VM
users start to complain that Linux VM's VRAM becomes very slow, and it
turns out that Linux VM should not map the VRAM uncacheable by ioremap().
Fix this slowness issue by using ioremap_cache().
With this change, the VRAM on new Hyper-V is as fast as regular RAM, so
it's no longer necessary to use the hacks we added to mitigate the
slowness, i.e. we no longer need to allocate physical memory and use
it to back up the VRAM in Generation-1 VM, and we also no longer need to
allocate physical memory to back up the framebuffer in a Generation-2 VM
and copy the framebuffer to the real VRAM. A further big change will
address these for v5.11.
Microsoft would like to request this patch in all supported releases.
[Test Case]
The test is very simple. When using the console in a local Hyper-V
instance and running a command with output with several lines (ie `ls
-l /`) the output delay is very noticeable and it should be
instantaneous with the fix.
[Where problems could occur]
The change might cause regressions in the hyperv_fb driver, affecting
one of the alternatives users have to debug problems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1908569/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879989] Re: "Failed to play sound: No such driver" ubuntu 20.04
Installing libcanberra-pulse indeed fixes the problem. Thanks! Flagging this as "Invalid" seems dubious. Shouldn't libcanberra-pulse be a dependency for gnome-control-center or the base sound system? Sound used to work fine. Given the number of sound devices I always used the gnome control center to switch the right device and check it works before starting Zoom, etc. The checking failed after the latest security updates. After a couple of hours I discovered sound was actually working properly and it was just the test in the control center failing. After running `gnome-control-center sound` on the terminal I got the message "Failed to play sound: No such driver" and found this post ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879989 Title: "Failed to play sound: No such driver" ubuntu 20.04 Status in linux package in Ubuntu: Invalid Bug description: my speakers- built in audio produces terrible sound I tested the speakers via settings/sound and there was no sound I checked gnome logs and found "Failed to play sound: No such driver" I checked online and it seams to be a problem that affects many users ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: regern70802 F pulseaudio /dev/snd/pcmC0D0c: regern70802 F...m pulseaudio /dev/snd/pcmC0D0p: regern70802 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 19:13:55 2020 InstallationDate: Installed on 2020-05-16 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 15-3552 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=55652357-023b-4633-8d3a-46ce1a22d378 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.sku: 06AC dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908569] Re: video: hyperv_fb: Fix the cache type when mapping the VRAM
SRU submission: https://lists.ubuntu.com/archives/kernel-
team/2021-January/116548.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1908569
Title:
video: hyperv_fb: Fix the cache type when mapping the VRAM
Status in linux-azure package in Ubuntu:
New
Status in linux-azure-4.15 package in Ubuntu:
New
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
In Progress
Status in linux-azure source package in Focal:
In Progress
Status in linux-azure-4.15 source package in Focal:
Invalid
Status in linux-azure source package in Groovy:
In Progress
Status in linux-azure-4.15 source package in Groovy:
Invalid
Bug description:
[Impact]
We identified a problem that is causing slow logging to the console
for customers.
The following commit resolves this issue as well as other cache relates
issues:
325073ae3485 ("video: hyperv_fb: Fix the cache type when mapping the VRAM")
(marcelo.cerri: it's actually commit id
5f1251a48c17b54939d7477305e39679a565382c in the mainline kernel)
Patch details from it's commit message:
x86 Hyper-V used to essentially always overwrite the effective cache type
of guest memory accesses to WB. This was problematic in cases where there
is a physical device assigned to the VM, since that often requires that
the VM should have control over cache types. Thus, on newer Hyper-V since
2018, Hyper-V always honors the VM's cache type, but unexpectedly Linux VM
users start to complain that Linux VM's VRAM becomes very slow, and it
turns out that Linux VM should not map the VRAM uncacheable by ioremap().
Fix this slowness issue by using ioremap_cache().
With this change, the VRAM on new Hyper-V is as fast as regular RAM, so
it's no longer necessary to use the hacks we added to mitigate the
slowness, i.e. we no longer need to allocate physical memory and use
it to back up the VRAM in Generation-1 VM, and we also no longer need to
allocate physical memory to back up the framebuffer in a Generation-2 VM
and copy the framebuffer to the real VRAM. A further big change will
address these for v5.11.
Microsoft would like to request this patch in all supported releases.
[Test Case]
The test is very simple. When using the console in a local Hyper-V
instance and running a command with output with several lines (ie `ls
-l /`) the output delay is very noticeable and it should be
instantaneous with the fix.
[Where problems could occur]
The change might cause regressions in the hyperv_fb driver, affecting
one of the alternatives users have to debug problems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1908569/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912280] [NEW] package linux-image-5.4.0-58-generic 5.4.0-58.64 failed to install/upgrade: installed linux-image-5.4.0-58-generic package pre-removal script subprocess returned
Public bug reported: I rebooted my computer after doing an update on another kernel and received this error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1058 F pulseaudio steve 1643 F pulseaudio CasperMD5CheckResult: skip Date: Mon Jan 18 16:08:22 2021 ErrorMessage: installed linux-image-5.4.0-58-generic package pre-removal script subprocess returned error exit status 1 MachineType: LENOVO 81X1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=7c8dd407-bec0-448c-a227-66ab1bbdb44f ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 SourcePackage: linux Title: package linux-image-5.4.0-58-generic 5.4.0-58.64 failed to install/upgrade: installed linux-image-5.4.0-58-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: ECCN30WW 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: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14IIL05 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrECCN30WW:bd09/07/2020:br1.30:efr1.25:svnLENOVO:pn81X1:pvrIdeaPadFlex514IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514IIL05: dmi.product.family: IdeaPad Flex 5 14IIL05 dmi.product.name: 81X1 dmi.product.sku: LENOVO_MT_81X1_BU_idea_FM_IdeaPad Flex 5 14IIL05 dmi.product.version: IdeaPad Flex 5 14IIL05 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1912280 Title: package linux-image-5.4.0-58-generic 5.4.0-58.64 failed to install/upgrade: installed linux-image-5.4.0-58-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: I rebooted my computer after doing an update on another kernel and received this error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1058 F pulseaudio steve 1643 F pulseaudio CasperMD5CheckResult: skip Date: Mon Jan 18 16:08:22 2021 ErrorMessage: installed linux-image-5.4.0-58-generic package pre-removal script subprocess returned error exit status 1 MachineType: LENOVO 81X1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=7c8dd407-bec0-448c-a227-66ab1bbdb44f ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 SourcePackage: linux Title: package linux-image-5.4.0-58-generic 5.4.0-58.64 failed to install/upgrade: installed linux-image-5.4.0-58-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: ECCN30WW 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: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14IIL05 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrECCN30WW:bd09/07/2020:br1.30:efr1.25:svnLENOVO:pn81X1:pvrIdeaPadFlex514IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514IIL05: dmi.product.family: IdeaPad Flex 5 14IIL05 dmi.product.name: 81X1 dmi.product.sku: LENOVO_MT_81X1_BU
[Kernel-packages] [Bug 1912280] Re: package linux-image-5.4.0-58-generic 5.4.0-58.64 failed to install/upgrade: installed linux-image-5.4.0-58-generic package pre-removal script subprocess returned er
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912280 Title: package linux-image-5.4.0-58-generic 5.4.0-58.64 failed to install/upgrade: installed linux-image-5.4.0-58-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: I rebooted my computer after doing an update on another kernel and received this error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1058 F pulseaudio steve 1643 F pulseaudio CasperMD5CheckResult: skip Date: Mon Jan 18 16:08:22 2021 ErrorMessage: installed linux-image-5.4.0-58-generic package pre-removal script subprocess returned error exit status 1 MachineType: LENOVO 81X1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=7c8dd407-bec0-448c-a227-66ab1bbdb44f ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 SourcePackage: linux Title: package linux-image-5.4.0-58-generic 5.4.0-58.64 failed to install/upgrade: installed linux-image-5.4.0-58-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: ECCN30WW 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: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14IIL05 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrECCN30WW:bd09/07/2020:br1.30:efr1.25:svnLENOVO:pn81X1:pvrIdeaPadFlex514IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514IIL05: dmi.product.family: IdeaPad Flex 5 14IIL05 dmi.product.name: 81X1 dmi.product.sku: LENOVO_MT_81X1_BU_idea_FM_IdeaPad Flex 5 14IIL05 dmi.product.version: IdeaPad Flex 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912280] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912280 Title: package linux-image-5.4.0-58-generic 5.4.0-58.64 failed to install/upgrade: installed linux-image-5.4.0-58-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: I rebooted my computer after doing an update on another kernel and received this error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1058 F pulseaudio steve 1643 F pulseaudio CasperMD5CheckResult: skip Date: Mon Jan 18 16:08:22 2021 ErrorMessage: installed linux-image-5.4.0-58-generic package pre-removal script subprocess returned error exit status 1 MachineType: LENOVO 81X1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=7c8dd407-bec0-448c-a227-66ab1bbdb44f ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 SourcePackage: linux Title: package linux-image-5.4.0-58-generic 5.4.0-58.64 failed to install/upgrade: installed linux-image-5.4.0-58-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: ECCN30WW 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: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14IIL05 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrECCN30WW:bd09/07/2020:br1.30:efr1.25:svnLENOVO:pn81X1:pvrIdeaPadFlex514IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514IIL05: dmi.product.family: IdeaPad Flex 5 14IIL05 dmi.product.name: 81X1 dmi.product.sku: LENOVO_MT_81X1_BU_idea_FM_IdeaPad Flex 5 14IIL05 dmi.product.version: IdeaPad Flex 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911456] Re: Can't receive files over bluetooth unless settings dialog is open
In that case you probably want: bt-obex -s -y But still it's just a workaround for the original problem. -- 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/1911456 Title: Can't receive files over bluetooth unless settings dialog is open Status in bluez package in Ubuntu: New Status in gnome-user-share package in Ubuntu: New Bug description: On 18.04 I could send files from my phone to my laptop at any time. On 20.04 I can't get files to be accepted by the laptop over bluetooth. After much frustration and experimenting, I figured out that it will work, but only if the bluetooth settings dialog is open. If the settings dialog is not open, the incoming file is rejected. If the dialog is closed after the file transfer begins, the transfer continues but the file is discarded when the transfer is complete. This is very frustrating. I need to be able to send files (mostly photos and videos) from my phone to my laptop without having to open the settings dialog on the laptop, just like I could before upgrading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1911456/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910664] Re: Need a new firmware to support RTL8821ce Wifi
@Timo, we need it for Focal, too. Please help continue tracking it. Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1910664 Title: Need a new firmware to support RTL8821ce Wifi Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: In Progress Bug description: [Impact] It shows below messages and fails to enable the wifi [ 3.965229] u kernel: rtw_8821ce :04:00.0: enabling device ( -> 0003) [ 3.965403] u kernel: rtw_8821ce :04:00.0: Direct firmware load for rtw88/rtw8821c_fw.bin failed with error -2 [ 3.965405] u kernel: rtw_8821ce :04:00.0: failed to request firmware [ 3.967613] u kernel: rtw_8821ce :04:00.0: failed to load firmware [Fix] There is a new firmware need to cherry pick 401bd6de rtw88: RTL8821C: add firmware file v24.5 [Test] After add the firmware, it shows [ 3.930187] rtw_8821ce :04:00.0: enabling device ( -> 0003) [ 3.931104] rtw_8821ce :04:00.0: Firmware version 24.5.0, H2C version 12 [ 3.999271] rtw_8821ce :04:00.0 wlp4s0: renamed from wlan0 [Where problems could occur] No problems could occur since it enables a new device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1910664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910995] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
you're the best @Rakhmanov! it worked for me and spent some time trying to find a solution to this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1910995 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: after update the packages and reboot my computer, the wifi do not work any more. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-34-generic Date: Thu Jan 7 06:11:05 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-09-18 (114 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 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.2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874122] Re: Add Mute LED support for an HP Pavilion x360 Convertible 14-cd0xxx
Hello, can you give this Focal 5.4 kernel a try: https://people.canonical.com/~phlin/kernel/lp-1874122-hp-x360-mute-led/ Which contains https://github.com/torvalds/linux/commit/a0ccbc5319d57b9efdc55c943a3fde30a0776502 ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874122 Title: Add Mute LED support for an HP Pavilion x360 Convertible 14-cd0xxx Status in linux package in Ubuntu: Incomplete Bug description: Mute LED isn't on after the audio output is muted. Others: https://bugs.launchpad.net/bugs/1871090 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1849 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 14:24:52 2020 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (506 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. enx000ec6c82c3f no wireless extensions. MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-26-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2018-12-02 (505 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908286] Re: Asus G732LWS | ALC294 | Speakers don't work on 20.04 or 20.10
Hello, can you help us to narrow down this between 5.4.0-42-generic and 5.4.0-48-generic I can see there are only two kernels there: 5.4.0-45-generic and 5.4.0-47-generic Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908286 Title: Asus G732LWS | ALC294 | Speakers don't work on 20.04 or 20.10 Status in linux package in Ubuntu: Confirmed Bug description: Asus G732LWS-DS76 Realtek ALC294 (Intel HDA Audio) Xubuntu 20.04 with kernel 5.4.0-58-generic No sound from speakers even though it shows in pavucontrol. For some reason the sound gets redirected to the internal mic (when I play music there is no sound from speakers, but when I open Audacity and start recording it records a song playing). I tried: alc294-sound-patch.fw from https://bugzilla.kernel.org/show_bug.cgi?id=206589 No effect "options snd-hda-intel model=asus-zenbook" in /etc/modprobe.d/alsa-base.conf Speakers start working, but it is impossible to control the volume, they're eithher ON (100%) or OFF (Muted) I tried different kernels and sidtributions to localize the problem: Doesn't work Xubuntu 20.04 | 5.4.0-58-generic Xubuntu 20.04 | 5.4.0-54-generic Xubuntu 20.04 | 5.4.0-48-generic Xubuntu 20.10 | 5.8.0-25-generic Fedora 33 | 5.8.15-301.fc33.x86_64 Manjaro 20.2 | 5.9.11-3-MANJARO WORKS Xubuntu 20.04 | 5.4.0-42-generic It appears that it is a kernel problem and something broke between 5.4.0-42-generic and 5.4.0-48-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kotek 5812 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Dec 15 09:25:13 2020 InstallationDate: Installed on 2020-10-01 (75 days ago) InstallationMedia: Xubuntu 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 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ROG Strix G732LWS_G732LWS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=8d8cfa7f-5e24-4952-b6ae-4ae35ca9563d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G732LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G732LWS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG732LWS.310:bd07/14/2020:svnASUSTeKCOMPUTERINC.:pnROGStrixG732LWS_G732LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG732LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G732LWS_G732LWS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908286] Re: Asus G732LWS | ALC294 | Speakers don't work on 20.04 or 20.10
Hello, I installed both 5.4.0-45-generic and 5.4.0-47-generic and they are pretty weird. My wifi didn't work on both and my trackpad also didn't on 5.4.0-47-generic. Also, no sound on both. Both from speaker and headphones. Is there a chance I did something wrong? I just did a "sudo apt install linux-image-5.4.0-45-generic linux-headers-5.4.0-45-generic" for both versions. Thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908286 Title: Asus G732LWS | ALC294 | Speakers don't work on 20.04 or 20.10 Status in linux package in Ubuntu: Confirmed Bug description: Asus G732LWS-DS76 Realtek ALC294 (Intel HDA Audio) Xubuntu 20.04 with kernel 5.4.0-58-generic No sound from speakers even though it shows in pavucontrol. For some reason the sound gets redirected to the internal mic (when I play music there is no sound from speakers, but when I open Audacity and start recording it records a song playing). I tried: alc294-sound-patch.fw from https://bugzilla.kernel.org/show_bug.cgi?id=206589 No effect "options snd-hda-intel model=asus-zenbook" in /etc/modprobe.d/alsa-base.conf Speakers start working, but it is impossible to control the volume, they're eithher ON (100%) or OFF (Muted) I tried different kernels and sidtributions to localize the problem: Doesn't work Xubuntu 20.04 | 5.4.0-58-generic Xubuntu 20.04 | 5.4.0-54-generic Xubuntu 20.04 | 5.4.0-48-generic Xubuntu 20.10 | 5.8.0-25-generic Fedora 33 | 5.8.15-301.fc33.x86_64 Manjaro 20.2 | 5.9.11-3-MANJARO WORKS Xubuntu 20.04 | 5.4.0-42-generic It appears that it is a kernel problem and something broke between 5.4.0-42-generic and 5.4.0-48-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kotek 5812 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Dec 15 09:25:13 2020 InstallationDate: Installed on 2020-10-01 (75 days ago) InstallationMedia: Xubuntu 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 0b05:1866 ASUSTek Computer, Inc. N-KEY Device Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ROG Strix G732LWS_G732LWS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=8d8cfa7f-5e24-4952-b6ae-4ae35ca9563d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G732LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G732LWS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG732LWS.310:bd07/14/2020:svnASUSTeKCOMPUTERINC.:pnROGStrixG732LWS_G732LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG732LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G732LWS_G732LWS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904860] Re: QCA9377 802.11ac Wireless Network Adapter-Network unclaimed on every ubuntu os
[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/1904860 Title: QCA9377 802.11ac Wireless Network Adapter-Network unclaimed on every ubuntu os Status in linux package in Ubuntu: Expired Bug description: 4 months ago,I installed ubuntu on my lenovo E41-25 notebook. Working damn fine going good. recently i updated my system via `sudo apt update && sudo apt upgrade`. Thats all i do. Now,my wifi adapter not working properly. harish@harish$ sudo dmesg | grep ath10k [ 12.347183] ath10k_pci :02:00.0: failed to iomap BAR0 [ 12.347239] ath10k_pci :02:00.0: failed to claim device: -5 [ 12.347355] ath10k_pci: probe of :02:00.0 failed with error -5 harish@harish$ lshw -c network WARNING: you should run this program as super-user. *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:01:00.0 logical name: enp1s0 version: 15 serial: 9c:5a:44:44:f4:41 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:30 ioport:3000(size=256) memory:f0404000-f0404fff memory:f040-f0403fff *-network UNCLAIMED description: Network controller product: QCA9377 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:02:00.0 version: 31 width: 64 bits clock: 33MHz capabilities: cap_list configuration: latency=0 *-network description: Ethernet interface physical id: 1 bus info: usb@2:3 logical name: usb0 serial: ca:74:69:53:09:2a capabilities: ethernet physical configuration: broadcast=yes driver=rndis_host driverversion=22-Aug-2005 firmware=RNDIS device ip=192.168.42.225 link=yes multicast=yes harish@harish$ lsmod Module Size Used by rndis_host 20480 0 cdc_ether 20480 1 rndis_host usbnet 45056 2 rndis_host,cdc_ether mii20480 1 usbnet cdc_acm40960 0 rfcomm 81920 4 cmac 16384 2 algif_hash 16384 1 algif_skcipher 16384 1 af_alg 24576 6 algif_hash,algif_skcipher bnep 24576 2 nls_iso8859_1 16384 1 edac_mce_amd 32768 0 kvm_amd98304 0 ccp86016 1 kvm_amd kvm 663552 1 kvm_amd crct10dif_pclmul 16384 1 ghash_clmulni_intel16384 0 snd_hda_codec_conexant28672 1 uvcvideo 98304 0 snd_hda_codec_generic81920 1 snd_hda_codec_conexant aesni_intel 372736 3 amdgpu 4579328 21 ledtrig_audio 16384 2 snd_hda_codec_generic,snd_hda_codec_conexant videobuf2_vmalloc 20480 1 uvcvideo videobuf2_memops 20480 1 videobuf2_vmalloc snd_hda_codec_hdmi 61440 1 crypto_simd16384 1 aesni_intel cryptd 24576 3 crypto_simd,ghash_clmulni_intel snd_hda_intel 53248 4 snd_intel_dspcfg 24576 1 snd_hda_intel snd_hda_codec 135168 4 snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel videobuf2_v4l2 24576 1 uvcvideo snd_hda_core 90112 5 snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec videobuf2_common 49152 2 videobuf2_v4l2,uvcvideo videodev 225280 3 videobuf2_v4l2,uvcvideo,videobuf2_common glue_helper16384 1 aesni_intel amd_iommu_v2 20480 1 amdgpu snd_hwdep 20480 1 snd_hda_codec mc 53248 4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common snd_pcm 106496 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core btusb 57344 0 btrtl 24576 1 btusb ath10k_pci 49152 0 btbcm 16384 1 btusb btintel24576 1 btusb snd_seq_midi 20480 0 snd_seq_midi_event 16384 1 snd_seq_midi ath10k_core 475136 1 ath10k_pci bluetooth 548864 31 btrtl,btintel,btbcm,bnep,bt
[Kernel-packages] [Bug 1906128] Re: Touchpad not detected on ByteSpeed C15B laptop
Hi Po-Hsu
I spent this evening installing Ubuntu. I tried Xenial, Bionic, Focal
and Groovy.
The proposed release worked on Xenial, but not on any of the others.
Just to confirm the process: I installed a fresh copy of the release,
then went to the developer options tab in the Software and Updates app
and ticked the proposed box. When this was done, the app updated the
cache. Then I used Software updater to upgrade and it worked (or not).
For the releases that didn't work I also tried using apt from the
terminal. Updated and then upgraded. Rebooted and then tested for the
trackpad function. Only worked in Xenial.
Let me know if I needed to do something different or to try again.
Regards,
Tom
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1906128
Title:
Touchpad not detected on ByteSpeed C15B laptop
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
In Progress
Bug description:
[Impact]
Touchpad on a ByteSpeed C15B laptop is not working.
User will need to add i8042.noloop=1 to boot options to make it work.
[Fix]
* a48491c65b513e ("Input: i8042 - add ByteSpeed touchpad to noloop table")
This fix can be cherry-picked into all affected releases.
[Test Case]
Test kernel for Bionic / Focal can be found here:
https://people.canonical.com/~phlin/kernel/lp-1906128-C15B/
And they have been tested with positive test results.
[Where problems could occur]
The fix is just a small and simple hardware quirk. I can't think of any
potential problem for now.
== Original Bug Report ==
Touchpad hardware is OK and works for Win10. Not working for live disc, not
for 18.04 and not for 20.04 after upgrading. I've attached a Logitech wireless
mouse with its USB adapter and that works. Bluetooth is also missing, but I
have not started trying to skull that out. I'm happy to help try debugging
things, and to help resolve the issue.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-54-generic 5.4.0-54.60
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tom1395 F pulseaudio
/dev/snd/controlC0: tom1395 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 28 19:09:05 2020
InstallationDate: Installed on 2020-01-26 (307 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
MachineType: ByteSpeed LLC ByteSpeed Laptop C15B
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-54-generic
root=UUID=07b919ee-c6ad-41a5-9c64-df3c8e477b6f ro quiet splash i8042.reset
i8042.nomux i8042.nopnp i8042noloop noapic vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.4.0-54-generic N/A
linux-backports-modules-5.4.0-54-generic N/A
linux-firmware1.187.4
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-11-25 (3 days ago)
dmi.bios.date: 03/18/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: C15B.616
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: C15B
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: ByteSpeed LLC
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrC15B.616:bd03/18/2014:svnByteSpeedLLC:pnByteSpeedLaptopC15B:pvr1.0:rvnPEGATRONCORPORATION:rnC15B:rvr1.0:cvnByteSpeedLLC:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: PEGA Family
dmi.product.name: ByteSpeed Laptop C15B
dmi.product.sku: 0
dmi.product.version: 1.0
dmi.sys.vendor: ByteSpeed LLC
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906128/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904823] Re: device-mapper: btree spine: node_check failed: csum
[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/1904823 Title: device-mapper: btree spine: node_check failed: csum Status in linux package in Ubuntu: Expired Bug description: While I have found previous reports of this check failing, they are all resolved years ago. So I guess this is something for upstream. device-mapper: btree spine: node_check failed: csum 544691913 != wanted 1983069109 [ cut here ] kernel BUG at drivers/md/persistent-data/dm-btree-spine.c:34! invalid opcode: [#1] SMP PTI CPU: 42 PID: 2175930 Comm: kworker/42:1 Not tainted 5.4.0-51-generic #56-Ubuntu Hardware name: Quanta Cloud Technology Inc. QuantaGrid D52B-1U/S5B-MB (LBG-1G), BIOS 3B17.Q302 08/12/2020 Workqueue: dm_bufio_cache work_fn [dm_bufio] RIP: 0010:node_prepare_for_write+0x61/0x70 [dm_persistent_data] Code: 01 00 48 89 43 08 e8 1e 9f ff ff ba 00 10 00 00 4c 89 e6 4c 89 f7 89 03 e8 1c fe ff ff 85 c0 75 09 5b 41 5c 41 5d 41 5e 5d c3 <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 RSP: 0018:98b9f539fd08 EFLAGS: 00010286 RAX: ffac RBX: 8bce38b4f000 RCX: RDX: RSI: 8bc580e978c8 RDI: 8bc580e978c8 RBP: 98b9f539fd28 R08: 8bc580e978c8 R09: 00c80001 R10: 0095 R11: 6b300095 R12: 8bc451e18d20 R13: 1000 R14: c0416550 R15: 8bc451e18d20 FS: () GS:8bc580e8() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f1204062010 CR3: 007ef02da004 CR4: 007626e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 PKRU: 5554 Call Trace: ? le64_inc+0x20/0x20 [dm_persistent_data] dm_block_manager_write_callback+0x42/0x50 [dm_persistent_data] submit_io+0x1ad/0x230 [dm_bufio] __flush_write_list+0x81/0xc0 [dm_bufio] work_fn+0x1c8/0x1f0 [dm_bufio] process_one_work+0x1eb/0x3b0 worker_thread+0x4d/0x400 kthread+0x104/0x140 ? process_one_work+0x3b0/0x3b0 ? kthread_park+0x90/0x90 ret_from_fork+0x35/0x40 Modules linked in: dm_snapshot vhost_net vhost tap ip6table_raw tcp_diag udp_diag inet_diag overlay veth dummy bridge nf_tables netconsole sch_ingress vxlan ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout openvswitch nsh nf_conncount ip6table_filter ip6_tables xt_CT iptable_raw iptable_mangle intel_rapl_msr intel_rapl_common xt_set xt_tcpudp isst_if_common skx_edac xt_state nfit xt_conntrack x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul ghash_clmulni_intel iptable_filter aesni_intel ipmi_ssif bpfilter kvm_intel crypto_simd cryptd glue_helper rapl kvm intel_cstate drm_vram_helper ttm drm_kms_helper i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt ioatdma ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter acpi_pad mac_hid ip_set_hash_net ip_set nfnetlink sch_fq_codel nf_nat_ftp nf_conntrack_ftp nf_nat_sip nf_conntrack_sip nf_nat_pptp nf_conntrack_pptp nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 tcp_htcp 8021q garp mrp stp llc bonding drm ip_tables x_tables autofs4 btrfs zstd_compress raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c raid10 raid1 crc32_pclmul ixgbe xfrm_algo dca mdio nvme nvme_core ahci i2c_i801 lpc_ich libahci wmi ---[ end trace 7e896cfa4fcf1285 ]--- RIP: 0010:node_prepare_for_write+0x61/0x70 [dm_persistent_data] Code: 01 00 48 89 43 08 e8 1e 9f ff ff ba 00 10 00 00 4c 89 e6 4c 89 f7 89 03 e8 1c fe ff ff 85 c0 75 09 5b 41 5c 41 5d 41 5e 5d c3 <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 RSP: 0018:98b9f539fd08 EFLAGS: 00010286 RAX: ffac RBX: 8bce38b4f000 RCX: RDX: RSI: 8bc580e978c8 RDI: 8bc580e978c8 RBP: 98b9f539fd28 R08: 8bc580e978c8 R09: 00c80001 R10: 0095 R11: 6b300095 R12: 8bc451e18d20 R13: 1000 R14: c0416550 R15: 8bc451e18d20 FS: () GS:8bc580e8() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f1204062010 CR3: 007ef02da004 CR4: 007626e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 PKRU: 5554 [ cut here ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904823/+subscriptions -- Mai
[Kernel-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward
** Changed in: util-linux (Ubuntu) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886112 Title: Enabling DMESG_RESTRICT in Groovy Onward Status in linux package in Ubuntu: Fix Released Status in procps package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Won't Fix Status in linux source package in Groovy: Fix Released Status in procps source package in Groovy: Fix Released Status in util-linux source package in Groovy: Won't Fix Bug description: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of sensitive information, such as detailed call traces and kernel addresses found in register dumps in kernel oops messages. Exploit developers and attackers can leverage these information leaks to get past KASLR, and they can use the kernel log buffer to get instant feedback on their privilege escalation attacks, as failures will be shown as further oops messages, which attackers can use to fix and tune their programs until they work. Currently, if I create a new, unprivileged user on a Focal system, they cannot access /var/log/kern.log, /var/log/syslog or see system events in journalctl. But yet, they are given free reign to the kernel log buffer. $ sudo adduser dave $ su dave $ groups dave $ cat /var/log/kern.log cat: /var/log/kern.log: Permission denied $ cat /var/log/syslog cat: /var/log/syslog: Permission denied $ journalctl Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target. Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms. $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... I propose that we restrict access to dmesg to users in group 'adm' like so: 1) Add kernel.dmesg_restrict = 1 to /etc/sysctl.d/10-kernel-hardening.conf 2) Following changes to /bin/dmesg permissions in package 'util-linux' - Ownership changes to root:adm - Permissions changed to 0750 (-rwxr-x---) - Add cap_syslog capability to binary. For most users, they will use the initial admin account, which is in the 'adm' group already, and will see no impact to these changes. If a log scraper type program needs access to dmesg, the user the daemon runs as can simply be added to the 'adm' group. [Testcase] Currently, all users can run /usr/bin/dmesg to view the kernel log buffer: $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... When the changes are applied, the default admin user will be able to view dmesg (since they are in group 'adm'), while new unprivileged users will not. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1886112-test $ whoami ubuntu $ groups ubuntu adm cdrom sudo dip plugdev $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... $ sudo adduser dave $ su dave $ groups dave $ dmesg -bash: /usr/bin/dmesg: Permission denied [Regression Potential] Some users or log scraper type programs may need to view the kernel log buffer, or have access to dmesg. In this case, the underlying service user would need to be added to the 'adm' group. Users have the ability to disable DMESG_RESTRICT by changing kernel.dmesg_restrict sysctl in /etc/sysctl.d/10-kernel-hardening.conf from '1' to '0', followed by a reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchp
[Kernel-packages] [Bug 1827452] Re: null pointer dereference in uvcvideo
Can someone please test the patch in #23? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827452 Title: null pointer dereference in uvcvideo Status in linux package in Ubuntu: Expired Bug description: I have a logitech c920 webcam. When using this camera in obs-studio v23.x, all of my USB devices stop working and I see the following in my kernel log: [ 590.282211] usb 3-3: new high-speed USB device number 5 using xhci_hcd [ 592.660916] usb 3-3: New USB device found, idVendor=046d, idProduct=082d, bcdDevice= 0.11 [ 592.660922] usb 3-3: New USB device strings: Mfr=0, Product=2, SerialNumber=1 [ 592.660925] usb 3-3: Product: HD Pro Webcam C920 [ 592.660928] usb 3-3: SerialNumber: 2EAD866F [ 592.664600] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d) [ 592.666416] uvcvideo 3-3:1.0: Entity type for entity Processing 3 was not initialized! [ 592.666421] uvcvideo 3-3:1.0: Entity type for entity Extension 6 was not initialized! [ 592.666425] uvcvideo 3-3:1.0: Entity type for entity Extension 12 was not initialized! [ 592.666428] uvcvideo 3-3:1.0: Entity type for entity Camera 1 was not initialized! [ 592.666430] uvcvideo 3-3:1.0: Entity type for entity Extension 8 was not initialized! [ 592.666433] uvcvideo 3-3:1.0: Entity type for entity Extension 9 was not initialized! [ 592.666436] uvcvideo 3-3:1.0: Entity type for entity Extension 10 was not initialized! [ 592.666439] uvcvideo 3-3:1.0: Entity type for entity Extension 11 was not initialized! [ 592.22] input: HD Pro Webcam C920 as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/input/input23 [ 748.490453] usb 3-3: reset high-speed USB device number 5 using xhci_hcd [ 938.125745] usb 3-3: USB disconnect, device number 5 [ 943.298530] BUG: unable to handle kernel NULL pointer dereference at [ 943.298533] #PF error: [normal kernel read fault] [ 943.298534] PGD 8007ca5f3067 P4D 8007ca5f3067 PUD 0 [ 943.298536] Oops: [#1] SMP PTI [ 943.298538] CPU: 0 PID: 9442 Comm: libobs: graphic Tainted: P OE 5.0.0-13-generic #14-Ubuntu [ 943.298539] Hardware name: Gigabyte Technology Co., Ltd. Z87-HD3/Z87-HD3, BIOS F7 01/20/2014 [ 943.298543] RIP: 0010:usb_ifnum_to_if+0x24/0x60 [ 943.298544] Code: ff c3 0f 1f 40 00 0f 1f 44 00 00 55 48 8b 87 c0 03 00 00 48 89 e5 48 85 c0 74 43 0f b6 48 04 84 c9 74 39 48 8b 90 98 00 00 00 <48> 8b 3a 0f b6 7f 02 39 fe 74 2b 48 8d 90 a0 00 00 00 8d 41 ff 48 [ 943.298545] RSP: 0018:bdae493dbab0 EFLAGS: 00010202 [ 943.298547] RAX: a106ae527000 RBX: a1070ad0a800 RCX: 0004 [ 943.298547] RDX: RSI: 0001 RDI: a1070ad0a800 [ 943.298548] RBP: bdae493dbab0 R08: 00027040 R09: b57825b8 [ 943.298549] R10: fba45fce4bc0 R11: 0001 R12: [ 943.298550] R13: a10644187b98 R14: ff92 R15: a1075131a000 [ 943.298551] FS: 7f93c40d7700() GS:a1075ea0() knlGS: [ 943.298552] CS: 0010 DS: ES: CR0: 80050033 [ 943.298553] CR2: CR3: 0006f8a94004 CR4: 001606f0 [ 943.298553] Call Trace: [ 943.298557] usb_hcd_alloc_bandwidth+0x241/0x370 [ 943.298559] usb_set_interface+0xfc/0x380 [ 943.298565] uvc_video_start_transfer+0x155/0x4b0 [uvcvideo] [ 943.298568] uvc_video_start_streaming+0x7f/0xd0 [uvcvideo] [ 943.298570] uvc_start_streaming+0x28/0x70 [uvcvideo] [ 943.298573] vb2_start_streaming+0x6d/0x110 [videobuf2_common] [ 943.298575] vb2_core_streamon+0x59/0xc0 [videobuf2_common] [ 943.298578] vb2_streamon+0x18/0x30 [videobuf2_v4l2] [ 943.298580] uvc_queue_streamon+0x2e/0x50 [uvcvideo] [ 943.298582] uvc_ioctl_streamon+0x3f/0x60 [uvcvideo] [ 943.298588] v4l_streamon+0x20/0x30 [videodev] [ 943.298592] __video_do_ioctl+0x19a/0x3f0 [videodev] [ 943.298596] video_usercopy+0x1a6/0x660 [videodev] [ 943.298599] ? v4l_s_fmt+0x630/0x630 [videodev] [ 943.298603] video_ioctl2+0x15/0x20 [videodev] [ 943.298606] v4l2_ioctl+0x49/0x50 [videodev] [ 943.298608] do_vfs_ioctl+0xa9/0x640 [ 943.298610] ? __switch_to_asm+0x34/0x70 [ 943.298611] ? __switch_to_asm+0x40/0x70 [ 943.298612] ? __switch_to_asm+0x34/0x70 [ 943.298612] ? __switch_to_asm+0x40/0x70 [ 943.298613] ? __switch_to_asm+0x34/0x70 [ 943.298614] ? __switch_to_asm+0x40/0x70 [ 943.298615] ? __switch_to_asm+0x34/0x70 [ 943.298616] ? __switch_to_asm+0x40/0x70 [ 943.298617] ksys_ioctl+0x67/0x90 [ 943.298619] __x64_sys_ioctl+0x1a/0x20 [ 943.298621] do_syscall_64+0x5a/0x110 [ 943.298622] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 943.298623] RIP: 0033:0x7f9430e082e9 [ 943.298624] Code: 00 c3 66 2e 0f 1f 84 00 00
[Kernel-packages] [Bug 1902672] Re: Support Advantech UNO-420 platform
** Description changed: [Impact] There are some drivers are required to enable Advantech UNO-420 platform. [Fix] Advantech is submitting their drivers to upstream for review, and considering that the patches are new drivers, it should be safe pull them back to ubuntu kernel. https://lkml.org/lkml/2021/1/18/500 [Test] Verified on Advantech UNO-420 platform. [Where problems could occur] - Those commits create 3 new drivers, and doesn't modify any existing driver code. Should introduce no regression. + Those commits create 3 new drivers, and do not modify any existing drivers. Should introduce no regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902672 Title: Support Advantech UNO-420 platform Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: [Impact] There are some drivers are required to enable Advantech UNO-420 platform. [Fix] Advantech is submitting their drivers to upstream for review, and considering that the patches are new drivers, it should be safe pull them back to ubuntu kernel. https://lkml.org/lkml/2021/1/18/500 [Test] Verified on Advantech UNO-420 platform. [Where problems could occur] Those commits create 3 new drivers, and do not modify any existing drivers. Should introduce no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902672/+subscriptions -- Mailing list: https://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 1906086] Re: DIsplay is limited to top half of the screen
Hi Daniel. I have installed Ubuntu over Win10. I have enabled Ubuntu on Wayland. Everything works - LAN/WAN, Audio, Video, WiFi, Bluetooth, Printing, Mail, software updates, etc. It's just that it is still squashed up into the top half of the screen. What else should I be doing please? Regards, Glenn Stewart due to the limits, I will send through 3 x messages with the attachments On Tue, Jan 19, 2021 at 7:42 PM Glenn Stewart wrote: > Hi Daniel. > > I have installed Ubuntu over Win10. > I have enabled Ubuntu on Wayland. > Everything works - LAN/WAN, Audio, Video, WiFi, Bluetooth, Printing, Mail, > software updates, etc. > It's just that it is still squashed up into the top half of the screen. > > What else should I be doing please? > > Regards, > Glenn Stewart > > Regards, > Glenn Stewart > > > On Tue, Jan 19, 2021 at 7:38 PM Glenn Stewart > wrote: > >> Hi Daniel. >> >> I have installed Ubuntu over Win10. >> I have enabled Ubuntu on Wayland. >> Everything works - LAN/WAN, Audio, Video, WiFi, Bluetooth, Printing, >> Mail, software updates, etc. >> It's just that it is still squashed up into the top half of the screen. >> >> What else should I be doing please? >> >> Regards, >> Glenn Stewart >> >> >> On Thu, Dec 3, 2020 at 6:50 AM Glenn Stewart >> wrote: >> >>> I did not want to actually install Ubuntu. I wanted to be able to run >>> it and see how it has progressed since I last used 12.04 from 2012 till >>> 2016 on 3 x machines that were formerly Win XP. >>> >>> In summary then, my hardware is suspected to be the issue, and if I want >>> to progress to see if the Wayland option helps, I have to install Ubuntu. >>> >>> From what I have seen so far, I will not proceed with installation. >>> >>> However, I may have to-visit that decision if I am unable to resolve the >>> issue in Win 10 - if I have to rebuild Win 10, I may as well clear it all >>> out and install Ubuntu. >>> >>> Thank you for your perseverance Daniel. >>> >>> Regards, >>> Glenn Stewart >>> >>> >>> On Thu, Dec 3, 2020 at 3:20 PM Daniel van Vugt < >>> 1906...@bugs.launchpad.net> wrote: >>> OK. You would need to install Ubuntu before you can choose Wayland. But it's not guaranteed to fix things. And if you see related problems in Windows 10 then it sounds like the hardware is faulty :( Maybe not badly faulty... if the problem is just incorrect timing info in the monitor's EDID. It's not unusual for manufacturers to mess up EDIDs so hopefully that's the only problem. Regardless, if this is fixable in software then it sounds kernel-related so reassigning... ** Package changed: mutter (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1906086 Title: DIsplay is limited to top half of the screen Status in linux package in Ubuntu: New Bug description: Display is limited to the top half of the screen. I have tried changing the resolution, without success. I am attempting to trial Ubuntu 20.10 from a USB stick. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.445.1 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 04:09:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8058] LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP EliteOne 800 G2 23-in Touch AiO ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2019 dmi.bios.vendor: HP dmi.bios.version: N11 Ver. 02.45 dmi.board.name: 8058 dmi.board.vendor: HP dmi.board.version: KBC Version 05.39 dmi.chassis.asset.tag: AUD6100LCF dmi.chassis.type: 13 dmi.chassis.vendor: HP
Re: [Kernel-packages] [Bug 1906086] Re: DIsplay is limited to top half of the screen
Regards, Glenn Stewart On Tue, Jan 19, 2021 at 7:52 PM Glenn Stewart wrote: > > > Regards, > Glenn Stewart > > > On Tue, Jan 19, 2021 at 7:51 PM Glenn Stewart > wrote: > >> Hi Daniel. >> >> I have installed Ubuntu over Win10. >> I have enabled Ubuntu on Wayland. >> Everything works - LAN/WAN, Audio, Video, WiFi, Bluetooth, Printing, Mail, >> software updates, etc. >> It's just that it is still squashed up into the top half of the screen. >> >> What else should I be doing please? >> >> Regards, >> Glenn Stewart >> due to the limits, I will send through 3 x messages with the attachments >> >> On Tue, Jan 19, 2021 at 7:42 PM Glenn Stewart >> wrote: >> >>> Hi Daniel. >>> >>> I have installed Ubuntu over Win10. >>> I have enabled Ubuntu on Wayland. >>> Everything works - LAN/WAN, Audio, Video, WiFi, Bluetooth, Printing, >>> Mail, >>> software updates, etc. >>> It's just that it is still squashed up into the top half of the screen. >>> >>> What else should I be doing please? >>> >>> Regards, >>> Glenn Stewart >>> >>> Regards, >>> Glenn Stewart >>> >>> >>> On Tue, Jan 19, 2021 at 7:38 PM Glenn Stewart < >>> glennwtstewar...@gmail.com> wrote: >>> Hi Daniel. I have installed Ubuntu over Win10. I have enabled Ubuntu on Wayland. Everything works - LAN/WAN, Audio, Video, WiFi, Bluetooth, Printing, Mail, software updates, etc. It's just that it is still squashed up into the top half of the screen. What else should I be doing please? Regards, Glenn Stewart On Thu, Dec 3, 2020 at 6:50 AM Glenn Stewart < glennwtstewar...@gmail.com> wrote: > I did not want to actually install Ubuntu. I wanted to be able to run > it and see how it has progressed since I last used 12.04 from 2012 till > 2016 on 3 x machines that were formerly Win XP. > > In summary then, my hardware is suspected to be the issue, and if I > want to progress to see if the Wayland option helps, I have to install > Ubuntu. > > From what I have seen so far, I will not proceed with installation. > > However, I may have to-visit that decision if I am unable to resolve > the issue in Win 10 - if I have to rebuild Win 10, I may as well clear it > all out and install Ubuntu. > > Thank you for your perseverance Daniel. > > Regards, > Glenn Stewart > > > On Thu, Dec 3, 2020 at 3:20 PM Daniel van Vugt < > 1906...@bugs.launchpad.net> wrote: > >> OK. You would need to install Ubuntu before you can choose Wayland. >> But it's not guaranteed to fix things. And if you see related problems in >> Windows 10 then it sounds like the hardware is faulty :( >> Maybe not badly faulty... if the problem is just incorrect timing >> info in the monitor's EDID. It's not unusual for manufacturers to mess up >> EDIDs so hopefully that's the only problem. >> >> Regardless, if this is fixable in software then it sounds >> kernel-related >> so reassigning... >> >> >> ** Package changed: mutter (Ubuntu) => linux (Ubuntu) >> >> ** Changed in: linux (Ubuntu) >>Status: Incomplete => New >> >> -- >> You received this bug notification because you are subscribed to the >> bug >> report. >> https://bugs.launchpad.net/bugs/1906086 >> >> Title: >> DIsplay is limited to top half of the screen >> >> Status in linux package in Ubuntu: >> New >> >> Bug description: >> Display is limited to the top half of the screen. >> I have tried changing the resolution, without success. >> >> I am attempting to trial Ubuntu 20.10 from a USB stick. >> >> 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 >> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair >> ApportVersion: 2.20.11-0ubuntu27.4 >> Architecture: amd64 >> BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' >> CasperMD5CheckResult: pass >> CasperVersion: 1.445.1 >> CompositorRunning: None >> CurrentDesktop: ubuntu:GNOME >> Date: Sat Nov 28 04:09:34 2020 >> DistUpgraded: Fresh install >> DistroCodename: focal >> DistroVariant: ubuntu >> ExtraDebuggingInterest: Yes, if not too technical >> GraphicsCard: >>Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 >> [VGA controller]) >> Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8058] >> LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 >> (20200731) >> MachineType: HP HP EliteOne 800 G2 23-in Touch AiO >> ProcEnviron: >>PATH=(custom, no user) >>XDG_RUNTIME_DIR= >>LANG=en_US.UTF-8 >>SHELL=/bin/bash >>>
Re: [Kernel-packages] [Bug 1906086] Re: DIsplay is limited to top half of the screen
Regards, Glenn Stewart On Tue, Jan 19, 2021 at 7:51 PM Glenn Stewart wrote: > Hi Daniel. > > I have installed Ubuntu over Win10. > I have enabled Ubuntu on Wayland. > Everything works - LAN/WAN, Audio, Video, WiFi, Bluetooth, Printing, Mail, > software updates, etc. > It's just that it is still squashed up into the top half of the screen. > > What else should I be doing please? > > Regards, > Glenn Stewart > due to the limits, I will send through 3 x messages with the attachments > > On Tue, Jan 19, 2021 at 7:42 PM Glenn Stewart > wrote: > >> Hi Daniel. >> >> I have installed Ubuntu over Win10. >> I have enabled Ubuntu on Wayland. >> Everything works - LAN/WAN, Audio, Video, WiFi, Bluetooth, Printing, Mail, >> software updates, etc. >> It's just that it is still squashed up into the top half of the screen. >> >> What else should I be doing please? >> >> Regards, >> Glenn Stewart >> >> Regards, >> Glenn Stewart >> >> >> On Tue, Jan 19, 2021 at 7:38 PM Glenn Stewart >> wrote: >> >>> Hi Daniel. >>> >>> I have installed Ubuntu over Win10. >>> I have enabled Ubuntu on Wayland. >>> Everything works - LAN/WAN, Audio, Video, WiFi, Bluetooth, Printing, >>> Mail, software updates, etc. >>> It's just that it is still squashed up into the top half of the screen. >>> >>> What else should I be doing please? >>> >>> Regards, >>> Glenn Stewart >>> >>> >>> On Thu, Dec 3, 2020 at 6:50 AM Glenn Stewart >>> wrote: >>> I did not want to actually install Ubuntu. I wanted to be able to run it and see how it has progressed since I last used 12.04 from 2012 till 2016 on 3 x machines that were formerly Win XP. In summary then, my hardware is suspected to be the issue, and if I want to progress to see if the Wayland option helps, I have to install Ubuntu. From what I have seen so far, I will not proceed with installation. However, I may have to-visit that decision if I am unable to resolve the issue in Win 10 - if I have to rebuild Win 10, I may as well clear it all out and install Ubuntu. Thank you for your perseverance Daniel. Regards, Glenn Stewart On Thu, Dec 3, 2020 at 3:20 PM Daniel van Vugt < 1906...@bugs.launchpad.net> wrote: > OK. You would need to install Ubuntu before you can choose Wayland. > But it's not guaranteed to fix things. And if you see related problems in > Windows 10 then it sounds like the hardware is faulty :( > Maybe not badly faulty... if the problem is just incorrect timing info > in the monitor's EDID. It's not unusual for manufacturers to mess up EDIDs > so hopefully that's the only problem. > > Regardless, if this is fixable in software then it sounds > kernel-related > so reassigning... > > > ** Package changed: mutter (Ubuntu) => linux (Ubuntu) > > ** Changed in: linux (Ubuntu) >Status: Incomplete => New > > -- > You received this bug notification because you are subscribed to the > bug > report. > https://bugs.launchpad.net/bugs/1906086 > > Title: > DIsplay is limited to top half of the screen > > Status in linux package in Ubuntu: > New > > Bug description: > Display is limited to the top half of the screen. > I have tried changing the resolution, without success. > > I am attempting to trial Ubuntu 20.10 from a USB stick. > > 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 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu27.4 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: pass > CasperVersion: 1.445.1 > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sat Nov 28 04:09:34 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 > [VGA controller]) > Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8058] > LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > MachineType: HP HP EliteOne 800 G2 23-in Touch AiO > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz > file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 12/24/2019 > dmi.bios.v
[Kernel-packages] [Bug 1906086] Re: DIsplay is limited to top half of the screen
Hi Glenn, That first screenshot in comment #17 is most telling. It shows the BIOS screen is rendered half right and half wrong. So given some of the problems persist in the BIOS screen (when no OS is running) AND in Windows 10, I think it's likely the screen is faulty and needs replacing. But maybe we can still improve the Linux situation... Next, 1. Please verify the problem occurs in both 'Ubuntu' and 'Ubuntu on Wayland' sessions. 2. Log into a regular 'Ubuntu' session and run: xrandr --verbose > xrandrv.txt cat /sys/class/drm/*/edid > edids.bin and attach the resulting files here. 3. Look in Settings > Screen Display and try selecting different values of 'Resolution' and 'Refresh Rate'. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (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/1906086 Title: DIsplay is limited to top half of the screen Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Display is limited to the top half of the screen. I have tried changing the resolution, without success. I am attempting to trial Ubuntu 20.10 from a USB stick. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.445.1 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 04:09:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8058] LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP EliteOne 800 G2 23-in Touch AiO ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2019 dmi.bios.vendor: HP dmi.bios.version: N11 Ver. 02.45 dmi.board.name: 8058 dmi.board.vendor: HP dmi.board.version: KBC Version 05.39 dmi.chassis.asset.tag: AUD6100LCF dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN11Ver.02.45:bd12/24/2019:svnHP:pnHPEliteOne800G223-inTouchAiO:pvr:rvnHP:rn8058:rvrKBCVersion05.39:cvnHP:ct13:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteOne 800 G2 23-in Touch AiO dmi.product.sku: T6T88PA#ABG dmi.sys.vendor: HP 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 N/A 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/1906086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906086] Re: DIsplay is limited to top half of the screen
I would also try the latest BIOS update from HP, but you need to have Windows installed to do that :( https://support.hp.com/au-en/drivers/selfservice/swdetails/hp- eliteone-800-g2-23-inch-touch-all-in-one-pc/769/swItemId/vc-262067-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/1906086 Title: DIsplay is limited to top half of the screen Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Display is limited to the top half of the screen. I have tried changing the resolution, without success. I am attempting to trial Ubuntu 20.10 from a USB stick. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.445.1 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 04:09:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8058] LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP EliteOne 800 G2 23-in Touch AiO ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2019 dmi.bios.vendor: HP dmi.bios.version: N11 Ver. 02.45 dmi.board.name: 8058 dmi.board.vendor: HP dmi.board.version: KBC Version 05.39 dmi.chassis.asset.tag: AUD6100LCF dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN11Ver.02.45:bd12/24/2019:svnHP:pnHPEliteOne800G223-inTouchAiO:pvr:rvnHP:rn8058:rvrKBCVersion05.39:cvnHP:ct13:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteOne 800 G2 23-in Touch AiO dmi.product.sku: T6T88PA#ABG dmi.sys.vendor: HP 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 N/A 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/1906086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
I have successfully resolved the problem. I don't know exactly what helped because I did a few things. Namely: I switched all SATA cables from the second controller to the first (my computer motherboard has two SATA controllers) and disabled the Compatibility Support Module. Unfortunately, CSM turned off the BIOS boot options, only UEFI was left. After changing the settings and rebooting, the message "Initramfs unpacking failed: Decoding failed" was still showing on the screen, but the system continued the boot process and finally saw the Ubuntu Server 20.04 installer -- You 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 grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Committed Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Committed Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: 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. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. 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
